Skip to content
Documentation/Technical reference

Smart contracts & versions

Contract roles, commitBatch, markVerified, and ledger compatibility.

On this page

Separate on-chain responsibilities

The contract uses AccessControl and ERC-2771. Issuer wallets are bound to orgRef; a relayer funds the transaction while valid forwarded calls retain issuer identity.

ISSUER_ROLE commits records; VERIFIER_ROLE records verification; CHECKPOINT_ROLE writes checkpoints. The admin manages roles and configuration. These roles are not API read permissions.

Core writes

FunctionPurpose
commitBatchCommit recordRoot identities subject to contract limits.
markVerifiedBind commitmentId, recordRoot, and receiptHash.
checkpointAnchor the Merkle root of organization log heads.
registerIssuerWalletBind a wallet to orgRef and grant issuer authority.

Check the right address and version

Bundle v1 corresponds to ledger v2; current bundle v2 code supports ledger v3. v3 exposes periodAnchorCount and sequences for month-slot history.

Do not trust a ledger address merely because a bundle declares it. Independently confirm chainId, address, and deployment block; these docs do not assert a live v3 address.

Sources reviewed in the monorepo

Based on source code; live availability is stated separately.

  • contracts/src/ShadowLedger.sol
  • contracts/src/ShadowLedgerV3.sol
  • docs/adr/ADR-0034-independent-commits-provisional-months-ledger-v3.md