Attestation
Also called cryptographic attestation, on-chain attestation, remote attestation
An attestation is a signed, verifiable statement one party makes that a third party can check without having to trust the party making it. That's a much older and broader pattern than any one product in this Lexicon, and it's worth seeing the shape of it before narrowing to one implementation. A TLS certificate is an attestation: a certificate authority signs "this public key belongs to this domain," and any browser can check the signature without asking the CA to vouch for it personally each time. A hardware TPM's remote-attestation report is an attestation: the chip signs "this device booted this exact, unmodified firmware," and a remote server can verify that signature before trusting the device. A W3C Verifiable Credential, the format underneath most of this Lexicon's identity terms, is itself an attestation: an issuer signs "this claim about this subject is true," and any verifier can check it independently of the issuer being online.
Where it comes from
The general pattern predates any single company and belongs to nobody. The specific piece Solidus touches is the Ethereum Attestation Service (EAS), an open-source public good for making arbitrary on-chain or off-chain attestations about anything, built by Bryce Patrick and Steve Dakh. EAS has become a widely used shared "reputation and evidence" layer across Ethereum-ecosystem identity, agent, and DAO tooling: the point of using a shared registry rather than a private one is that other tools built on EAS can see and act on an attestation Solidus emits, not just Solidus's own systems. Solidus did not build EAS; it emits into it.
Solidus status
Solidus Agents' backend includes a built and deployed EAS bridge module:
when a BBS+ capability credential is issued to, or revoked from, an agent,
the module is designed to mirror that event as an EAS attestation against
EAS's standard OP-stack predeploy contracts (fixed addresses ending …0021
and …0020, the same on every OP-stack chain, independently checkable
against EAS's own documentation).
What is not independently confirmed as of this writing: whether that mirroring is actually switched on and flowing on live testnet today. Turning it on requires a one-time on-chain schema-registration transaction from a funded relayer wallet, internal project records as late as 2026-07-10 show that step still blocked on funding the relayer through a public, captcha-gated faucet, and nothing in the record since confirms it was completed. State this plainly rather than assume the best case: the code is shipped; whether the schema is actually registered and attestations are actually flowing is unconfirmed, and should be checked against the live contracts again before anyone claims otherwise.
Proof: the EAS predeploy contracts Solidus's module talks to are public and fixed, verifiable independently of Solidus. Whether Solidus's own schema is registered under them, and whether any attestations have actually been emitted, is checkable on EAS's own explorer once the schema UID is known; that UID was not available to confirm at the time of writing, which is itself the honest status to report rather than a claim either way.
Where it comes from
Someone else specified this. Solidus assembles it.
An attestation, in this field, is any signed, verifiable statement one party makes that a third party can check without having to trust the party making it, a pattern far older and broader than any one product. A TLS certificate is an attestation ("this key belongs to this domain," signed by a certificate authority); a TPM's remote-attestation report is an attestation ("this device booted this exact firmware," signed by hardware); a W3C Verifiable Credential is an attestation too ("this issuer says this claim is true about this subject"). The specific piece Solidus touches is the Ethereum Attestation Service (EAS), an open-source public good for making arbitrary on-chain or off-chain attestations, built by Bryce Patrick and Steve Dakh, which has become a common shared "reputation and evidence" layer across the Ethereum ecosystem's identity, agent, and DAO tooling alike. Solidus did not build EAS; it emits into it.
How to check this
Running on the test network. Not mainnet.
The EAS predeploy contracts Solidus's module talks to are public and fixed, verifiable independently of Solidus. Whether Solidus's own schema is registered under them, and whether any attestations have actually been emitted, is checkable on EAS's own explorer once the schema UID is known; that UID was not available to confirm at the time of writing, which is itself the honest status to report rather than a claim either way.