Why WildRoot

A chain should not have to choose between responsive applications, proof of work, familiar tooling and operator-grade infrastructure.

WildRoot is built around a simple separation: community consensus makes application state irreversible; proof of work checkpoints that history and secures mining. Around that core, the project adds EVM compatibility, native ML-DSA-87 accounts, predictable gas rules, exchange/custody APIs and a complete self-hosted software stack.

The problem

Most application tradeoffs come from making one mechanism do every job.

Block production, application ordering, mining rewards, wallet compatibility and data indexing have different operational needs. WildRoot does not force all of them into one timing loop.

Block cadence is not the UX clock

A 60-second PoW target can be useful for mining and checkpoint history without forcing every payment, contract call or application interaction to wait for a block.

Compatibility is an interface, not consensus

WildRoot supports Ethereum-shaped tooling where it helps developers, while preserving its own DAG, community sequence locks, fee rules and PoW checkpoint semantics underneath.

Operations need first-class primitives

Exchanges and custodians need deterministic cursors, high-rate address creation, crash-safe wallet files, indexed histories and idempotent retries—not only a generic account RPC.

What is different

WildRoot's design choices are deliberate.

NeedCommon architectural pressureWildRoot approachWhy it matters
Fast irreversible application stateWait for block inclusion / confirmation depthFull-roster community sequence lock creates application Trust immediately after verificationApplication finality is not coupled to the 60-second PoW interval
Proof of workMake miners serialize every application actionCoinbase-only PoW checkpoints commit the already-Trusted prefixMining stays independent from application responsiveness
EVM adoptionFork Ethereum semantics wholesaleEthereum-compatible RPC/envelopes over WildRoot consensusFamiliar tooling without giving up the native design
Native account securityReuse only secp256k1-style accountsML-DSA-87 native wrpq1 accounts plus separate 0x compatibility accountsPost-quantum native signatures can coexist with today's EVM ecosystem
FeesPriority-fee auction pressureDeterministic protocol base fee; maxPriorityFeePerGas is metadata, not a miner tipApplications can reason about protocol charging without a tip market
Contract transparencyDepend on a centralized explorer source databaseCreator-signed source bundles can live in canonical transaction historySource remains reconstructable from canonical chain history
Why people can actually adopt it

The migration path matters as much as the protocol idea.

EVM teams

Keep familiar development tools

Solidity, REVM execution, HTTP/WebSocket JSON-RPC, receipts, logs, subscriptions and Ethereum-format addresses give existing EVM teams a familiar surface.

Exchanges

Credit by irreversible sequence

listtrustedtransactions exposes a monotonic community sequence cursor that can be committed atomically with customer credits and replayed after restart or WebSocket loss.

Custody

Generate addresses without rewriting history

The binary wallet appends address batches with one durability barrier and maintains direct address-to-derivation indexes. The format supports derivation indexes up to 100,000,000.

Users

Native and EVM identities in one desktop

Multiple encrypted wallets can stay loaded, native and 0x addresses coexist, backup/restore uses explicit files, and recovery material remains separately available.

Miners

A real mining economy remains

WildRoot preserves PoW, Stratum, CPU/GPU mining, CUDA/OpenCL support, a 1 WR perpetual subsidy and a 60-block maturity rule.

Infrastructure

Self-host the whole stack

Daemon, GUI with built-in Explorer, CLI, miner and integration interfaces can run without a centralized application server being part of consensus.

A real tradeoff, stated plainly

Community Trust is unanimous and intentionally fails closed.

Mainnet community membership is a small DNSSEC-published endpoint roster, not stake weight or miner voting. Every pinned roster member must sign the same next sequence. If a required member is unavailable, Trust stops rather than allowing separate partitions to create conflicting histories.

That choice prioritizes one irreversible application history over partition availability. WildRoot exposes the model openly because adoption depends on understanding the actual trust and availability boundary.

Membership sourceDNSSEC-validated community endpoint roster
Application decisionUnanimous full-roster lock
Application finalityImmediate after valid lock + local execution
Partition behaviorFail closed
PoW relationshipIndependent later checkpointing