ICS Committee Verification Guide

Round 6 · PR #886 · TX to follow

GM, signers! Please review the applications and the resulting ICS list before signing the update transaction. You can start the review now; the TX will be shared separately.

1. Update your local files

The PR has not been merged yet. Updating develop alone will not give you this round's files.

• Recommended: check out the PR to get the round's configuration, source data and tree artifacts together.
• If you keep your existing checkout, at minimum update ics_assessment/config.py to match the PR. You also need its updated assessment data to reproduce the results; changing config.py does not refresh those files.

Use the PR's committed data for verification. Running sync can replace it with newer data.

The config includes a change from 30 to 28 days of mainnet activity. Confirm this criterion with the technical team before signing.

2. Review the applications

Applications CSV: [attach the file or its private link here]

You can review the applications manually or run the batch script. For script setup, see ics_assessment/README.md in the PR.

Save the supplied CSV as ics_assessment/ics-forms.csv. Set HIGH_SIGNAL_API_KEY and HUMAN_PASSPORT_API_KEY locally; I can share both in DM.

From ics_assessment/, with your Python environment active, run:

python main.py batch --full

The script skips submissions marked outdated. Check for approved but ineligible and not approved but eligible results, and DM me about any discrepancies.

Passport is queried live, so scores may differ from the original assessment. Its rate limit also makes the script slow.

3. Check the ICS list and tree

Use the files in artifacts/mainnet/ics from the PR. Updating the assessment's config.py alone does not update the tree files.

1. Check that sources/ics_assessment_6.json matches the main addresses of the active APPROVED applications. A successful batch creates approved-address-summary.json for this comparison.
2. With the Python and JavaScript dependencies installed, set PROVIDER_URL_MAINNET to a mainnet RPC that supports historical calls. From artifacts/mainnet/ics, run:

python main.py
node compose.js

1. Check that the regenerated list contains the approved additions and preserves the previous addresses, and that the generated artifacts match the PR. Keep the generator's reference block and existing sources/exclusions unchanged.

4. Check the TX and sign

Once the TX is shared:

• Compare your generated merkle-tree.json with the tree at the IPFS reference in the TX.
• Confirm that the generated root (tree[0]) matches the root in the decoded Easy Track calldata. The TX announcement will include the relevant contract/decoder link.
• Check the multisig transaction using the guide in the pinned committee message.

Resolve any discrepancies before signing. If the PR changes after your review, recheck the affected files and results.

Please keep the applications CSV, API keys and application logs private.