A successful RPC response doesn't mean the data is correct.
Your systems depend on blockchain data to verify balances and reconcile activity. Use Magma-managed RPC access, bring your own providers and private nodes, or combine both. Configured checks compare eligible reads across independent sources and identify stale or conflicting answers; balances and reconciliation decisions remain in your applications.
Keep your providers. Keep your systems. Add an independent layer of data verification.
- 284 Supported Blockchain Networks
- Independent provider verification
- Configurable validation policies
- Balance check
- Transaction receipt
- Contract-state read
- Provider AVendor group AIdle
- Provider BVendor group BIdle
- Provider CVendor group CIdle
Your systems can make the wrong decision from a perfectly valid response.
RPC infrastructure is often evaluated on availability, latency, and error rates.
Those metrics matter. But they do not answer a more fundamental question.
Is the data correct?
A provider can respond quickly while serving outdated blockchain state. Two providers can disagree about a transaction receipt. A compromised endpoint can return manipulated information that looks structurally valid.
If your application accepts that answer without further verification, the problem moves from the infrastructure layer into your business logic.
For exchanges, custody platforms, and financial applications, the consequences can affect customer balances, transaction processing, reporting, and operational trust.
Stale data
The provider is online but behind the chain.
Your application may receive an outdated balance, block, or transaction status without seeing an ordinary transport error.
Conflicting data
Independent providers return different answers for the same eligible read.
Without a verification policy, your application may act on whichever provider answered first.
Untrusted data
A compromised or malfunctioning endpoint returns a believable but incorrect response.
Traditional uptime monitoring may not detect the problem.
Availability tells you whether a provider answered. Data integrity tells you whether that answer deserves your trust.
Check the provider. Check the answer. Understand the disagreement.
Smart Router combines several independent mechanisms to reduce the risk of unreliable blockchain data.
They solve different problems and work together.
- 01Freshness
Freshness-aware routing
Don't ask a node that is already behind.
Smart Router tracks the observed chain height of configured providers.
When a provider falls behind the acceptable freshness threshold, the routing layer can exclude it from serving new eligible requests until it catches up.
This helps prevent an out-of-sync node from being treated as a healthy source simply because its API still responds.
- 02Independent Verification
Independent response verification
Don't trust one answer when the decision is critical.
For supported reads, Smart Router can send the same request to several independent RPC providers.
A configurable validation policy determines how many responses must agree and whether those responses must come from different vendor groups.
This makes it harder for one unreliable or compromised provider to silently influence a critical result.
- 03Operational Evidence
Disagreement visibility
Don't let inconsistent answers disappear into your logs.
Validation results and provider disagreement signals can be observed through the router's response metadata, metrics, and operational logging.
Teams can use this information to investigate problematic providers, improve routing policies, and support their internal control processes.
Each mechanism addresses a different risk. A healthy endpoint is not automatically a correct endpoint, and a matching response is not a replacement for blockchain-specific finality rules.
Three providers agree. But are they truly independent?
A quorum is only meaningful when you understand where its answers come from.
Two nodes operated by the same vendor may share infrastructure, software, or failure modes.
Smart Router supports policies that require matching responses across distinct provider groups, giving infrastructure teams control over how sensitive blockchain reads are checked.
- 3 maximum participants
- 2 matching responses required
- At least 2 independent groups
Illustrative two-of-three validation policy requiring agreement across at least two provider groups. Real behavior depends on configuration, method support, caching, and available providers.
Explore cross-validation documentationReconciliation starts with information you can defend.
For financial platforms, blockchain data is not just something displayed in a dashboard.
It feeds real operational processes.
An exchange may compare blockchain balances with internal account records. A custodian may use transaction and balance data as part of its asset controls. A wallet infrastructure provider may need consistent transaction history across multiple RPC sources.
These reconciliation processes are only as dependable as the information entering them.
Magma helps strengthen that input layer by reducing reliance on individual providers and supporting independent verification for sensitive blockchain reads.
Your financial and accounting systems remain responsible for reconciliation rules, exception handling, and ledger accuracy.
- 01
Reliable blockchain access
Magma routes eligible reads through configured, monitored providers and can avoid endpoints that have become unhealthy or stale.
- 02
Independently checked data
For configured sensitive operations, Smart Router can require agreement across independent RPC sources before returning a response.
- 03
Customer-owned reconciliation
Your application compares trusted blockchain inputs with internal records and applies its own accounting, confirmation, and exception-handling policies.
- Freshness evaluation
- Configured cross-validation
- Provider disagreement metrics
- Compare on-chain and internal records
- Apply accounting rules
- Investigate exceptions
- Provider routing
- RPC freshness
- Configured response verification
- RPC operational visibility
- Internal ledger
- Balance reconciliation
- Accounting policy
- Exception resolution
- Financial reporting decisions
Magma doesn't replace your reconciliation system. It helps make the blockchain data entering that system more dependable.
A compromised RPC layer can become a financial security incident.
On April 18, 2026, the KelpDAO rsETH bridge was exploited, resulting in the loss of approximately $292 million.
According to LayerZero's investigation, attackers compromised internal RPC infrastructure and manipulated the responses used by a verification service.
A denial-of-service attack against an external RPC source further reduced the availability of independent information.
The incident also exposed the risks of relying on a single required verifier within the affected cross-chain application's security configuration.
The lesson goes beyond provider uptime.
A system can receive technically valid responses and still make decisions based on manipulated information.
- Approximate value lost in the April 2026 KelpDAO incident
- $292M
- Part of the attack path identified by LayerZero
- Compromised RPC responses
Approximate value lost in the April 2026 KelpDAO incident
Part of the attack path identified by LayerZero
This incident was not a Magma customer incident, and Magma did not participate in its detection or prevention.
No single RPC validation technique can guarantee that an attack like this will be prevented.
The lesson is the importance of independent trust domains, resilient access to uncompromised sources, and strong application-level verification policies.
- 1Internal RPC compromised
- 2External source under DoS
- 3Verifier acts on bad inputs
Provider independence must be real, not just multiple endpoints on paper.
Conceptual. Not a reconstruction of the affected infrastructure.

