How Bitget serves 125 million users on its exchange with Alchemy

When a crypto exchange confirms that a user's deposit has actually landed onchain, there is no room for "probably." Bitget is a global exchange and web3 ecosystem serving more than 125 million users. It treats deposit and withdrawal verification as critical financial infrastructure. To remove single points of failure from that path, Bitget added Alchemy's industry-leading RPC APIs.

The setup

Bitget runs most of its blockchain reads on self-hosted nodes, which gives the team direct control over its core infrastructure. On the workflows that move user money, Bitget pairs that control with independent confirmation: a third-party node provider that cross-checks the data its own nodes return, so a deposit is credited only when multiple sources agree.

As Bitget scaled, the team decided to increase the robustness of that confirmation layer. Two factors shaped what it needed:

• Self-hosted full nodes retain only a short window of recent blocks, roughly the last 128, so on their own they can't serve the archive and trace data the team needs to reconstruct older transactions or pull internal transactions out of a block.
• Its existing third-party provider returned rate-limit errors during traffic spikes, exactly when deposit confirmation matters most.

To raise the bar on both, Bitget added Alchemy, chosen for the performance and reliability to keep confirmation fast and dependable on the most sensitive workflow Bitget runs.

The solution

Bitget's design is deliberately redundant: self-hosted nodes carry the bulk of traffic, and two independent third-party providers confirm the data that touches user funds. There are three layers:

An independent verification layer

Bitget routes its deposit and withdrawal confirmation traffic to Alchemy as a parallel check against its own nodes. When two independent sources agree, the exchange can credit a deposit with confidence. If one source is throttled or out of sync, the other still answers. This is the layer that removes the single-vendor risk Bitget set out to solve.

An archive and trace layer

Because Bitget's own nodes keep only a short block window, the team leans on Alchemy's archive depth and trace methods to reconstruct transaction detail and extract internal transactions, using calls like trace_block, debug_traceBlockByNumber, eth_getBlockReceipts, and eth_getLogs. This is data their self-hosted infrastructure structurally cannot provide.

A multi-chain coverage layer

Bitget verifies activity across a wide and growing set of networks from one provider, including BNB Smart Chain, Bitcoin, Base, Arbitrum, zkSync, and others, with Alchemy's Bitcoin API support covering the non-EVM chains that are hardest to operate well. Regional coverage in APAC was part of the decision, with Alchemy's Tokyo footprint matching where much of Bitget's traffic originates.

The results

Over a recent 30-day window, Bitget routed 25M+ requests to Alchemy across 9 networks. With Alchemy, they achieved a higher security bar on deposit verification by making the critical path independently confirmed rather than dependent on any single node source.

Ultimately, Bitget chose Alchemy for:

• Chain and regional coverage: one provider across EVM chains plus Bitcoin, including the archive and trace data self-hosted nodes can't serve, and APAC regional coverage close to Bitget's traffic.
• Reliability at scale: a provider with proven reliability across tens of millions of requests on the workload that confirms user funds.
• Hard infrastructure done well: trace and internal-transaction methods, Bitcoin RPC, and high-throughput support—the parts of node infrastructure that are difficult to run themselves.
• Documentation and support: a direct, responsive working relationship through evaluation and integration.

Build on the same blockchain infrastructure Bitget trusts to verify user funds. Get started here, or talk to our team.