A deposit isn't just a transaction. It's a promise to your customer.
Crediting a deposit depends on current, consistent and available blockchain data. Magma can supply managed RPC access for your scanners, orchestrate your existing providers and private nodes, or combine both. Freshness-aware routing and configurable verification support eligible reads; recognition, crediting and finality policies remain yours.
Keep your existing deposit systems. Make the blockchain data they depend on more reliable.
- 284 Supported Blockchain Networks
- Independent provider verification
- Existing RPC providers supported
Verified deposit data. Crediting stays with you.
Magma handles provider selection, freshness checks and configured cross-provider verification. Your deposit system receives agreed data and applies its own financial rules.
Request → Magma → RPC providers → Blockchain · Response returns through Magma
Crediting decided by your application.
Illustrative flow with eligible providers and verification enabled for a supported read. If the required agreement is not met, the data is not verified. Crediting decisions remain with your application.
Your customers see a balance. Your infrastructure sees hundreds of ways to get it wrong.
Behind every credited deposit is a chain of infrastructure decisions.
Your systems must continuously read blockchain data, identify relevant transactions, retrieve receipts, and apply the confirmation rules appropriate to each network.
But the RPC infrastructure underneath those operations can behave unpredictably.
One provider falls behind the chain. Another returns an incomplete or inconsistent answer. A third becomes unavailable during heavy network activity.
The result can be delayed deposit visibility, interrupted scanning, or unreliable data reaching the systems responsible for customer balances.
Missing visibility
A provider outage or timeout interrupts access to the blocks, logs, or receipts your deposit monitoring system needs.
Stale blockchain data
A node can respond successfully while operating behind the current chain state. A successful HTTP response does not mean the data is fresh.
Conflicting answers
Different RPC providers may return inconsistent information. For sensitive reads, accepting one answer without additional verification creates avoidable uncertainty.
A deposit system needs more than a working RPC connection. It needs dependable access to blockchain data and the ability to verify sensitive answers.
Built for the blockchain data your deposit systems depend on.
Magma sits between your application and your RPC providers. Instead of requiring every deposit service to manage provider health, failover, and verification on its own, Smart Router brings those capabilities into one infrastructure layer.
- 01Access
Reliable block access
Keep your existing block scanners and deposit monitoring applications connected to multiple RPC providers.
Smart Router can retry eligible failed requests through healthy alternatives, helping reduce interruptions caused by individual provider failures.
- 02Check freshness
Freshness-aware routing
A provider can be available but behind the blockchain.
Smart Router monitors provider freshness and uses configured health policies to avoid selecting endpoints that are too far behind the chain.
- 03Verify answers
Independent answer verification
For supported sensitive reads, configure cross-validation across multiple RPC providers.
The router can require agreement from independent vendor groups before returning an answer, reducing dependence on a single source of truth.
- 04Return data
Block-aware caching
Deposit monitoring workloads repeatedly request blocks, receipts, and historical data.
Smart Router uses block-aware caching for eligible requests, taking chain state and finality into account to reduce repetitive provider calls without applying ordinary caching rules blindly to changing chain data.
Three providers. One question. Can you trust the answer?
For sensitive blockchain reads, relying on a single provider means trusting that provider's answer.
Smart Router can compare responses across independent providers and require a configured level of agreement before returning data to your application.
eth_getTransactionReceipt- Provider AIndependent provider group 1Receipt found, status 1(agrees)
- Provider BIndependent provider group 2Receipt found, status 1(agrees)
- Provider CIndependent provider group 3Receipt found, status 1(agrees)
Verified response returned to your application.
Illustrative example using an enabled cross-validation policy with a two-provider quorum across independent provider groups.
Better blockchain data. Fewer operational surprises.
More dependable deposit monitoring
Reduce interruptions in blockchain data access when an individual RPC provider fails or degrades.
Greater confidence in sensitive reads
Use configured cross-provider validation for critical responses instead of trusting one upstream answer.
Less infrastructure to maintain
Keep the deposit-processing logic you have already built while Magma manages the RPC routing layer, or operates the managed infrastructure for you.
Your engineering team remains responsible for deposit rules, confirmations, accounting, and crediting. Magma helps make the underlying blockchain connectivity more resilient and verifiable.
Deposit monitoring isn't an occasional API call.
Exchanges, custody platforms, and wallet infrastructure providers continuously query blockchain networks.
The workload may involve polling blocks, retrieving transaction receipts, scanning event logs, querying balances, and checking transaction status across many chains.
A single deposit can depend on multiple blockchain reads before the customer's systems make a crediting decision.
At scale, this creates continuous pressure on RPC provider availability, response consistency, and upstream request volume.
Continuous scanning
Maintain access to block and event data across supported networks.
Repeated reads
Use caching for eligible repeated requests while respecting configured rules for changing blockchain state.
Critical verification
Apply stronger, configurable cross-provider verification to sensitive reads where data integrity matters more than minimizing upstream calls.
You shouldn't need a different reliability architecture for every blockchain you support.
Built for teams where blockchain data is business-critical.
Magma Smart Router is used in production by leading digital asset infrastructure teams, including Kraken, Fireblocks, Galaxy, and Hypernative.
Our platform supports enterprise RPC workloads across multiple blockchain networks, combining provider orchestration, data validation, and operational visibility.
More intelligence around critical deposit data.
We are extending the infrastructure capabilities available to teams that rely on verified on-chain information.
Scheduled verification of private nodes
Compare responses from your own blockchain nodes with external providers at selected finalized block heights, supporting stronger operational controls and audit evidence.
Re-verifiable data records
Create more detailed records of which providers were queried, what they returned, and which validation policy was applied, so verification decisions can be reviewed later.
More visibility into data disagreements
Make it easier to understand patterns of provider disagreement and the operational impact of inconsistent answers.
Planned capabilities. Scope and availability are subject to change.
Frequently asked questions
Related: High Availability · Exchanges · Custody Platforms · Supported Blockchains
How much confidence do you have in the blockchain data behind every deposit?
Tell us which networks you monitor, which providers you use, and where your deposit workflows are most sensitive to missing, delayed, or inconsistent data.
We'll help you evaluate how a more resilient and verifiable RPC layer can strengthen the infrastructure you already operate.
Keep your deposit systems. Strengthen the infrastructure behind them.