Built for the data reliability demands of global digital asset platforms.
Kraken operates blockchain infrastructure supporting large-scale trading and digital asset services.
To strengthen the systems behind its operations, Kraken integrated Magma Smart Router as an additional RPC routing and resilience layer above its existing infrastructure.
The public Kraken case study describes the partnership's focus on reliability, uptime, data accuracy, and continuity during demanding operating conditions.
Magma provides infrastructure capabilities that help teams manage provider quality and reduce dependence on individual upstream endpoints.
For enterprises operating critical blockchain systems, the goal is more than a fast RPC response. It is dependable infrastructure and greater confidence in the information those systems receive.
Read the Kraken case studyGeneric illustration. Not Kraken's actual configuration.
Trusted in production by












More providers don't automatically mean more trustworthy data.
Using multiple RPC endpoints is an important step toward resilient blockchain access.
But if those endpoints share the same infrastructure, vendor, or failure mode, their answers may not be as independent as they appear.
Smart Router allows infrastructure teams to group providers and configure agreement requirements for sensitive reads.
This adds another level of control beyond ordinary failover and load balancing.
Provider diversity
Combine independent RPC vendors or private nodes where appropriate, rather than assuming multiple URLs always provide independent verification.
Risk-based policies
Apply stronger verification to eligible high-value reads such as balances, transaction receipts, and contract state, while avoiding unnecessary validation overhead for every ordinary request.
Visibility into disagreements
Use validation signals and operational metrics to identify problematic responses and inform provider and policy decisions.
Better data integrity is not about asking the largest number of providers. It is about selecting the right independent sources and defining what level of agreement your systems require.
When blockchain data drives financial decisions, one unchecked answer is too much uncertainty.
Exchanges
Use verified blockchain inputs as part of systems that monitor deposits, transaction status, and customer balances.
Reduce dependence on a single RPC provider for sensitive data.
Custody Platforms
Strengthen the reliability of blockchain reads used by internal asset monitoring, operational controls, and reconciliation workflows.
Wallet Infrastructure
Provide dependable data access across multiple blockchain networks while keeping wallet-specific business and accounting logic in the existing platform.
Financial Institutions
Support stronger infrastructure controls around blockchain information used in reporting and reconciliation, with observable validation results and independent RPC sources.
Different businesses apply different accounting and finality rules. Magma helps improve the quality of the RPC data they consume without replacing those business controls.
Your data integrity controls are only as useful as the infrastructure operating them.
Adding response verification is one step.
Keeping providers healthy, maintaining policies, handling failures, and monitoring disagreements across many blockchains are ongoing responsibilities.
Magma combines its Smart Router technology with deployment and infrastructure management options for enterprise teams.
You can run the router within your own environment or work with Magma to operate the infrastructure under a managed service arrangement.
- Keep your existing infrastructure
- Use the RPC providers and private nodes you already operate, subject to supported chain and interface configurations.
- Centralize reliability controls
- Manage provider selection, routing behavior, supported verification policies, and observability through one infrastructure layer.
- Work with an engineering partner
- Magma can support deployment, configuration, integration, monitoring, and incident response according to your service agreement.
Building stronger evidence behind every critical blockchain answer.
We're extending Smart Router's data integrity capabilities to give enterprise teams more options for monitoring, verifying, and documenting the blockchain information their systems rely on.
Scheduled verification of private nodes
Compare data from customer-operated nodes with independent external providers on a recurring schedule, using appropriate fixed or finalized block contexts.
This can support operational control procedures and internal review.
Re-verifiable validation records
Create more complete records of the sources, responses, and verification policies involved in selected data decisions, so evidence can be reviewed independently later.
Provider correctness insights
Build a clearer picture of provider data quality through independently measured correctness signals across supported chains and methods.
Planned capabilities. Scope and availability may change.
Frequently asked questions
Related: High Availability · Deposit Detection & Crediting · Withdrawals & Transaction Broadcasting · New Chain Listings · Data Integrity platform
If two RPC providers disagree, what does your system do?
If your platform depends on blockchain data for balances, deposits, transaction status, or financial reconciliation, your infrastructure needs a clear answer.
Tell us which networks, RPC providers, and sensitive methods your systems depend on.
We'll help you evaluate how independent validation and stronger RPC reliability controls could fit your existing architecture.
Make critical blockchain decisions with greater confidence in the data behind them.

