Skip to content
Magma Devs
Solutions / New Chain Listings

Launch the next blockchain. Don't rebuild the infrastructure beneath it.

Every new network adds interfaces, provider integration and operational work. Expand across 284 blockchain networks using Magma-managed RPC access, your own providers and private nodes, or a hybrid of both. Magma helps configure supported connections and agreed operations; network inclusion and onboarding scope follow your package.

More blockchain coverage. Less infrastructure to build and maintain.

  • 284 Supported Blockchain Networks
  • EVM and non-EVM
  • Bring your existing providers
Illustrative onboarding workflow. Each chain uses its supported RPC interfaces and configured endpoints. Production readiness requires validation.
The challenge

Your product team wants the next chain. Your infrastructure team gets another project.

For an exchange, custodian, or wallet platform, expanding blockchain coverage is essential to staying competitive.

But every new chain adds more work behind the scenes.

Someone must find suitable RPC endpoints, understand the network's interfaces, connect providers, configure routing behavior, test responses, monitor node health, and prepare for incidents.

And once the chain is live, your team owns that infrastructure indefinitely.

Multiply this work across dozens of mainnets, testnets, and different blockchain architectures, and network expansion can become a growing operational burden.

Different networks, different interfaces

Ethereum, Bitcoin, Solana, Cosmos, and other ecosystems expose different methods, interfaces, and behaviors.

One integration approach does not automatically fit every chain.

More providers to manage

New networks introduce additional upstream endpoints, rate limits, service agreements, health checks, and failure modes.

Ongoing maintenance

The work continues after launch. Providers degrade, chain specifications change, networks upgrade, and monitoring must remain reliable.

Adding a blockchain should expand what your product can offer, not multiply the infrastructure your engineers have to maintain.

The Magma approach

Different blockchains. One operational foundation.

Smart Router separates chain-specific RPC definitions from the infrastructure that serves the requests.

Rather than building a new routing and reliability system for every blockchain, your team can reuse a common infrastructure layer while keeping each network's actual RPC behavior intact.

  1. 01Chain Spec

    Chain-specific definitions

    Smart Router uses JSON chain specifications to describe supported RPC methods, interfaces, request behavior, and blockchain-specific routing requirements.

    These specifications let the router understand a network without requiring custom orchestration code for every chain.

  2. 02Provider Integration

    Your existing providers

    Connect the RPC providers, private nodes, and supported interfaces that your infrastructure already uses.

    Magma operates above those upstreams instead of requiring you to replace them with a single vendor.

  3. 03Reliability Layer

    Reusable reliability

    Apply provider health monitoring, routing, failover, caching, and configurable validation where supported by the chain and method.

    The same orchestration platform can serve multiple networks while respecting their differences.

  4. 04Production Operations

    Engineering and operational support

    Magma engineers can help with chain configuration, provider integration, endpoint validation, and deployment.

    With managed infrastructure, Magma can also operate the routing layer, monitoring, and upgrades as part of the service.

Your application still handles each blockchain's business logic. Magma helps you avoid rebuilding the infrastructure responsible for connecting to it.

See how it works

A new network doesn't need a new RPC infrastructure stack.

Smart Router uses blockchain specifications to describe how supported networks communicate.

For an existing supported network, the operational task is connecting suitable endpoints and configuring the service.

For a network not yet in the catalog, Magma can help define the chain specification and validate its integration.

Ethereum Mainnet

Supported interfaces for this network:

JSON-RPC

Illustrative configuration flow. Actual onboarding requirements depend on the network, RPC providers, interfaces, and deployment environment.

Read how chain specs work
Beyond one blockchain family

Because enterprise blockchain infrastructure doesn't stop at Ethereum.

Many blockchain infrastructure products are built primarily around EVM-compatible networks.

But enterprise custody, exchanges, and wallet platforms often operate across very different blockchain ecosystems.

Smart Router supports multiple chain families and RPC interfaces through a shared orchestration architecture.

ethereumarbitrumoptimismbasepolygon

EVM networks

Ethereum, major L2s, and other compatible networks.

Common interface: JSON-RPC.

JSON-RPCRESTTendermintgRPC

Mainnets in this family include Arbitrum, Arbitrum Nova, Avalanche, Avalanche C-Chain, Avalanche P-Chain, Base. Methods and add-ons vary by chain.

Same Smart Router architecture

One operational platform does not mean pretending every blockchain works the same way. It means managing their differences without multiplying your routing infrastructure.

Business impact

Spend less time integrating infrastructure. More time launching what customers want.

Move faster on network expansion

Build on a library of supported chain definitions and reuse the routing infrastructure you already operate.

Your team can focus on the product and business logic specific to the new network.

Reduce long-term operational overhead

Avoid maintaining a different provider orchestration system for every blockchain.

Keep provider connectivity, routing, and health visibility under a shared operational model.

Keep your options open

Use providers that fit each blockchain's needs, including specialized vendors and private nodes.

