Attestations (EAS)

Be attested by an address on the Ethereum Attestation Service.

An attestation requirement checks that a member's wallet has been attested on the Ethereum Attestation Service (EAS) by a given attester, under a given schema, and optionally that a field of the attestation has a given value.

What it's for

EAS attestations are signed statements about an address: "passed KYC", "attended the hackathon", "graduated from the course". If you or a partner issue attestations, this requirement turns them into a role without any extra integration.

Set it up

1. Under Who gets it, press Requirement and pick Be attested by.
2. Pick the chain the attestations are made on.
3. In Reference, paste the address of the attester, the wallet or contract that issues the attestations.
4. In Schema Id, paste the schema's ID, a 0x value. Find it on the EAS explorer for that chain (easscan.org): open the schema, or any attestation made with it, and copy its schema UID.
5. To check a field inside the attestation, enter its name in Key and the value in Value, and pick how to compare them. Leave both empty to require only that an attestation exists.
6. Press Add requirement.

Gotchas

• The attestation must be on the chain you picked and made to one of the member's connected wallets.
• Key must match the field name in the schema exactly.

Examples

• Verified humans: attested by your verifier's address under your "verified" schema.
• Graduates: attested by your course's address, Key level, Value advanced.

Requirement type

This is the exact type the requirement picker offers, with its fields as you see them in the form.

Chains (6): Ethereum, Arbitrum One, OP Mainnet, Base, BASE_GOERLI, Linea Mainnet. See supported chains.

Be attested by

Members connect a wallet to be checked.