<aside> 👋 This FAQ is relevant when you’re setting up an access requirement for the Ethereum Attestation Service (EAS). In order for you to gate your DeForm based on the validity of the users’ EAS attestations, you must specify various metadata pertaining to the relevant attestations.

</aside>

Configure the EAS Schema UID

1. Go to the Ethereum Attestation Service website and go to the desired EAS schema page.

Here’s an example:

Link: https://optimism.easscan.org/schema/view/0xfdcfdad2dbe7489e0ce56b260348b7f14e8365a8a325aef9834818c00d46b31b

Obtain the schema UID from the top of the page, under the schema’s name. Alternatively, the same schema UID is part of the schema page’s URL.

2. Input your EAS schema UID into the access gate requirement setup

Make sure to save your requirement!

[Optional] Configure the EAS attester address

In the case that you want to make sure you only check for a particular EAS schema’s attestations that are issued by a certain address, you can configure the address in the requirement below.

Note: we don’t allow you to configure multiple issuers right now. If this is something you need, please let us know here: https://deform.canny.io/feature-requests

[Optional] Configure advanced filters for EAS attestations

In the case that you want the EAS attestations to contain certain data in its payload, you can configure the EAS attestation requirement on DeForm.

You can add as many key-value pairs as you’d like - in the example below, we check whether a user’s received attestations is associated to a particular EAS schema, issued by a particular attester address, and has the following key value pairs in its payload:

• key = uint128, value = 1011
• key = address, value = 0x0000000000000000000000000000000000000000
• key = uint128_array, value = [1, 2, 3] *
• key = string_array, value = ["item1", "item2", "item3"] *