Clockchain Documentation (v1)
BinuteCoin / 12 SWT Agents — The Proof-of-Time Anchor Ledger.
1) What is Clockchain?
Clockchain is a 12-agent (SWT) anchor ledger designed to finalize hash commitments with BFT-style quorum.
- Anchor-first: anchors hashes (commitments), not large payloads.
- 12 Identical Agents: AGENT-1 to AGENT-12 distributed across SWT zones.
- Proof-of-Time: Leader rotates automatically by HS (Harmony Segment).
- Threshold Finality: Requires T=8/12 validator votes to become FINAL.
Clockchain is used by Timeverse to create durable, independently verifiable audit trails for TSAE receipts, Layer-0 ledgers, and Trust Anchors.
2) The anchor-first design
Anchoring only hashes keeps the ledger lightweight, scalable, and privacy-preserving. No content bytes or GPS data are ever stored on-chain.
Rule of thumb
3) Core objects
3.1 SecProf envelope
Timeverse uses Security Profile envelopes (Ed25519 + canonical JSON) for TSAE receipts, Anchor messages, and T-WATCH witnesses.
3.2 DATA_ANCHOR transaction
The main on-chain primitive. It carries the hash commitment and the ORCH-signed envelope.
// Binding rule (MUST)
data_hash == sha256(canonical(anchor_envelope))3.3 Blocks and finality
A block is FINAL when it meets the BFT threshold (typically 8/12 validator signatures).
4) Proof-of-Time leader schedule
Clockchain uses a deterministic schedule mapping the current HS to a leader SWT.
leader_swt := ((hs - 1 + 6) mod 12) + 1
Verifier rule (MUST)
leader_agent_id does not match the expected agent for the block's hs_leader.5) Offline verification
Given a data_hash, you can verify everything without trusting a server.
Fetch data
Get anchor detail from API, pinned keys from /keys, and BFT threshold from /status.
Verify hash binding
Recompute recomputed = sha256(canonical(anchor_envelope)) and check it matches data_hash.
Verify ORCH signature
Verify the SecProf envelope signature using the pinned ORCH key.
Verify witness (optional)
If T-WATCH witness exists, verify signature and check binding to data_hash.
Verify FINAL
Check that bft_votes >= bft_threshold.
6) Trust Anchors on Clockchain
Clockchain does not need custom "trust" transaction types. It uses an evidence-first strategy where trust evidence is stored off-chain and only the commitment is anchored via DATA_ANCHOR.
7) Fees / BNC (overview)
BinuteCoin (BNC) is the utility layer used for anchoring fees and validation incentives. Token economics are deployment policies and are not strictly required for proof verification.
9) Common misunderstandings
"Clockchain stores the content"
No. Clockchain anchors hashes only. Content stays in Layer-0 or private storage.
"This is quantum entanglement"
No. Timeverse uses deterministic coordination and signed evidence. No quantum state is transported by Clockchain.
10) Minimal glossary
HS: 1..12 segment index
ticks: integer resolution R per cycle
TSAE: signed evidence receipt
Anchor envelope: ORCH-signed SecProf container
Witness: optional T-WATCH signed envelope
FINAL: block meets BFT threshold votes