Zeq Blockchain

A ledger where every block is anchored to the Zeqond at which it was sealed. Forks are detectable in real time because time is a first-class witness.

Live app → /apps/zeq-blockchain/
Source → apps/zeq-blockchain/index.html + apps/zeq-blockchain/chain.js (≈ 780 lines)
Operators → KO42 · CS87 · ZEQ-TETHER-003
Error budget → 0.000% bit-exact block commitments

What it solves

Classical blockchains decouple time from consensus — the "time" in a Bitcoin block is an unverifiable field the miner fills in. Zeq Blockchain ties every block to the Zeqond at which it was sealed, signed by the tethered device that sealed it. Validators reject blocks whose phase_at_seal is outside the window agreed for that block height.

That simplifies three things dramatically: fork choice (pick the entangled state whose Zeqond drift is smallest), replay prevention (duplicate Zeqonds are detectable), and post-hoc audit (every state transition is time-anchored).

The entangled state itself is a minimal Merkle-DAG with Ed25519 signatures. CS87 provides the key-material floor; ZEQ-TETHER-003 lets a multi-device validator set sign quorums.

The math — 7-step Wizard applied

Step	Decision
1. Prime	KO42 mandatory
2. Limit	`CS87` + `ZEQ-TETHER-003` + KO42 = 3
3. Scale	Block cadence 1 per 16 Zeqonds ≈ 12.4 s
4. Precision	Hamming = 0 on block hashes
5. Compile	Master Equation
6. Execute	Functional Equation
7. Verify	Block-header reproducibility across validators

Verbatim formulas:

KO42.1 — ds² = g_μν dx^μ dx^ν + α sin(2π · 1.287 t) dt²
CS87 — Ω(x) = min{|p| : U(p) = x}
ZEQ-TETHER-003 — B_sib = ∑_k e^(i·φ_k) |sibling_k⟩

Runnable worked example — seal + verify

# 1. Seal a block
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": {
      "op": "seal_block",
      "parent_hash": "0x...",
      "txs": ["tx1", "tx2", "tx3"]
    }
  }'

Expected:

{
  "block_hash": "0x...",
  "height": 10421,
  "phase_at_seal": 0.2231,
  "zeqond": 1745124300.174,
  "validator_quorum": 7
}

# 2. Verify the block
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":{"op":"verify_block","block_hash":"0x..."}}'

Expected:

{"verified": true, "error_pct": 0.000}

Extend it

Light client: a mobile wallet only needs to track Zeqonds + quorum signatures to verify inclusion.
Cross-chain anchor: publish a Zeq block hash to another chain for auditable time bridging.
Hardware validator: run a validator on a Zeq Pulse-attested node; signatures are tamper-evident.

Seeds

Stake without finance — Zeqond-weighted consensus doesn't need a token; compute contribution is the stake.
Forensic ledger — because Zeqonds are witnessable after the fact, a historical chain can be audited even if validators churn.
Zero-knowledge compliance — commit ZK proofs of regulatory-policy compliance to each block.

Papers

Zeq framework paper — DOI 10.5281/zenodo.15825138
Zeq paper — DOI 10.5281/zenodo.18158152

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

What it solves​

The math — 7-step Wizard applied​

Runnable worked example — seal + verify​

Extend it​

Seeds​

Papers​