eth_maxPriorityFeePerGas

BNB Smart Chain runs as chain ID 56 and charges all gas in BNB. eth_maxPriorityFeePerGas gives you a starting tip to attach when you build a transaction for its ~3-second PoSA blocks. Query https://bsc.therpc.io/YOUR_API_KEY and the method returns the node's suggested priority fee, meaning the tip per gas unit, for EIP-1559 transactions, expressed as a hex value in wei. That figure is a heuristic the node derives from recent block history. Treat it as a reasonable default, not a guaranteed inclusion price on BNB Smart Chain.

Use cases

• Fill the maxPriorityFeePerGas field when assembling an EIP-1559 transaction bound for BNB Smart Chain so validators see a competitive tip.
• Seed a wallet's fee-suggestion screen with a sensible default tip in BNB before letting the user nudge it up or down.

Parameters

Este método no acepta parámetros. Pasa un array vacío [].

Response

Example request

1curl https://bsc.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H "Content-Type: application/json" \
4  -d '{
5    "jsonrpc": "2.0",
6    "method": "eth_maxPriorityFeePerGas",
7    "params": [],
8    "id": 1
9  }'

Try it live in the BNB Smart Chain playground.

Errors & troubleshooting

Common pitfalls

• The answer is only a heuristic: two BNB Smart Chain nodes can hand back different tips for the very same block, so don't assume it is canonical.
• A network that has not enabled EIP-1559 may reject this call or return a meaningless figure. Fall back to eth_gasPrice for a legacy gas price instead.
• When you need a precise fee strategy, call eth_feeHistory with explicit percentiles rather than relying on this single suggested number.

Supported networks

• Mainnet — Chain ID: 56
• Testnet — Chain ID: 97

See also

• eth_feeHistory
• eth_gasPrice
• eth_estimateGas

1curl https://bsc.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H 'Content-Type: application/json' \
4  -d '{"jsonrpc":"2.0","id":1,"method":"eth_maxPriorityFeePerGas","params":[]}'