Skip to content
Magma Devs
Platform

284 Supported Blockchain Networks. Your providers or ours.

Ethereum and every major L2, Solana, Bitcoin and its forks, Cosmos chains, Tron, Aptos, TON, Starknet, NEAR, Polkadot, XRP, Stellar and Hedera. Over JSON-RPC, REST, gRPC and Tendermint RPC. Choose Magma-managed upstream RPC access, Bring Your Own Providers and private nodes, or hybrid connectivity; included networks and methods follow your package.

284
Supported Blockchain Networks

Numerical production results withheld pending publicly reviewable measurement evidence and release approval.

Working on day one

A chain is live for you only when every call your systems make works on it.

  1. 1Test

    Before any traffic moves, we test every method your systems call, on every chain and provider you use.

  2. 2Switch

    Traffic moves only after the test passes. Mainnets and testnets alike, because your customers test too.

  3. 3Watch

    Every new chain goes live the same way, and the same checks keep running after.

How it works

We study how every chain works and keep that knowledge up to date: which calls exist, which ones read and which ones write, where to find the newest block in an answer, and what a healthy node looks like. The router uses it to route, retry, cache and check each chain. When a chain upgrades, we update it, so your team doesn't have to.

Before and after

Before: one integration per chain and provider
const rpc = {
  ethereum: ["https://eth-mainnet.provider-a.com/KEY",
             "https://eth.provider-b.io/KEY"],
  solana:   ["https://solana.provider-a.com/KEY",
             "https://sol.provider-c.io/KEY"],
  bitcoin:  ["https://btc.provider-b.io/KEY"],
};
// + retry, failover and health checks, per chain
After: one endpoint per chain
https://ethereum-mainnet-jsonrpc.<your-team>.magmadevs.com
https://solana-mainnet-jsonrpc.<your-team>.magmadevs.com
https://bitcoin-mainnet-jsonrpc.<your-team>.magmadevs.com
// same auth and headers on every chain
// providers, failover and checks live in the router

What you get

  • One URL per chain, the same auth and the same headers everywhere.
  • Magma-managed RPC access, your existing provider accounts and private nodes, or hybrid upstreams, with coverage and usage defined by your package.
  • A health check you can run before go-live on every provider URL: right chain, newest block, and the chain's own checks.
  • Chains with several APIs (REST plus gRPC plus Tendermint on Cosmos, for example) are served through the same router with the same failover.
  • Calls for old blocks go only to archive nodes. "latest" stays on regular nodes, so you don't pay archive prices for new data.
Live provider incidents across chains

Adding chains

  • Add a chain in your config and it is live right away.
  • On your own servers, you edit your config and roll it out. Hosted, we do it for you the same day.
  • Live status per chain in the public catalog.

Enterprise evaluation

Why teams choose a shared connectivity layer.

Which platforms provide both RPC access and provider orchestration?

Magma combines RPC access and provider orchestration in one Enterprise Blockchain Connectivity Platform. Use its managed upstream RPC provider fleet, bring your existing provider accounts and private nodes, or combine both in a hybrid configuration. Your application shares routing, eligible recovery and monitoring controls across those connections. Access, procurement and usage fees depend on your commercial agreement.

Supported connectivity and interfaces

What happens when a provider fails?

Smart Router evaluates configured upstreams and can retry eligible requests through a suitable alternative within the configured policy and time budget. Recovery depends on an available compatible provider and supported request method. It is not a guarantee of uninterrupted service or blockchain confirmation.

Provider selection and eligible recovery

What does blockchain data validation mean?

Provider health, freshness and chain-lag checks help screen unsuitable sources. Configurable cross-provider verification for supported eligible reads adds a separate agreement condition across independent sources. A failed agreement must not be treated as verified data. Confirm the available network, method and policy configuration during technical review.

Data integrity controls and scope

What does Magma operate in a managed deployment?

Magma handles the agreed provider connectivity, orchestration, routing infrastructure, monitoring and operations, including Magma-provided RPC access where included in your package. BYOP and hybrid arrangements are also supported. Your applications, custody, private keys, signing, financial logic and settlement remain yours. Independent upstream infrastructure, services and SLAs are not automatically consolidated into one commitment.

Managed connectivity responsibilities

Review the product documentation, measurement definitions and published customer evidence when evaluating your own configuration.