LockPending
A same-slot contender can be validated but is not made spendable while the slot lacks a settlement certificate.
Transactions
Transactions execute in the DAG, not in a mempool.
WildRoot uses a live transaction DAG as the application execution layer. Accepted transactions can become usable immediately while PoW checkpoints later anchor and finalize the resulting history.
1
Sign
The sender signs protocol fields including chain ID, sender nonce, finalized PoW height and timestamp metadata.
2
Validate
Nodes verify signatures, dependencies, timestamps, fees, nonce order and the rules implied by the finalized-height anchor.
3
DAG accept
Once admitted, the transaction can affect native or EVM live state immediately unless it is waiting on a conflict lock.
4
Activate & finalize
A verified application frontier activates after its DA threshold and becomes hard-final 60 PoW blocks later.
Canonical order
Sender intent is preserved before independent transactions are compared.
Sequential sender nonces ensure nonce N+1 cannot execute before nonce N. Dependency edges and UTXO parents also come first. Only ready, non-dependent transactions use their signed timestamp_ms, with txid as the exact-millisecond tie-break.
Transactions do not expire merely because they are old. Offline or delayed transactions are still evaluated against the current valid state and their signed protocol context when they arrive.
A
Causal dependencies
Parents, UTXOs and sender nonce relationships cannot be reordered by hash values.
B
Signed timestamp
Unix milliseconds are sender-signed and must not precede the transaction's protocol dependencies.
C
Exact-tie txid
Hash ordering is only a deterministic tie-break when independent transactions share the same millisecond.
Same-nonce conflicts
Conflicting candidates do not become spendable by racing timestamps.
WildRoot treats a sender/nonce slot as a conflict boundary. Same-sender/same-nonce contenders remain non-spendable while settlement validators decide exactly one txid.
Quorum-selected winner
The configured settlement-validator quorum signs exactly one transaction identifier for the sender/nonce slot.
Winner + conflicts
A valid certificate makes the selected winner immutable in the live DAG and marks alternatives Conflicted, independent of an older competing timestamp.
Signed context
The transaction carries the PoW context it was created against.
Every non-coinbase native transaction signs chain_id, sender_nonce and finalized_height. EIP-1559 wrappers carry WildRoot's signed finalized-height anchor through a compatibility field rather than a miner-tip market.
Native and EVM transactions share the same nonce namespace for the same sender. Different wallets can independently use nonce 0.
Timestamp unitUnix milliseconds
Arrival timeNon-consensus
Age expiryNone
Per-sender orderStrict sequential nonce
Protocol anchorSigned finalized PoW height
Canonical transaction ordering provides deterministic convergence, not guaranteed race fairness. Contracts allocating scarce rewards should use application-level mechanisms such as commit-reveal, auctions or appropriate randomness instead of assuming transaction order is a fair race.