Agent identity on Base: the NEXTAI roadmap
The proposal to anchor on Base with EAS and ERC-8004: what is being studied, what evidence is still missing and what works today without blockchain.
The NEXTAI roadmap includes studying the anchoring of agent credential issuances and revocations on Base, using technologies such as EAS and ERC-8004. As of 17 September 2026 this layer is presented as a proposal, with no committed deployment date and no on-chain verification on record.
The current public system works with signed credentials, DID identifiers, verification and status lists. You can consult the Argos ID and the documentation.
The problem it aims to solve
A signature lets you verify the origin and integrity of a declaration. An external registry can add timestamp evidence and make it harder for an operator to alter the published history after the fact. Those are different contributions.
That registry will not demonstrate that the declared content is true, or that the agent only uses the permissions written into its credential. Nor will it turn the issuer into an independent auditor.
What we require before calling it live
- A specification of the anchored data, its relationship with the credential and its privacy policy.
- A network, contracts and addresses that can be verified.
- Real test transactions and independent query examples.
- A consistent procedure for issuance, replacement and revocation.
- Handling of network failures, costs and changes to the standard in use.
- A public verification that distinguishes the signature from the anchor.
Until that evidence exists, we will not add a visual check that appears to confirm a deployment that is not there.
What is still needed outside blockchain
Connectors have to check permissions and status before accepting actions. Jobs and access have to be stoppable. Authenticating the agent making a request requires a binding to that interaction; presenting a copied public credential is not enough.
Revoking a credential communicates a change of status. Its propagation depends on caches and consumers; it is not automatic proof that the agent has been switched off.
What a client can check today
The declared identity and scope, the status returned by the verifier, and the published documentation. The credential is a verifiable self-declaration issued by Cosmolabs OÜ for its own agents. It is not a state identity document and it is not an official attestation.
The NEXTAI commercial priority is to pair that identity with evidence of control in each company's processes. An external registry will make sense if it improves the evidence and the interoperability for a specific case.
Read what blockchain adds and what it does not or visit the identity page.