Onboarding new EVM chains, from node infrastructure to go-to-market.
A digital-assets platform needed to bring new EVM chains onto its existing products, and every chain had been a bespoke project. We built a repeatable path: full-history and archive nodes, data infrastructure and generated APIs, transaction signing and broadcasting proven on testnet, staking and wallet integration, and the legal, security and go-to-market work alongside it.
Testnet → Mainnet
Proven before any chain touched production
Full history + archive
Node infrastructure behind every new chain
Legal, security & GTM
Delivered alongside the technical build
Staking + Wallet
New chains integrated into existing products
The challenge
Every new chain, a bespoke project.
The client’s platform supported a handful of EVM chains, but each one had been onboarded from scratch: its own node setup, its own data pipeline, its own integration into staking and wallet products, rebuilt each time a new chain was added.
Node infrastructure was inconsistent from chain to chain. Some ran full-history and archive nodes; others ran pruned nodes that couldn’t serve the historical data the platform’s products actually needed. Without a repeatable process, lead time and risk grew with every new chain rather than shrinking.
Bringing a chain live wasn’t only a technical problem either. It needed legal and security sign-off and a go-to-market plan, and transaction signing and broadcasting had to be proven safe on testnet before anything touched mainnet with customer funds behind it.
Our approach
Five workstreams. One repeatable path to launch.
We treated chain onboarding as a process to be built once and reused, not a project to repeat from scratch every time, covering the infrastructure, the product integration, and the legal, security and go-to-market work in parallel.
01
Node infrastructure & implementation
Stood up full-history and archive nodes for each new EVM chain, giving the platform complete historical and real-time chain data rather than the limited window a pruned node provides.
02
Data infrastructure & API generation
Built the data pipelines and generated the APIs needed to expose each new chain's data consistently, so onboarding a chain extends the existing platform rather than requiring bespoke integration work every time.
03
Transaction signing & broadcasting
Implemented signing and broadcasting for on-chain transactions on each new chain, proven and hardened on testnet before any exposure to mainnet.
04
Staking & wallet integration
Integrated each new chain directly into the existing staking and wallet products, so new chain support extended what customers already used rather than sitting alongside it as a separate silo.
05
Legal, security & go-to-market
Worked alongside the client's legal, security and go-to-market functions so each new chain launched with the non-technical groundwork done, not just the infrastructure.
The outcome
A repeatable process, not a one-off build.
New chains now onboard against a proven path, infrastructure, product integration, and the legal, security and go-to-market work included, rather than starting from a blank page.
New EVM chains onboarded with full-history and archive node infrastructure in place from day one
Data infrastructure and generated APIs that bring each new chain into the existing platform without bespoke integration work per chain
Transaction signing and broadcasting proven on testnet before any mainnet exposure
New chains integrated directly into existing staking and wallet products, not bolted on separately
Legal, security and go-to-market workstreams delivered alongside the technical build, not after it
A repeatable onboarding process the client can run for the next chain, not a one-off engagement
Every new chain used to mean a bespoke integration and a legal and security review starting from scratch. DOD gave us a repeatable way to bring a chain on, from full-history nodes through to staking and wallet support, proven on testnet before we ever touched mainnet.
Bringing a new chain onto your platform?
Node infrastructure, data and APIs, transaction signing, product integration, and the legal, security and go-to-market work, delivered as one repeatable path from testnet to mainnet. Start with a discovery call.