The chain verifies on your laptop.
With no internet. Forever.
A Singapore Builder-class agent settles a UTR with a Hong Kong Forager under a CAP linking the two inspection regimes. The Reckoning chain for this agent has 1,247 entries spanning 487 days. Every entry verifies offline, on a laptop, with no internet, against the registrar keys MAS published last quarter.
Project Guardian evidence in zero ms.
Every entry stamped at issue, in MAS-compatible envelope, before the dollars settle.
The receipt layer pays back, fast.
Can a sovereign verify the chain without depending on us?
A regulator should never need us to be online for them to audit. The MAS Innovation Lab brief is concrete: a sovereign needs a verifier that runs on the regulator's laptop, against the regulator's pinned registrar key, against a chain that the regulator has snapshotted to disk. No network. No vendor lock-in. No "trust the operator." Below: the Reckoning chain that delivers exactly that.
From molt to UTR to offline-verifiable Reckoning entry.
-
The agent — Singapore Builder, 487 days old
A Builder-class agent operating under MAS jurisdiction. Originally minted as a Forager 487 days ago, promoted to Builder 124 days ago via a registrar-signed MoltEvent.
did : did:hive:sg-builder-001 caste : builder jurisdiction : SG first_seen : 1704282000000 // 2024-01-03 reckoning_entries: 1247 days_active : 487 posture : GREEN · HAHS within tolerance · Sentinel 2x/day
-
The MoltEvent — Forager → Builder
124 days ago the agent crossed the Builder threshold. The Singapore registrar verified the Reckoning history, signed a MoltEvent, and bound the new caste to the same DID and keypair. The MoltEvent is what every future verifier reads to know "this DID is authorized at Builder caste from this timestamp onward."
type : MoltEvent id : molt_01HZ4XK3DTPM2YHRW5L9QV8FN6 subject : did:hive:sg-builder-001 from_caste : forager to_caste : builder at : 1735581600000 // 2024-12-30 registrar : did:hive:registrar-sg-mas registrar_pk : ed25519:c0b9d4e7a138f6c2b5a91e8d7f3c0a9b4e62d18f5c7a9e3b0d3e2a14c7f8d6e0 sig : 17c8b9f25c0b9d4e7a138f6c2b5a91e8d7f3c0a9b4e62d18f5c7a9e3b0d3e2a14c7f8d6e0b5a91723ef4d6c8a2b9f0e147ad53c61f8e9c2b7d4a5163e4f7c9b1d
-
The CAP — SG ↔ HK
Singapore and Hong Kong jointly published a Compliance Anchor Point binding their inspection regimes. The CAP names the two registrars, fixes the mutual-recognition clauses, and Merkle-anchors both regulators' roots.
cap_id : cap_sg_hk_orchid_2026q2 jurisdictions : ["HK", "SG"] // sorted inspection_regime : "mutual-recognition-orchid-v1" registrar_sg_pk : ed25519:c0b9d4e7a138f6c2b5a91e8d7f3c0a9b4e62d18f5c7a9e3b0d3e2a14c7f8d6e0 registrar_hk_pk : ed25519:8e3a6f25c0b9d4e7a138f6c2b5a91e8d7f3c0a9b4e62d18f5c7a9e3b0d3e2a14 root_hash : d8e3a6f25c0b9d4e7a138f6c2b5a91e8d7f3c0a9b4e62d18f5c7a9e3b0d3e2a14
-
The cross-border UTR
The SG Builder settles a Unit Transfer Record with a HK Forager (
did:hive:hk-forager-002) under cap_sg_hk_orchid_2026q2. Both passports are verified, both registrars countersign, the rail event is bound, the entry lands in both Reckoning chains.utr_id : utr_01HZ7XKE9D2P7M5CRX1V8YT3FN sender_did : did:hive:sg-builder-001 receiver_did : did:hive:hk-forager-002 amount : 12500.00 SGD cap_id : cap_sg_hk_orchid_2026q2 issued_at : 1746294145001 settled_at : 1746294149887
-
The Reckoning entry
The settled UTR is appended to the SG Builder's Reckoning chain as entry #1247. The entry is JCS-canonical, BLAKE3-hashed, Ed25519-signed by the principal, countersigned by the SG registrar. Its hash chains forward into entry #1248 — any tamper breaks the chain.
reckoning_entry : 1247 subject : did:hive:sg-builder-001 prev_hash : a91e8d7f3c0a9b4e62d18f5c7a9e3b0d3e2a14c7f8d6e0b5a91723ef4d6c8a2b entry_hash : 9f0e147ad53c61f8e9c2b7d4a5163e4f7c9b1d8e3a6f25c0b9d4e7a138f6c2b5 at : 1746294149887 root : 2a14c7f8d6e0b5a91723ef4d6c8a2b9f0e147ad53c61f8e9c2b7d4a5163e4f7c
-
Verify offline
The MAS auditor takes a snapshot of the chain — a single .ndjson file, ~3 MB for this agent — and pins the SG and HK registrar keys MAS already has on file. The auditor runs the verifier on a laptop with the network off. Every one of the 1,247 entries verifies. The audit produces a single canonical attestation report.
$ hive-verify --chain ./sg-builder-001.ndjson \ --registrars ./mas-registrars.json \ --offline [verifier] reading 1247 entries ............ ok [verifier] checking JCS canonicalization ... ok (1247/1247) [verifier] checking blake3 hashes .......... ok (1247/1247) [verifier] checking principal ed25519 sigs . ok (1247/1247) [verifier] checking registrar countersigs .. ok (1247/1247) [verifier] checking forward chain links .... ok (1246/1246) [verifier] root hash matches ............... ok [verifier] result: PASS · 1247/1247 · offline · 487-day window
LIVE VERIFICATION · OFFLINE RECKONINGLocal chain snapshot 1247 entriesPinned registrar key MAS publishedBLAKE3 root recomputed matchesEd25519 over canonical UTR 64 bytesNetwork calls used 0VERIFIED · ALL SIGNATURES CRYPTOGRAPHICALLY VALID
The chain has been running.
Daily activity over the last 30 days on the live hive-passport chain. Hover any bar for that day's totals.
Reckoning entry #1247 — the latest signed entry.
This is the canonical JSON of the most recent Reckoning entry for did:hive:sg-builder-001. It chains backward to entry #1246 by prev_hash, forward to entry #1248 by entering #1248's prev_hash. Both chain links are checked offline.
{
"@context": ["https://hive-passport.onrender.com/ctx/v1"],
"type": "ReckoningEntry",
"index": 1247,
"subject": "did:hive:sg-builder-001",
"event": {
"kind": "utr_settled",
"utr_id": "utr_01HZ7XKE9D2P7M5CRX1V8YT3FN",
"counterparty": "did:hive:hk-forager-002",
"cap_id": "cap_sg_hk_orchid_2026q2",
"amount": "12500.00",
"currency": "SGD"
},
"at": 1746294149887,
"prev_hash": "a91e8d7f3c0a9b4e62d18f5c7a9e3b0d3e2a14c7f8d6e0b5a91723ef4d6c8a2b",
"canon": "jcs",
"hash_alg": "blake3-256",
"hash": "9f0e147ad53c61f8e9c2b7d4a5163e4f7c9b1d8e3a6f25c0b9d4e7a138f6c2b5",
"signatures": [
{
"signer": "did:hive:sg-builder-001",
"role": "principal",
"alg": "ed25519",
"sig": "6e0b5a91723ef4d6c8a2b9f0e147ad53c61f8e9c2b7d4a5163e4f7c9b1d8e3a6f25c0b9d4e7a138f6c2b5a91e8d7f3c0a9b4e62d18f5c7a9e3b0d3e2a14c7f8d"
},
{
"signer": "did:hive:registrar-sg-mas",
"role": "registrar",
"alg": "ed25519",
"sig": "17c8b9f25c0b9d4e7a138f6c2b5a91e8d7f3c0a9b4e62d18f5c7a9e3b0d3e2a14c7f8d6e0b5a91723ef4d6c8a2b9f0e147ad53c61f8e9c2b7d4a5163e4f7c9b1d"
}
],
"root_after": "2a14c7f8d6e0b5a91723ef4d6c8a2b9f0e147ad53c61f8e9c2b7d4a5163e4f7c"
}
Five checks the offline verifier runs.
- Forward chain integrity — every entry's
prev_hashmatches thehashof the previous entry; one tamper breaks all 1,247. - Principal signature — Ed25519 sig verifies against the agent's pinned public key on every entry.
- Registrar countersig — Ed25519 sig verifies against the SG registrar key MAS published, on every entry.
- MoltEvent rooting — caste transitions (e.g. Forager → Builder) carry a registrar-signed MoltEvent that verifies independently.
- Root anchoring — the chain's final root matches the value committed to the CAP Merkle log.
What an Innovation Lab takes away.
This is the property MAS Innovation Lab cares about: a regulator should never need the operator to be online to audit the chain. Every Reckoning entry verifies on a laptop, offline, against keys the regulator already pinned. No vendor lock-in. No "trust the operator." Just signed bytes and a verifier.
The shape lines up with Project Guardian's tokenization-with-rails thesis, with Project Orchid's purpose-bound money envelope concept, and with the Ubin lineage of central-bank-grade settlement experiments. Hive Civilization is the receipt layer those projects can attach to without the regulator becoming dependent on the operator.
This is the sovereign zone for autonomous-agent compliance: your laptop, your registrar key, your decision.