Per-block target adjustment
The development rule targets 60-second checkpoints and clamps the observed adjustment interval to a narrow 59–61 second range before calculating the next target.
Consensus
PoW checkpoints secure history without becoming the transaction queue.
WildRoot PoW blocks are coinbase-focused checkpoints. The live DAG executes transactions; checkpoint history supplies rewards, availability acknowledgements, protocol height and hard finality.
Target interval60 seconds
Subsidy1 WR forever
Coinbase maturity60 blocks
PoW digest512-bit
Checkpoint chain
Blocks carry PoW history and compact application commitments.
A PoW block can commit the current application frontier using a compact DAG/state commitment while the ordered transaction list is synchronized separately. Missing sidecar or transaction-body data does not make an otherwise valid PoW block invalid; instead, a node without certified application data remains application-unsynchronized until it can verify the frontier.
PoW headerheight · previous checkpoint · target · timestamp · coinbase
Application commitmentDAG root · transaction count · fee/gas commitment fields
FrontierCertificate sidecarOrdered txids synchronized separately and replayed deterministically
Data availability
Non-empty frontiers must prove that their application data is available.
1
Proposal
A checkpoint proposes a non-empty application frontier commitment.
2
12-block window
The current design bounds the availability acknowledgement period to 12 active-chain PoW blocks.
3
6 acknowledgements
The frontier activates after the required active-chain PoW acknowledgement threshold and local deterministic replay.
4
60-block finality
Application hard finality is reached 60 PoW blocks after successful activation.
A proposal that does not obtain the required acknowledgements within the bounded window expires rather than forcing nodes to invent unavailable application state.
Fees
Protocol gas, not a miner-tip auction.
The base fee starts and floors at 10,000 Gwei. Its maximum change is capped at 1% per verified application frontier. Native transfers use a deterministic base plus canonical-byte charge; EVM execution charges actual REVM gas together with signed-envelope and WildRoot metadata byte gas.
Fee accounting is enforced by protocol rules and replayed as part of deterministic application verification.
Base-fee minimum10,000 Gwei
Maximum adjustment1% per verified application frontier
Native transfer gas
21,000 + 4 × canonical transaction bytesMiner tip marketNone
Network fee address
wrpq1a80147c9e64036ccdf5cd1ab3cdc6140fae09f6cbcd87fd9f87e74f8441d17aa1d52afd637241ae28db699a46cca3c48abd8aec18d84e72b6f3281a0b07a6f62One 60-block boundary
PoW/coinbase hard finality and coinbase spend maturity use the same 60-block depth, while application state becomes hard-final 60 blocks after its frontier activation.
Height-anchored evolution
The current pre-production chain activates its canonical ruleset from height 0. After production freeze, consensus changes are intended to use explicit activation heights rather than rewriting history.