Skip to main content

DOFProofRegistry

Every governance decision generates a keccak256 proof hash that is batched into a Merkle tree and attested on-chain via DOFProofRegistry.
The old contract DOFValidationRegistry at 0x88f6043B091055Bbd896Fc8D2c6234A47C02C052 is deprecated. Do not use it. The canonical contract is DOFProofRegistry.
Current attestations: 30+

DOFProofRegistry — Deployment Table (9 chains)


ERC-8004 Identity Contracts — Tempo Mainnet

DOF agent identities (DOFIdentityRegistry + DOFReputationRegistry) are also deployed on Tempo Mainnet (chain ID 42431). These are separate from DOFProofRegistry and handle agent registration and reputation scoring under the ERC-8004 standard. Total chains with DOF contracts: 9 (8 DOFProofRegistry + 1 Tempo ERC-8004)

Environment Setup


Writing an Attestation


Verifying On-Chain (Anyone)

No DOF installation required:
Or via Snowtrace Explorer: https://snowtrace.io/address/0x154a3F49a9d28FeCC1f6Db7573303F4D809A26F6

Agent Trust Scores

Agents are identified by ERC-8004 token ID (not wallet address):

Proof Chain


Formal Verification

How proof hashes are generated

Z3 API Reference

ProofResult states and TransitionVerifier