githubEdit

How to Get a BNB Smart Chain (BSC) RPC Endpoint

Step-by-step guide to getting a fast, reliableBSC RPC endpoint

BNB Smart Chain remains one of the most active blockchains for DeFi, trading bots, and dApp development. With block times under 3 seconds and significantly lower gas fees than Ethereum, BSC handles massive transaction volumes, and your RPC infrastructure needs to keep pace.

This guide walks you through setting up BSC RPC access with GetBlock, from free development endpoints to Accelerated Dedicated Nodes with private mempool support.

Step-by-Step: Get Your BSC RPC Endpoint

1

Create a GetBlock Account

Go to GetBlock Dashboardarrow-up-right and sign up. You can register with email or via Google/GitHub OAuth.

2

Create a BSC Endpoint

Once logged in:

  1. Click "Shared Nodes" in the left sidebar

  2. Click "Create New Endpoint" or the "+" button

  1. Select:

    • Protocol: BSC

    • Network: Mainnet or Testnet

    • API Interface: JSON-RPC or Websocket or GraphQL or MEV-Protected(JSON-RPC) or MEV-Protected(Websocket)

    • Region: Frankfurt (EU) or Singapore or New York

  2. Click "Create": Your endpoint URL will be generated immediately.

3

Copy Your Endpoint URL

Your endpoint URL looks like this:

https://go.getblock.io/a1b2c3d4e5f6789012345678abcdef01/
circle-exclamation
4

Test the Connection

curl -X POST https://go.getblock.io/<YOUR-ACCESS-TOKEN>/ \
  -H "Content-Type: application/json" \
  -d '{
  "jsonrpc":"2.0",
  "method":"eth_chainId",
  "params":[],
  "id":1
  }'

Code Examples

# Get USDT balance on BSC using eth_call
curl -X POST https://go.getblock.io/<YOUR-ACCESS-TOKEN>/ \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "method": "eth_call",
    "params": [{
      "to": "0x55d398326f99059fF775485246999027B3197955",
      "data": "0x70a08231000000000000000000000000YOUR_ADDRESS_WITHOUT_0x"
    }, "latest"],
    "id": "getblock.io"
  }'

Connect MetaMask to BSC via GetBlock

  1. Open MetaMask → Add NetworkAdd manually

  2. Enter:

    • Network Name: BSC Mainnet (GetBlock)

    • RPC URL: https://go.getblock.io/<YOUR-ACCESS-TOKEN>/

    • Chain ID: 56

    • Symbol: BNB

    • Explorer: https://bscscan.com

  3. Save

Public BSC RPC vs GetBlock

Feature
Public RPC
GetBlock

Rate limits

Heavy throttling

Up to 500 RPS

Uptime

No guarantee

99.9%+ SLA

Trace/Debug methods

Not available

Available (Starter+)

Archive data

Limited

Full history

Private mempool

No

Available (Accelerated Dedicated)

MEV protection

None

Via BloXroute BDN integration

WebSocket

Unreliable

Persistent connections

BSC Advanced Tooling — Exclusive to GetBlock

Accelerated Dedicated Node

GetBlock offers BSC-specific infrastructure with an integrated BloXroute BDN (Blockchain Distribution Network):

Private Mempool Submission

Submit transactions to a private mempool, bypassing the public mempool entirely:

  • MEV protection — your transactions aren't visible to sandwich bots

  • Higher landing rate — direct submission to block producers

  • Priority fee support — set custom priority fees for faster inclusion

How to Submit to Private Mempoolarrow-up-right

Bundle Support (Multicall3)

Execute multiple transactions atomically:

  • All-or-nothing execution

  • MEV-resistant operations

  • Complex DeFi strategies in a single block

How to Use Bundlesarrow-up-right

Stream Subscription

Subscribe to real-time BSC data streams:

  • New pending transactions

  • New blocks

  • Transaction receipts

How to Subscribe to Streams arrow-up-right

Choosing Your Plan

Use Case
Plan
Key Benefit

Development & testing

Free

50K CU/day

Production dApp

Starter ($49/mo)

100 RPS, trace/debug

DeFi protocol

Advanced ($199/mo)

300 RPS, archive

Trading bot / DEX

Dedicated (from $1,000/mo)

Unlimited, private mempool

HFT / MEV

Accelerated Dedicated (custom)

BloXroute BDN, bundles

What's Next?

Need high-performance BSC infrastructure for trading or DeFi? Contact usarrow-up-right to discuss Accelerated Dedicated Nodes with private mempool and bundle support.

Last updated

Was this helpful?