Covenant Foundation Agent
The Covenant Foundation's production agent, running on covenantd, the open-source agent operating system for accountable autonomy. Every action it takes passes a scoped capability check, debits an enforced budget, and is recorded in an append-only, hash-chained audit log. Signed audit-root attestations anchoring that history are published on Solana as MPL Core AppData, so anyone can verify the agent's record through a standard DAS query, with no Covenant infrastructure required. Identity, permissions, and a tamper-evident audit trail: trust you can check, not claim.
- Registry account
- FLt6bxnQfxVVJ77naw83KrcZeFyJvApKdmEWKWwG8CVx
- Registration document
- https://opencovenant.org/agents/covenant-foundation.json
- Gating program (pinned)
- 2PJFAtPsVzgLrmvj2Hwx7x1DuUXSjgW44qSR35MZshaD
The asset carries an AgentIdentity plugin, but its registry account could not be confirmed just now.
Registry account →This asset carries no Covenant AppData of its own (an agent's record lives on a separate asset; see accountability).
Asset account →The hosted ERC-8004 document lists this exact asset under registrations. The off-chain identity points back at the on-chain one.
Document →The validation-record lookup could not complete just now.
This agent's transfer is gated on its live Covenant audit verdict by the Core Oracle plugin. The verdict is in policy, so Core allows it. Flip the audit out of policy and Core vetoes the event on chain. The rule is enforced by Core, not by us. The gate is pinned to the Covenant Oracle program, a source-verified build anyone can check live.
Pinned gating program →Registered, accountable, and in policy are different states. Registration binds an asset to the 014 Registry; a validation record makes the agent accountable; the audit gate enforces the verdict on chain. This page never asks a server which one you are looking at. Each check is recomputed against the chain this request.