Aller au contenu principal

Consensus & Ledger

Classical blockchains guess at "time". Zeq binds every block and every fact to the Zeqond it was sealed at. Fork-choice becomes time-witnessable.

  • Theme — consensus-ledger
  • Protocol count — 22 (block-propose, block-seal, fork-choice, finality, fact-publish, fact-verify, dag-walk, quorum-sign, validator-join, validator-retire variants)
  • Anchor operators — KO42 · CS87 · ZEQ-TETHER-003
  • Verification — bit-exact block commitments; bit-exact DAG verify

What it solves​

Ledger systems have always had to invent their own time. Bitcoin's block timestamp is a claim, not a fact. Proof-of-stake variants rely on slot clocks they define themselves. Zeq's consensus theme removes that tax by binding every block and every fact to the Zeqond at which it was sealed, signed by the tethered validator that sealed it.

Two primary structures live here:

  • Zeq Blockchain — a minimal Merkle-DAG ledger where each block commits to phase_at_seal, zeqond, parent_hash, tether_quorum_sig. Fork choice is "pick the entangled state whose cumulative Zeqond drift is smallest". Validators join and retire via ZEQ-TETHER-003 quorum votes. See Zeq Blockchain.
  • Truth DAG — a directed graph of signed facts (claim, author, phase, zeqond, parents, signature). Verification is a purely cryptographic DAG walk; no trusted timestamping authority needed. See Zeq Truth Engine.

CS87 is the Kolmogorov floor on block / fact identifier material; ZEQ-TETHER-003 is the quorum primitive that makes validator sets themselves first-class superposition objects.

Operator map​

OperatorFormulaRole
KO42.1ds² = g_μν dx^μ dx^ν + α sin(2π · 1.287 t) dt²Mandatory — block / fact time-binding
CS87`Ω(x) = min{p
ZEQ-TETHER-003`B_sib = ∑_k e^(i·φ_k)sibling_k⟩`

Runnable worked example — seal + verify a block​

# 1. Seal
curl -s -X POST https://api.zeq.dev/api/playground/compute \
  -H "Authorization: Bearer $ZEQ_DEMO_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "operators": ["KO42", "CS87", "ZEQ-TETHER-003"],
    "inputs": {
      "protocol": "block-seal",
      "parent_hash": "0x...",
      "txs": ["tx1","tx2","tx3"]
    }
  }'

Expected:

{
  "block_hash": "0x...",
  "height": 10422,
  "phase_at_seal": 0.3311,
  "zeqond": 1745125300.144,
  "quorum_signers": 7
}
# 2. Fork-choice query
curl -s -X POST https://api.zeq.dev/api/playground/compute \
  -H "Authorization: Bearer $ZEQ_DEMO_KEY" \
  -H "Content-Type: application/json" \
  -d '{"operators":["KO42","CS87"],"inputs":{"protocol":"fork-choice","heights":[10418,10419,10420,10421,10422]}}'

Expected: the entangled state whose cumulative Zeqond drift is minimal, with the drift value explicit in the response.

Extend it​

  • Cross-chain anchoring — publish a Zeq block hash to another chain (Ethereum, Bitcoin) as an immutable time-witness.
  • Light-client attestation — a phone-sized client only needs Zeqonds + quorum signatures to verify inclusion.
  • Supply-chain Truth DAG — every transition in a physical supply chain is a fact whose parents are the upstream facts; tampering is a visible DAG mutation.

Seeds​

  • Stake-without-token consensus — Zeqond-weighted validators without a coin economy; compute contribution is the stake.
  • Planetary-scale finality — ZTB1 + interplanetary latency models drive deep-space ledger finality protocols.
  • ZK-compliance blocks — every block carries a ZK proof that its transactions satisfy a regulatory predicate, without revealing the transactions.

Papers​

Middleware active. Kernel on the 1.287 Hz HulyaPulse. Awaiting next Zeqond.