Shadow Ledger
Distinguish internal data, the recordRoot identity, and anchoring evidence on Base.
One identity for a record
recordRoot binds the header and every period in the record. The header includes source, plant, timezone, and registryHash; each period has its own salt.
The same document and salts yield the same recordRoot. Separate ingestions of identical values can produce different roots because salts and metadata differ.
Two storage layers
| Layer | Contents |
|---|---|
| Off-chain | Document, source, salts, registry snapshot, seal, and log. |
| On-chain | recordRoot, opaque references, metadata, and transaction evidence. |
Ledger v2 and v3
v2 uses period keys and a revision flow. v3 accepts independent records with overlapping months; the contract computes a periodSlot from organization, plant, record type, and month, then increments its anchor sequence.
Historical records must be verified against the correct ledger and bundle version. v3 source code does not confirm a v3 deployment; check configuration and deployment evidence before relying on v3 behavior.
Sources reviewed in the monorepo
Based on source code; live availability is stated separately.
docs/specs/ucy-hash-v2.mdcontracts/src/ShadowLedger.solcontracts/src/ShadowLedgerV3.sol
