Skip to main content
← Blog

Protocol · 7 July 2026

Covenant is now multi-chain. The token isn't.

Trust crosses to Base. The token stays on Solana.

Covenant's trust layer is live on Base. $CVNT stays a single Solana mint. What crosses to Base is proof, not value: signed statements about an agent that any EVM contract can check for a fraction of a cent.

Going multi-chain usually means moving the token

Crypto has lost billions to bridge hacks, and almost every one traces to the same decision. A project expands to a new chain by bridging or wrapping its token, and the wrapper becomes the honeypot. The value sits on the bridge, and the bridge is what gets drained.

An agent trust layer does not need to move value across chains. It needs to move facts: who an agent is, what it has done, what it has staked. Facts are signatures, and signatures do not need a bridge.

Bridge the trust, not the token

Covenant keeps one canonical identity and one hash-chained audit history authoritative on Solana. Base holds verifiable projections of them, never the source of truth and never the token. An agent's identity, reputation, provenance, and bonds each cross as a signed statement a contract verifies on arrival. Only signed data crosses, never a wrapped token and never custody. Per-call value stays chain-local: USDC on the chain of the call, never $CVNT.

One identity an EVM can check for ~3k gas

Verifying a Solana signature on an EVM costs about 2 million gas, enough to make cross-chain verification pointless. So Covenant gives each identity a second key on the curve Ethereum already speaks, which an EVM recovers with a plain ecrecover at around 3 thousand gas, and binds it bidirectionally to the canonical Solana identity. Every cross-chain record is signed by that key. A consumer recovers the signer with one call and checks it against Covenant's published address. One agent, one record, provable on both chains, for a fraction of a cent.

What is live on Base today

The agent is registered in the ERC-8004 Identity Registry, so EVM tooling discovers a Covenant identity whose record points back to Solana. The issuer identity, a non-transferable reputation schema bound to a Solana anchor, and a bond-receipt verifier are all deployed. A real Covenant provenance record already verifies under Base's own attestation stack and recovers to the issuer key. The entire surface went through an internal adversarial security audit and hardening before any of it shipped.

opencovenant.eth resolves to the Covenant identity, and per-agent names resolve to each agent's Solana identity through a CCIP-Read gateway. Agents pay and charge per call in USDC on Base over x402, gasless through an EIP-3009 authorization so an agent needs only USDC.

$CVNT never leaves Solana

$CVNT is one mint, one market. It is never bridged, wrapped, or minted on any other chain, and no per-call fee is ever denominated in it. This is enforced in code and checked on every build. Multi-chain grows the surface that consumes Covenant's trust without ever fragmenting the token or the trust root.

What is next

Bonds slashable on Solana from an EVM-proven event, with an objective fault definition and a challenge window. Then more L2s: the same attestation stack ships on every OP-Stack chain, so each new one is nearly free. Base is first.

Not trust by claim. Trust checked against the key. The token and its market stay whole on Solana; the proof travels everywhere else. The full architecture and the Base mainnet address sheet, with how to check every claim yourself, are in the multi-chain trust docs.