RPC Gateway: WebSockets for Arbitrum and BSC

Stop polling. Start streaming. Tatum WebSocket subscriptions push blockchain updates to your app over a persistent connection, so you can react to new blocks, pending transactions, and contract events without a polling loop.

Now available on Arbitrum One and BNB Smart Chain (BSC).

Arbitrum One

BSC

What you get

• Real-time updates: receive JSON-RPC notifications as subscribed events occur.
• Filtered contract events: subscribe to logs by contract address, event topics, or both.
• Subscriptions and queries on one connection: make standard JSON-RPC calls alongside your subscriptions.

Build live dashboards, track transaction confirmations, or trigger application workflows from smart contract events.

Supported subscriptions

Both chains support the following subscription types through eth_subscribe:

• newHeads: receive new block headers. Use eth_getBlockByNumber to fetch the transactions in a block.
• newPendingTransactions: receive pending transaction hashes. Pending does not mean confirmed; this stream can be high-volume, so fetch transaction details selectively.
• logs: receive contract events filtered by address or topics. Handle removed: true when a chain reorganization invalidates a previously reported log.

Connect to a mainnet endpoint

Get an API key, then follow your chain’s reference documentation for authentication and connection examples.

Arbitrum One

wss://arbitrum-one-mainnet.gateway.tatum.io 📖 Docs

BSC

wss://bsc-mainnet.gateway.tatum.io 📖 Docs

Plan for reconnects and chain reorganizations

Subscriptions are tied to the connection. If it drops, reconnect and subscribe again. Recover missed on-chain events with historical RPC queries, such as eth_getLogs for contract logs, and handle duplicate events safely.

Treat incoming updates as provisional until they meet your application’s confirmation requirements. See the WebSocket subscription guide for production guidance.

Explore the documentation