Skip to content
Magma Devs
Solutions / Transaction Broadcasting

Your withdrawal shouldn't depend on one RPC provider answering.

A silent RPC failure can leave a signed transaction's outcome unclear. Magma supplies managed RPC access, connects your existing providers and private nodes, or combines both in a hybrid configuration for parallel submission through eligible upstreams. Signing, authorization and confirmation policies remain in your systems; supported methods and usage follow your package.

One connection. Multiple paths to the network. Less uncertainty in your transaction infrastructure.

  • 284 Supported Blockchain Networks
  • Bring your existing RPC providers
  • Managed or self-hosted
Wallet / custody system
Signed transaction
Magma Smart Router
Broadcast fan-out
Provider AReady
Provider BReady
Provider CReady
Blockchain network
SignedBroadcastRPC acknowledged
On-chain confirmation: handled by your system
Illustrative flow for supported stateful broadcasts. Eligible providers depend on routing configuration. RPC acknowledgement does not guarantee on-chain confirmation.
The challenge

The most dangerous transaction error is the one you don't understand.

Imagine your platform submits a withdrawal through an RPC provider.

The request times out.

Did the transaction fail to reach the node? Was it accepted but the response lost? Is it already propagating through the blockchain network?

From an unsuccessful RPC request alone, your application may not know.

This ambiguity matters when your systems move customer assets. Retrying the same signed payload and creating a new transaction are not the same decision.

Silent provider failures

A provider stops responding during transaction submission.

Your application cannot reliably infer the transaction's network status from that timeout alone.

Network congestion

During periods of heavy blockchain activity, providers can become overloaded, delay responses, or struggle to propagate transactions.

Operational uncertainty

When transaction submission and network confirmation are confused, teams waste time investigating and may make unsafe retry or replacement decisions.

Reliable transaction infrastructure needs more than an RPC endpoint. It needs resilient broadcast paths and clear ownership of what happens after submission.

The Magma approach

One signed transaction. Multiple opportunities to reach the network.

Smart Router sits between your transaction systems and the RPC providers you already use. For supported write methods, it broadcasts the same signed transaction through eligible configured providers instead of depending on a single upstream connection.

  1. 01Your systems

    Keep your existing signing infrastructure

    Your application or custody platform continues creating, authorizing, and signing transactions.

    Magma does not require access to your private keys or control over withdrawal approvals.

  2. 02Magma layer

    Connect independent providers

    Configure the RPC providers and private nodes your platform already uses.

    Smart Router provides a unified access layer across supported blockchain interfaces.

  3. 03Magma layer

    Broadcast in parallel

    For supported transaction submission methods, Smart Router sends the signed payload to the eligible providers selected for that request.

    If one provider becomes unavailable or does not respond, another eligible provider may still accept the submission.

  4. 04Your systems

    Keep confirmation and settlement under your control

    Your application remains responsible for checking transaction inclusion, applying blockchain-specific confirmation and finality rules, and reconciling customer balances.

    Magma strengthens the infrastructure used to submit transactions. Your systems continue making the financial decisions.

Parallel broadcasting in action

If one provider goes silent, your transaction still has another path.

Traditional single-endpoint submission can leave an entire withdrawal workflow dependent on one upstream response.

Magma lets supported write requests reach multiple eligible providers in parallel.

Illustrative

Submitting signed transaction…

More broadcast paths. Less dependence on one provider.

Parallel submission improves resilience at the RPC layer. It does not override blockchain rules, guarantee inclusion, or replace the monitoring your systems need after broadcasting.

Business impact

A better transaction path protects more than performance.

Reduce single-provider exposure

A provider outage or silent failure should not be the only path available to a critical withdrawal workflow.

Reduce manual infrastructure intervention

Keep provider routing and broadcast orchestration in one layer rather than rebuilding the same operational logic in every service.

Strengthen customer trust

More resilient blockchain connectivity helps your team reduce infrastructure-related interruptions in the workflows customers rely on to move assets.

Magma makes the broadcasting layer more resilient. Your application maintains responsibility for transaction correctness, signing policies, balances, and settlement.

Proven under real network pressureFireblocks

When Solana came under extreme pressure, Fireblocks kept transactions moving.

During the January 2025 launch of the $TRUMP token, Solana experienced extraordinary transaction activity.

Fireblocks saw a increase in Solana traffic as institutional customers executed time-sensitive operations.

RPC providers across the ecosystem became congested, creating a difficult environment for reliable transaction broadcasting.

Smart Router automatically routed around degraded providers and supported parallel transaction propagation across eligible upstreams.

The Magma-authored account describes routing capabilities, not an independently audited benchmark. The available evidence does not isolate Magma's contribution to Fireblocks-wide broadcast-time or response-time improvements.

