Issuing EAS Attestations with OKX Wallet: Fields, Revocation, and Verification

When you use OKX Wallet to issue an EAS attestation, the wallet itself does not "create" or "edit" the attestation content for you. The role of OKX Wallet here is the same as MetaMask: connect to the EAS interface, pop up the transaction signature, and write the attestation on-chain. What really determines what you can sign and how you sign it is the EAS Schema (data template) and the EASScan or third-party frontend.

OKX Exchange
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！

Register Now App Download

Fields: The Schema Decides Everything

An "attestation" in EAS is not free text. It must reference a registered Schema. The Schema defines what fields exist in this attestation and what type each field is.

The simplest Schema can have only one string field, such as "an attestation about a statement." More complex Schemas can have dozens of fields covering various types: address, bool, uint8 to uint256, bytes32, string, and even arrays of these types.

For example, there is a music metadata Schema on EASScan that includes more than twenty string fields such as isrc, displayArtist, and genre, as well as structured fields like RP_nfcUidHash (bytes32) and RP_releaseId (uint256). Another Human Passport Schema uses combinations like bool passing_score, uint8 score_decimals, and tuple(string provider, uint256 score)[] stamps to express scores and a list of credentials.

What you can put into the attestation you issue depends on which Schema you reference. If the content you want to attest does not fit any existing Schema, you need to register a new one first — and registering a Schema itself is an on-chain transaction that requires a signature from OKX Wallet.

Issuing: Operate in EASScan or a Compatible Frontend

OKX Wallet cannot directly issue EAS attestations within its own interface. You need to open a frontend that supports EAS (such as the deployed network corresponding to easscan.org, or any application that integrates the EAS SDK), connect OKX Wallet, and then:

1. Select or register a Schema. If it is an existing Schema, simply select it.

2. Fill in the field values. The frontend will automatically render the corresponding input boxes based on the Schema. For string, enter text; for address, enter an address; for uint256, enter a number.

3. Specify the Recipient. This is the "recipient" address of the attestation. It can be someone else or yourself.

4. Confirm Revocable. When the Schema is registered, it sets whether "attestations under this Schema can be revoked." If the Schema itself is set to non-revocable, you cannot change this when issuing.

5. Sign and submit. OKX Wallet pops up the transaction confirmation. You review the gas fee and network, then sign.

EAS attestations are soul-bound — they are non-transferable, non-sellable, and non-tradable. They do not need an SBT wrapper. Once signed, it is signed. You can only "void" it through revocation.

Revocation: Only the Attester Can Do It

Revocation changes the attestation status from valid to revoked, setting the revoked field to true. Only the Attester address that issued this attestation can revoke it.

There are two ways to do it:

Manually revoke on EASScan. If you are using a frontend based on easscan.org, open the detail page of that attestation. If you are the Attester, a "revoke attestation" button will appear on the page. Click it and then confirm with a signature from OKX Wallet.

Through the command line or SDK. easctl revoke --schema 0x... --uid 0x... is the CLI method. If using the SDK, eas.revoke({ uid: "0x..." }) returns a transaction. After signing, it goes on-chain.

The prerequisite for revocation is that the Schema was registered with revocable: true. If the Schema is non-revocable, there is no way to void it after you issue it.

Verification: How to Confirm an Attestation Is Still Valid

Verification is not just "look at it and say it is real." You need to check the on-chain state. Use the EAS SDK's getAttestation(uid) to pull the attestation object. It contains a revocationTime field.

• revocationTime = 0: The attestation has not been revoked.

• revocationTime > 0: The attestation has been revoked. This timestamp is the moment the revocation happened.

At the same time, check whether the attester field is a signing address you trust. An attestation with revocationTime = 0 but whose attester is a wallet you do not recognize is just as worthless as a revoked attestation.

OKX Exchange
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！

Register Now App Download

References

1. Ethereum Attestation Service·Create a Schema, no update date indicated on the page; verification date: 2026-10-12.
2. EASScan·Schemas, no update date indicated on the page; verification date: 2026-10-12.
3. EASScan·Schema #4190, no update date indicated on the page; verification date: 2026-10-12.
4. EASScan·Schema #116 (Human Passport), no update date indicated on the page; verification date: 2026-10-12.
5. EASScan·EAS Block Explorer Homepage, no update date indicated on the page; verification date: 2026-10-12.
6. Rootstock Documentation·Navigating the EAS Dashboard, page publication or update date: 2026-05-27; verification date: 2026-10-12.
7. NPM·@cellar-door/eas v0.1.0, page publication or update date: 2026-03-09; verification date: 2026-10-12.
8. Ethereum Attestation Service·Revoking Attestations, no update date indicated on the page; verification date: 2026-10-12.
9. NPM·easctl, page publication or update date: 2026-03-25; verification date: 2026-10-12.
10. GitHub·ethereum-attestation-service/eas-sdk repository, page publication or update date: 2026-08-26; verification date: 2026-10-12.