LIQUA CHAIN
single-node reference · BLAKE3 PoW · continuous reward decay · ephemeral keypair claims⚠ SINGLE-NODE REFERENCE — NOT A REAL L1
This is a working demonstration of the spec's mechanics, not the production chain.- One node. No P2P. No multi-node consensus. Anyone running this can fork it at will.
- BLAKE3 PoW stands in for the spec's RandomX (faster to demo, same mechanism).
- No transaction execution yet — pure block production + reward emission.
- RPC at
http://localhost:8765./explorer.html?rpc=http://localhost:8765reads it as a generic chain. - Phase 4 in /roadmap.html scales this to a real network — 12–18 months, senior Rust+Sol team, $1.5–2.5M.
BLOCK HEIGHT
—
blocks mined
DIFFICULTY
—
bits leading zero
AVG BLOCK TIME
—
target 10s
CHAIN AGE
—
since genesis
EMISSION → CAP
— / 100,000,000 LIQUA · —
▶ REWARD DECAY R(t) = R_max · e^(−λt)—
theoretical curve · R_max=5 LIQUA · half-life 30s
recent blocks (elapsed → reward)
▶ BLOCK DETAILclick a block to inspect
— click a block in the table below to see its full header, hash, miner address, ephemeral reward keypair, and elapsed-time decay —
▶ RECENT BLOCKS—
| # | hash | elapsed | reward | diff | nonce | miner (ephemeral) |
|---|---|---|---|---|---|---|
| — waiting for blocks — | ||||||
⌬ Molecular framing.
Each block is a successful cellular metabolic event — a "cell" (one mining hash run) producing output (a hash) the network accepts.
The reward decay enforces a "fast twitch" pressure: late blocks earn less, like a cell that takes too long to express the right protein.
Reward goes to an ephemeral keypair derived from the parent block hash + this node's id (spec §4c).
On the real L1, miners would claim this on L2 only after
K=12 confirmations — that's the reorg-safety gate built into the design.
The chain you're watching here demonstrates the mechanism. The production version (Phase 4) replaces BLAKE3 with RandomX and adds the P2P + consensus + bridge layer.