Client engagement
Phoenix Solutions LLC · RabbitChain
Root Digit supported a 36-month blockchain infrastructure programme spanning consensus, parallel transaction execution, validator operations, EVM compatibility, protocol security and developer tooling.
The problem
Phoenix Solutions needed a Layer 1 network that could sustain high transaction volume and sub-second finality without making consensus failure, validator recovery or transaction ordering opaque.
The network also had to preserve EVM compatibility, low transaction cost and familiar developer tooling while treating protocol security, node operations and upgrade control as part of the same system.
Why it was difficult
These operating and governance conditions determined what a credible solution had to achieve.
01
Parallel execution is useful only when conflicting state access is detected and resolved correctly. Benchmarks therefore had to account for realistic contract interaction rather than independent transfers alone.
02
A 0.3-second finality objective still required Byzantine-fault-tolerant agreement, deterministic validator rules and a recovery path for failed or unavailable block producers.
03
Solidity contracts, MetaMask, Hardhat, Truffle and familiar RPC behaviour had to work without teams learning a separate development model or depending on undocumented chain-specific exceptions.
04
Key management, consensus safety, node operations, networking, bridge behaviour, MEV exposure and upgrade controls all formed part of the attack surface.
The solution
Root Digit engineered an EVM-compatible Layer 1 combining DPoS-VP consensus, Byzantine-fault-tolerant agreement, a 21-producer validator model and conflict-safe parallel transaction execution.
The solution included protocol and key security, validator operations, RPC and Solidity compatibility, explorer and SDK services, testnet tooling and application primitives—allowing performance to be evaluated together with safety and operability.
How we did it
The workstreams below show how the solution was designed, built and controlled.
01
The DPoS-VP model combined 21 block producers with validation pools of delegated participants. BFT agreement, producer rotation and failover rules were designed together so performance changes could be assessed against fault tolerance.
02
Transactions were scheduled across independent state paths, with conflicts detected before commit. The design targeted 5,000-plus TPS, 0.3-second finality, five-second block production and a transaction fee near $0.001.
03
Threshold-signature controls, hardware security modules, formal review of critical components and external audits were incorporated into the operating model rather than treated as a pre-launch checklist.
04
Compatibility work covered the execution environment, RPC interfaces, wallets and established Solidity toolchains. Root Digit also delivered SDKs, explorer services, a testnet faucet and technical documentation.
05
Core services included oracle integration, swaps, liquidity primitives and flash-loan support, with controls for transaction ordering and MEV exposure considered at protocol level.
System design
01
Block-producer election, validation pools, BFT voting and failover determined which history could be committed and how the network recovered from unavailable participants.
02
EVM-compatible execution, parallel scheduling and conflict handling turned ordered transactions into a deterministic state transition across every validating node.
03
Peer networking, validator deployment, telemetry, explorer services and upgrade procedures provided the operational controls required to run and observe the protocol.
Delivery sequence
Phase 01
Consensus, validator incentives, network assumptions, state model and measurable performance and safety criteria.
Phase 02
Consensus nodes, EVM execution, parallel scheduler, RPC compatibility and initial validator tooling.
Phase 03
Load and fault testing, key controls, formal review, external audits and operational runbooks.
Phase 04
SDKs, documentation, explorer, faucet, application primitives and support for network participants.
Outcomes and evidence
Network-scale and ecosystem figures are based on Phoenix Solutions programme records. Root Digit has not independently audited public-chain activity; protocol scope, architecture and delivery facts reflect the engineering engagement.
Sustained production performance reported by the client.
Reported production finality.
Reported across 24 months of operation.
Client-reported network record.
Engagement conclusion
RabbitChain’s delivery was treated as a full protocol operating system: consensus, execution, keys, tooling and recovery procedures were designed as one system. That is what allowed performance objectives to be evaluated without separating them from safety and operability.
Start a conversation
We use cookies to enhance your browsing experience, serve personalized content, and analyze our traffic. By clicking "Accept All", you consent to our use of cookies. You can also choose "Necessary Only" to limit cookies to essential website functions only. Learn more