EVM

Ethereum-compatible tooling on WildRoot's DAG execution layer.

WildRoot exposes Ethereum-style HTTP and WebSocket JSON-RPC while executing accepted EVM transactions through the same live DAG and sender-ordering rules as native transactions.

Compatibility boundary

Familiar APIs, WildRoot consensus.

EVM wallets, Solidity development tools and applications interact through Ethereum-compatible JSON-RPC. Underneath that interface, WildRoot controls transaction admission, DAG ordering, fee settlement, data availability and finality.

EVM walletsRemixSolidityHTTP JSON-RPCWebSocket subscriptions

Default EVM endpoints

Mainnet chain ID  11915729 (0xB5D1D1)
EVM HTTP          http://127.0.0.1:17324
EVM WebSocket     ws://127.0.0.1:17325
Public explorer   https://explorer.wildrootcore.com

Shared execution model

EVM transactions are not a second ordering system.

Nonce

Shared sender namespace

Native and EVM transactions from the same sender share one sequential nonce namespace, preventing cross-interface reorder bypasses.

State

Immediate receipts and logs

Accepted DAG execution can update contract state, receipts, logs and token indexes immediately rather than waiting for a checkpoint block.

Finality

Frontier replay

Checkpointed application frontiers deterministically replay the same EVM effects before activation and later hard finality.

EIP-1559 wrapper

The priority-fee field carries protocol metadata, not a miner tip.

WildRoot has no miner-tip market. In its current EIP-1559 compatibility wrapper, the signed maxPriorityFeePerGas field carries the WildRoot finalized-height anchor used to derive the transaction's applicable protocol context.

Applications should treat WildRoot's compatibility RPC as Ethereum-shaped transport over WildRoot consensus—not as a claim that every Ethereum fee-market semantic is identical.

Check chain ID

curl -s http://127.0.0.1:17324 \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Explorer model

Native and EVM activity are visible through one chain view.

Contract transactions

The explorer API exposes contract creation and calls, method selectors, receipts, gas/fee accounting, logs, token transfers and contract creator metadata.

Real PoW anchor status

EVM transaction detail can show the real WildRoot PoW anchor, checkpoint depth and finality rather than inventing transaction-bearing PoW blocks.

Explorer model Developer interfaces