Skip to main content

What is attestation

What is attestation

An attestation is a signed statement that confirms something specific about a subject — an address, an action, a credential, or a piece of data. It is not identity itself; it is a claim about identity or about something an entity has done. In crypto and decentralized systems, attestations provide a structured way for one party to make a verifiable statement that another party can independently check without relying on a central authority.

Think of an attestation as a notarized stamp on a document. The stamp does not create the document or define who you are — it confirms that a specific fact about the document (or about you) has been verified by someone. In the blockchain context, that "stamp" is a cryptographic signature attached to a structured claim, and anyone with access to the right tools can verify it.

In short: an attestation is a cryptographically signed statement confirming a fact about a subject or action — it is a building block for trustless verification, not a synonym for identity itself.

How attestation works

Structure of an attestation

An attestation typically contains three elements: a subject (the entity or address the claim is about), a claim (the specific assertion being made), and a signature (the cryptographic proof that the issuer actually made the statement). Some attestation frameworks add metadata such as timestamps, expiration dates, revocation status, and schema identifiers that define the structure of the claim.

For example, an attestation might state: "Address 0xABC… completed KYC verification on 2025-06-15, as confirmed by Issuer 0xDEF…." The claim is structured data, the subject is the address, and the signature ties it to the issuer's cryptographic key.

Onchain and offchain attestations

Attestations can be recorded directly on a blockchain (onchain) or stored offchain and verified on demand. Onchain attestations are permanently visible and can be referenced by smart contracts — for instance, a DeFi protocol might check whether an address holds a valid attestation before granting access. Offchain attestations are stored privately or on decentralized storage networks and are presented only when needed, preserving privacy while still being cryptographically verifiable.

The choice between onchain and offchain depends on the use case. Public reputation scores or protocol-level permissions often benefit from onchain attestations. Sensitive personal data — like proof of age or residency — is better handled offchain, where the subject controls when and to whom it is disclosed.

Attestation frameworks

Several protocols have emerged to standardize how attestations are created, stored, and verified. The Ethereum Attestation Service (EAS) provides a flexible onchain registry for arbitrary attestations on Ethereum and its Layer 2 networks. Verifiable Credentials, defined by the W3C standard, offer a broader interoperable format used across both blockchain and traditional web systems. These frameworks differ in scope and implementation but share the same core idea: structured, signed claims that can be independently verified.

Why attestation matters for crypto AI projects

In the crypto AI space, attestations serve several practical functions that directly affect how projects build trust and prove their claims.

Verifying AI outputs

When an AI model produces an inference result — a prediction, a classification, a generated output — an attestation can record what model was used, what input was provided, and what output was returned. This creates a verifiable trail. If a project claims its AI model achieved a certain accuracy or produced a specific result, an onchain attestation of that output makes the claim independently checkable rather than a matter of trust.

Establishing reputation without centralization

Decentralized compute networks, data marketplaces, and AI agent platforms need ways to evaluate participant reliability without a central reputation authority. Attestations allow peers, validators, or protocol mechanisms to issue signed statements about a participant's behavior — tasks completed, uptime maintained, data quality verified. These attestations accumulate into a portable, verifiable reputation that no single party controls.

Gating access and permissions

Smart contracts can use attestations as access conditions. A decentralized AI marketplace might require compute providers to hold an attestation confirming their hardware meets minimum specifications. A governance system might require attestations confirming a participant's stake duration or contribution history before granting voting rights.

Where this appears in DecAIHub project cards

Attestation as a concept surfaces in project cards primarily through:

  • Category — projects in Identity, Verification, or Data categories often rely on attestation mechanisms as core infrastructure.
  • AI component — when a project records AI inference results or model validation outcomes onchain, attestation is typically the mechanism used.
  • Onchain necessity — attestation is one of the concrete reasons a project might need blockchain: to create tamper-proof, verifiable records of claims and actions that would otherwise require trusting a single party.

What attestation alone does not prove

  • Truth of the claim — an attestation proves that a specific issuer made a specific statement. It does not guarantee that the statement is accurate. A bad actor can sign a false attestation. The value depends on the issuer's credibility and the verification process behind the claim.
  • Identity of the subject — an attestation about an address does not prove who controls that address in the physical world unless additional identity verification is layered in. See What is identity in crypto for this distinction.
  • Decentralization — issuing attestations onchain does not make a project decentralized. If a single entity is the sole issuer of all attestations in a system, the trust model remains centralized despite the onchain infrastructure.
  • Permanence — some attestation frameworks support revocation or expiration. An attestation that was valid yesterday may not be valid today. Always check whether the attestation system includes revocation logic.

Do not confuse with

Term Distinction
Identity Identity is the broader concept of who or what an entity is. An attestation is a single signed statement about that entity — one building block of identity, not identity itself.
Credential A credential (e.g., a Verifiable Credential) is a structured data format for claims. An attestation is the broader concept of a signed statement. Credentials are one implementation format for attestations.
Certificate In traditional systems, a certificate (e.g., SSL/TLS) binds a public key to an identity via a trusted authority. An attestation is a more general cryptographic claim that does not require a centralized certificate authority.

Frequently asked questions

Is an attestation the same as a digital identity?

No. An attestation is a single statement about a subject. Identity is the broader concept of who or what that subject is. A digital identity might be composed of many attestations — proof of name, proof of age, proof of account ownership — but each attestation is just one piece of evidence, not the identity itself.

Can attestations be faked?

The cryptographic signature on an attestation cannot be forged without the issuer's private key. However, the content of an attestation can be false if the issuer is dishonest or compromised. The trustworthiness of an attestation depends on the trustworthiness of the issuer and the rigor of the verification process that preceded the signature. This is why attestation frameworks often include issuer reputation systems and dispute mechanisms.

Do attestations need to be onchain?

Not necessarily. Offchain attestations — stored locally, on IPFS, or in other decentralized storage — are cryptographically valid and verifiable without touching the blockchain. Onchain attestations offer permanence and composability with smart contracts but come with gas costs and privacy trade-offs. The right choice depends on the use case.

External references

See also