You are not forced into one RPC vendor relationship as your network coverage grows.

The goal is not simply to support another chain. It's to make the next chain easier to operate than the last.

Multi-chain infrastructure at enterprise scaleFireblocks

Supporting more than 100 blockchain networks is an infrastructure challenge. Fireblocks knows it.

Fireblocks provides institutional digital asset infrastructure across more than 100 blockchain networks.

Supporting this breadth of networks creates demanding requirements for RPC availability, performance, data accuracy, and operational visibility.

Fireblocks uses Magma Smart Router above its existing RPC providers and internal infrastructure to manage routing, recovery, and observability across its blockchain environment.

Rather than replacing Fireblocks' providers, Magma adds a common reliability layer across the infrastructure it already operates.

According to Magma's published Fireblocks case study, the initial Smart Router integration into Fireblocks' environment was completed in a single onboarding session.

Blockchain networks supported by Fireblocks
100+

Blockchain networks supported by Fireblocks

Reported initial Smart Router integration at Fireblocks
One onboarding session

Reported initial Smart Router integration at Fireblocks

The onboarding session refers to integrating Smart Router into Fireblocks' existing environment, not to onboarding each new blockchain.

As blockchain coverage grows, the underlying RPC infrastructure must scale in reliability and operational consistency, not just endpoint count.

Read the Fireblocks case study

Trusted in production by

Kraken
Fireblocks
Galaxy
Hypernative
Kraken
Fireblocks
Galaxy
Hypernative
Kraken
Fireblocks
Galaxy
Hypernative
From network request to production

You bring the next network. We help build the path to it.

Whether you're connecting a network already supported by Smart Router or extending coverage to another blockchain, Magma can help reduce the amount of infrastructure work your team needs to own.

  1. 01

    Define the network requirements

    We review the blockchain, mainnet or testnet requirements, RPC interfaces, expected traffic, methods, and available providers.

  2. 02

    Configure connectivity

    We connect supported provider endpoints or your own nodes, using the relevant chain specification and routing configuration.

  3. 03

    Validate before go-live

    We test endpoint health, method compatibility, and the routing behavior required for the customer's use case.

  4. 04

    Deploy and operate

    Your application uses the configured RPC connectivity. Depending on the deployment model, Magma can also manage infrastructure upgrades, monitoring, and incident response.

For supported networks with the required access and endpoints available, onboarding can be completed within a day. New or unsupported networks may require additional validation and engineering work.

Plan your next chain onboarding
Built for multi-chain businesses

Expand the networks your customers can use, without expanding your infrastructure burden at the same rate.

The blockchain-specific business logic remains yours. The complexity of running the RPC infrastructure doesn't have to.

On the roadmap

Making multi-chain expansion even more straightforward.

On the Roadmap

Self-service chain management

A dashboard experience for adding and managing supported chain configurations without relying exclusively on manual setup.

On the Roadmap

A live chain catalog

A searchable view of supported networks with operational status and relevant interface information.

On the Roadmap

Transparent chain request tracking

Greater visibility into new chain requests, engineering progress, and expected onboarding timelines.

Planned capabilities. Scope and availability may change.

Frequently asked questions

Smart Router supports 284 blockchain networks across EVM and non-EVM ecosystems. Supported interfaces vary by chain. The current chain catalog and documentation provide more detail.

Yes. Magma can review a new chain's API interfaces, available upstream nodes, and integration requirements. Networks compatible with Smart Router's specification model can be introduced through a chain specification, without rewriting the router itself. The work and timeline depend on the network.

No. Magma operates above the compatible RPC providers and private nodes you already use. You can keep your provider relationships and connect supported endpoints to the shared routing infrastructure.

No. Different networks can require different URLs, APIs, methods, and interfaces. Smart Router provides a common orchestration layer while respecting each chain's protocol and configuration.

No. Magma focuses on blockchain RPC connectivity and infrastructure. Exchange-specific asset listing, custody policy, accounting, signing, and application integration remain with your systems.

For an already supported network, with provider access and required endpoints ready, Magma's onboarding process can bring connectivity online within a day. More complex configurations and newly requested networks may require additional engineering and validation.

Yes. Smart Router supports configured private nodes alongside compatible external RPC providers. This gives your team flexibility over infrastructure ownership and provider selection.

Not necessarily. Magma offers managed deployments and dedicated Enterprise infrastructure, alongside self-hosted deployment options under the applicable license.

Related: High Availability · Deposit Detection & Crediting · Withdrawals & Transaction Broadcasting · Multi-chain Connectivity · Pricing · Smart Router on GitHub

Ready for your next network?

Which blockchain is next on your roadmap?

Tell us which networks you're planning to support, which RPC providers you already use, and what's slowing down your infrastructure team.

We'll help you assess the connectivity requirements and how Magma can make your next integration easier to launch and operate.

Expand your blockchain coverage. Keep your infrastructure manageable.