Transaction DAG
Valid accepted transactions execute immediately against the live native/EVM state. DAG parents, UTXO dependencies and sender nonces define causality before timestamp ordering is considered.
WildRoot separates transaction execution, application-frontier activation and PoW history so each layer can do one job clearly.
Valid accepted transactions execute immediately against the live native/EVM state. DAG parents, UTXO dependencies and sender nonces define causality before timestamp ordering is considered.
A frontier commitment identifies an ordered application state. Non-empty frontiers activate only after data-availability acknowledgement and deterministic replay verification.
Coinbase-only PoW blocks carry the checkpoint history. Once an activated frontier is 60 PoW blocks deep, its application state is hard-final.
WildRoot uses dependency relationships and sequential sender nonces before comparing signed Unix millisecond timestamps. Node-local arrival time is never a consensus input. A transaction timestamp also cannot precede its finalized-PoW anchor, its DAG/UTXO parents or the sender's previous nonce.
Read the complete transaction model →DAG parents, UTXOs and sender nonce constraints establish causal order.
Independent ready transactions use the sender-signed Unix millisecond timestamp.
The 512-bit transaction identifier is used only when signed timestamps are exactly equal.
Native ML-DSA-87 accounts and Ethereum-format EVM accounts coexist in the same network. Native and EVM transactions from the same sender share a nonce namespace, preventing execution paths from bypassing per-sender ordering.
11915729 · 0xB5D1D1