Is NEUS an open standard?
The proof envelope follows the draft CAIP-380 Portable Proof format and can be read independently of the NEUS app.
CAIP-380 on ChainAgnosticStandardsCAIP-380 proposal
Last updated: August 2026
What CAIP-380 Portable Proof is
CAIP-380 is a draft ChainAgnostic standard for a wallet-signed, chain-agnostic proof envelope. It uses CAIP-2 chain context, CAIP-10 account ids, W3C did:pkh profile identifiers, and a SHAKE-256 qHash over the standardized proof request fields. Wallet-signed NEUS requests use this envelope; other authenticated NEUS proofs remain NEUS proofs without being labeled CAIP-380.
Signed envelopes verify without NEUS
An app that retains a complete wallet-signed envelope can recompute its qHash, signer string, DID binding, and signature without calling NEUS. That proves the request and its signer. Current status, revocation, and verifier outcomes still need NEUS or another compatible result source.
NEUS vs W3C Verifiable Credentials
W3C Verifiable Credentials is a general data model; CAIP-380 is a chain-agnostic, wallet-signed envelope purpose-built for portable proof with a stable proof ID. The two are complementary, not mutually exclusive.
| Dimension | W3C Verifiable Credentials | NEUS (CAIP-380) |
|---|---|---|
| What it is | General data model for verifiable claims | Chain-agnostic, wallet-signed proof envelope with a stable proof ID |
| Chain support | Resolver-dependent; often chain-agnostic by design but heavy to verify | One envelope. Any CAIP-2 namespace. |
| Verification | Requires a resolver layer | Request hash + signer string + signature verify offline; live results remain source-backed |
| Best for | Broad credential use cases (education, government, identity) | Portable proofs for apps, gates, agents, and partner flows |
CAIP-380 vs ERC-7683
ERC-7683 is an Ethereum token standard for cross-chain intents; CAIP-380 is a chain-agnostic proof envelope for portable trust. They solve different problems and compose cleanly.
| Dimension | ERC-7683 | CAIP-380 |
|---|---|---|
| Problem space | Cross-chain token intent execution | Portable proof verification |
| Chain scope | EVM chains | Any CAIP-2 namespace |
| Output | Settled token transfer | A proof ID downstream systems reuse |
| Composes with NEUS? | Yes; NEUS can gate on token outcomes | CAIP-380 is the envelope for wallet-signed NEUS requests |
NEUS and the MCP authorization spec
MCP (Model Context Protocol) connects AI assistants to tools and context. Its authorization specification secures a client's access to an MCP server. NEUS adds agent identity, granted permissions, and reusable portable proofs that integrations can check across sessions.
Independent proof checks
CAIP-380 defines a draft format for wallet-signed request envelopes. Systems that retain a complete envelope can validate its request hash and signature without the NEUS interface. NEUS records completed checks; applications decide which current results to require and how to include them in their own audit logs.
Works with existing agent stacks
NEUS is framework-neutral and model-neutral. Agent runtimes handle planning, tools, and memory; messaging protocols handle agent-to-agent handoff; model providers handle inference. NEUS supplies identity and permission proofs that those systems can check. It does not replace the framework, model, or messaging protocol. See the agents page for where NEUS sits in the stack.
Frequently asked questions
Is NEUS an open standard or a proprietary format?
NEUS uses the draft CAIP-380 Portable Proof format. The proposal documents the signed-envelope fields, identifier, and signing format publicly; it is not a finalized standard.
What is CAIP-380 Portable Proof?
CAIP-380 is a draft proposal for a wallet-signed, chain-agnostic proof envelope. It uses CAIP-2 chain context, CAIP-10 account IDs, did:pkh identifiers, and a SHAKE-256 proof ID over defined request fields.
Can I verify a NEUS proof without NEUS infrastructure?
If you retain the complete wallet-signed envelope, you can validate its request ID, DID binding, and signature against the draft format. Current status, revocation, and verifier outcomes still require NEUS or another compatible source.
What happens to proofs if NEUS shuts down?
Integrations that retain complete signed envelopes can continue validating their proof IDs and signatures. Live discovery, revocation status, and provider-backed refreshes require an available compatible service.
How is NEUS different from W3C Verifiable Credentials?
W3C Verifiable Credentials defines a broad model for verifiable claims. The draft CAIP-380 format defines a wallet-signed proof envelope with chain and account references. An integration may use either or both.
How does CAIP-380 relate to ERC-7683?
ERC-7683 standardizes cross-chain token intents. The draft CAIP-380 format describes portable proofs. They address different parts of an integration and can be used together.
How does NEUS relate to the MCP authorization spec?
MCP connects a client to tools and context. Its authorization specification secures access to an MCP server. NEUS adds identity, permissions, and portable proofs through a hosted MCP server.
How does NEUS support audit and accountability?
NEUS records completed identity, ownership, and permission checks as portable proofs. Applications can reference those proofs in their own activity logs and access reviews.
How does CAIP-380 fit with agentic IAM and non-human identity (NHI) governance?
Sign-in systems manage accounts and login tokens. NEUS permission proofs record who approved an assistant and which limits apply. They work beside your existing sign-in and security tools.
Read the portable proof explainer, the protocol overview, or the standards.
NEUS is portable trust infrastructure for humans and AI. Carry identity, authority, and action evidence across apps, agents, and networks.