Review transaction submission scope. Broadcast acknowledgement is not blockchain confirmation; performance figures require customer-approved attribution and measurement evidence.

Extreme network activity is when your customers need infrastructure they can rely on most. The RPC layer must adapt faster than an engineering team can manually switch providers.

Read the Fireblocks story

Illustrative congestion routing, not measured Fireblocks performance. Magma's published case study is not an independent audit. Broadcast acknowledgement is not on-chain confirmation.

Who it's for

For platforms where sending transactions is a critical operation.

Custody Platforms

Support resilient blockchain access for signed withdrawal operations while retaining your existing custody, approval, and signing infrastructure.

Exchanges

Reduce dependency on individual RPC providers during high-volume transaction submission and periods of market volatility.

Wallet Infrastructure

Provide a common RPC broadcasting layer across supported networks while keeping transaction preparation, authorization, and customer experiences in your own systems.

Stablecoin & Payment Infrastructure

Build more resilient broadcast paths for blockchain payment and payout workflows, without confusing transaction submission with final settlement.

Different financial applications have different transaction rules. Reliable access to the blockchain should not require every team to build the same provider orchestration layer from scratch.

End-to-end RPC management

Transaction broadcasting is one part of the infrastructure your team shouldn't have to babysit.

Your withdrawal systems depend on much more than the final submission request.

They rely on blockchain state, nonce or sequence information, gas or fee estimates, transaction receipts, healthy RPC endpoints, and accurate provider responses.

Magma provides one reliability and orchestration layer across these RPC dependencies.

Rather than adding another disconnected transaction-sending integration, your team can use a shared infrastructure layer for routing, data verification on eligible reads, provider health management, and resilient broadcasting.

Provider-independent routing
Use your existing RPC vendors and your own nodes.
Data integrity for critical reads
Configure independent cross-provider verification for supported reads where consistency matters.
Managed infrastructure
Let Magma operate the routing infrastructure, monitoring, upgrades, and incident response under an appropriate managed service agreement.
Explore Magma's deployment options
On the Roadmap

From reliable broadcasting to deeper transaction visibility.

We're extending the infrastructure layer beyond transaction submission, helping teams understand what happened after a transaction was broadcast.

Per-transaction history

A searchable record of which providers received a transaction, what each returned, and which submission attempts or routing decisions occurred.

On-chain confirmation monitoring

More visibility into when a broadcast transaction appears on-chain, including detecting transactions that remain unconfirmed or appear to have been dropped.

Transaction investigation

Tools to reconstruct the available transaction lifecycle and help engineering teams investigate ambiguous or failed submission workflows.

Pre-broadcast policy integrations

Potential integration with third-party screening and policy systems to enforce external transaction decisions before broadcasting, subject to product development and supported networks.

Planned capabilities. Product scope and availability may change.

Frequently asked questions

No. Your custody, wallet, or transaction system remains responsible for preparing, authorizing, and signing transactions. Magma handles supported RPC submission requests and infrastructure routing.

For supported stateful methods, Smart Router sends the same signed transaction through the eligible RPC providers selected by its configuration. This improves the opportunity for at least one available provider to receive and accept the submission.

Smart Router forwards the same signed transaction payload. It does not create or sign new transfers. Your system must still manage nonce or sequence rules, transaction replacement, retry decisions, and reconciliation according to each blockchain's behavior.

Not necessarily. A provider may receive or forward a transaction before the response is lost. A timeout alone does not establish the transaction's on-chain status. Your system should check the transaction before making a new signing or replacement decision.

No. Successful RPC submission is not the same as blockchain inclusion or finality. Network congestion, transaction validity, fees, and protocol behavior still affect whether and when a transaction is confirmed.

Yes. Smart Router works with eligible endpoints from different providers and your own nodes. The exact broadcast targets depend on supported methods and the configured provider pool.

A stored, searchable per-transaction lifecycle and automated confirmation monitoring are planned capabilities. Today's Smart Router provides RPC routing, broadcast fan-out for supported writes, response-level information, and operational metrics.

Yes. Magma offers managed RPC infrastructure, including dedicated private deployments, monitoring, upgrades, and incident response under the applicable service plan.

Related: High Availability · Deposit Detection & Crediting · Exchanges · Custody Platforms

Let's review your transaction path

What happens to your withdrawals when an RPC provider stops answering?

If your platform moves customer assets, uncertainty in the broadcast layer is a risk worth understanding.

Tell us which networks, RPC providers, and transaction workflows you rely on. We'll help you evaluate where your current infrastructure is exposed and how Magma can make it more resilient.

Keep control of your transactions. Let Magma strengthen the path to the blockchain.