A blockchain attestation proves who signed a statement, not that the statement is true. Coinbase issued 723,690 on the Base network to certify verified accounts. This is the number recorded o
A blockchain attestation proves who signed a statement, not that the statement is true. Coinbase issued 723,690 on the Base network to certify verified accounts. This is the number recorded on October 19, 2026 on the EASSCAN explorer. The W3C, which sets web standards, reminds that verifying a credential does not amount to validating its content.
An attestation is a declaration from one entity about another entity, such as an address, or about data. Decentralized identity is one of its building blocks. On Ethereum and its layer 2 networks, a dedicated protocol is called Ethereum Attestation Service, or EAS. This open-source protocol has no token, and the protocol charges no fees.
Its documentation provides a simple definition.
Basically, attestations are simply digital signatures on structured information.
Ethereum Attestation Service, official documentation
A blockchain attestation is thus not an NFT. According to the EAS documentation, NFTs serve poorly as credentials. They transfer from one wallet to another and lack interoperability. A resold diploma would indeed no longer make sense. Our beginner’s guide to NFTs details this model of exchangeable token. EAS finally clarifies that it is not an identity provider.
The architecture consists of two smart contracts. The first records the schemas, that is, the declaration formats. For example, a schema can contain a course title and a completion date. The second contract issues attestations based on these schemas.
Each attestation then contains a series of fields, public when recorded on the blockchain. These include a unique identifier, the used schema, the issuer’s address and, if applicable, that of the recipient. There are also the creation date and a possible expiration date. If the issuer revoked it, the revocation date also appears. An attestation cannot be modified. Its issuer can revoke it if the schema allows it, and this revocation remains visible.
EAS operates on Ethereum and on several layer 2 networks, including Optimism and Base. On these two networks, the contract is even at the same address.
Coinbase relies on EAS for its “Coinbase Verifications.” According to its developer documentation, the exchange issues these attestations on Base, from the ENS name verifications.coinbase.eth. An application can then know if a wallet is linked to a Coinbase account authorized to trade. The account verification schema contains only one field: yes or no.
The EASSCAN explorer allows measuring this usage. On October 19, 2026, the Coinbase “verified account” schema, created on October 23, 2023, had 723,690 attestations. The “verified country” schema had 306,815. This second schema records the country of residence in clear text, readable by all. Yet Coinbase presents its attestations as evidence “without revealing private information”. Its documentation also specifies: “since the attestation can be stored on the blockchain, anyone can collect EAS attestation data”.
These two schemas weigh heavily on their network. On the same day, EASSCAN counted 3,644,502 attestations on Base, including more than one million for these Coinbase-only schemas. Among the three compared networks, Optimism had 1,319,168, and Ethereum only 14,957.
Not all attestations end up on the blockchain. An off-chain attestation is created by a simple signature from your wallet, without network fees. According to EAS documentation, even the explorer server then ignores its existence. You then keep it as a file, link, or QR code.
However, this discretion has a price. An off-chain attestation does not have a network-provided timestamp. To prove it existed on a given date, simply record its identifier on the blockchain, for a minimal cost. To make it public, it can also be published on IPFS, a decentralized storage network: it then becomes visible on the explorer.
For a school, the choice matters. An on-chain attestation by default exposes its data to everyone, like the country of residence of Coinbase clients. An off-chain attestation remains between the issuer and its holder, as long as no one publishes it.
A valid signature proves that an address issued a statement, and that it has not changed. However, it says nothing about the truthfulness of the content. The W3C recommendation clearly states: “verifiability of a credential does not imply the truth of the claims it contains”. The verifier must therefore check these claims according to their own rules.
An address also does not prove identity. The protocol is open to all: anyone can thus create a “diploma” schema and issue attestations. Before trusting an attestation, ask yourself five questions.
The W3C model relies on three main actors: the issuer, the holder, and the verifier. To publish the necessary identifiers, the text cites trusted databases or government identity databases. Distributed ledgers, like a blockchain, appear only as one example among others.
EAS’s blockchain attestation thus constitutes one solution among others, specific to the Ethereum ecosystem. Its own documentation acknowledges that a contract cannot directly read a W3C-format credential without a gateway. Moreover, no attestation alone equates to a diploma recognized by a state.
On October 19, 2026, EASSCAN recorded 3,644,502 attestations on Base, versus 14,957 on Ethereum. Each relies on EAS’s two contracts, whose logic is explained in our guide on how smart contracts work.
