eth_maxPriorityFeePerGas on Mode
Everything below was measured on 2026-10-13 by calling eth_maxPriorityFeePerGas on Mode through the same endpoint customers use, and is re-measured weekly.
What eth_maxPriorityFeePerGas does
Returns the node's suggested priority fee (tip) per gas for an EIP-1559 transaction, in wei. Libraries such as viem and ethers fill maxPriorityFeePerGas from it by default, so its accuracy decides what your users pay.
eth_maxPriorityFeePerGas on Mode: what we measured
| Suggested tip | 0.00100 gwei |
|---|---|
| Median tip paid (median of the per-block medians, last 20 blocks) | 7,071 wei |
| Base fee | 252 wei |
Should you use the suggestion?
The suggestion is 141 times the median tip paid. Any library that fills the tip from eth_maxPriorityFeePerGas overpays by that factor on Mode; take the tip from eth_feeHistory percentiles instead.
Chains where the suggested tip is far above what is paid
On 28 of the chains we measure, the suggested tip was at least ten times the median tip paid (or the median paid was zero).
Example request
curl -s https://rpc.swiftnodes.io/rpc/mode?key=YOUR_API_KEY \
-X POST -H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"eth_maxPriorityFeePerGas","params":[]}'import { createPublicClient, http } from "viem";
const client = createPublicClient({
transport: http("https://rpc.swiftnodes.io/rpc/mode?key=YOUR_API_KEY"),
});
// Tip from what recent blocks paid, not the node's suggestion
const { reward } = await client.getFeeHistory({ blockCount: 20, rewardPercentiles: [50] });
const tips = reward!.map((r) => r[0]).sort((a, b) => (a < b ? -1 : a > b ? 1 : 0));
const maxPriorityFeePerGas = tips[Math.floor(tips.length / 2)];
await wallet.sendTransaction({ to, value, maxPriorityFeePerGas });Other methods on Mode
- eth_blockNumberSupported
- eth_chainIdSupported
- eth_getBalanceSupported
- eth_getBlockByNumberSupported
- eth_getTransactionByHashSupported
- eth_getTransactionReceiptSupported
- eth_callSupported
- eth_estimateGasSupported
- eth_gasPriceSupported
- eth_sendRawTransactionSupported
- eth_getTransactionCountSupported
- eth_getCodeSupported
- eth_subscribeNot available
- eth_getLogsSupported
- eth_getBlockReceiptsSupported
- eth_feeHistorySupported
- eth_getProofSupported
- eth_createAccessListSupported
- debug_traceCallSupported
- trace_blockSupported
- trace_transactionNot available
eth_maxPriorityFeePerGas on other chains
- Ethereum
- Base
- Arbitrum
- Optimism
- Polygon
- BNB Smart Chain
- Avalanche
- Sonic
- Linea
- Scroll
- zkSync Era
- Blast
- Mantle
- Gnosis
- Celo
- Berachain
- Monad
- Unichain
- Kaia
- PulseChain
- World Chain
- Ronin
- Abstract
- ApeChain
- MegaETH
- Fantom
- Lisk
- Hemi
- X Layer
- BOB
- Plasma
- Fraxtal
- Zora
- Story
- Soneium
- Sei
- Hyperliquid
- Taiko
- Morph
- Ink
- Katana
- Ethereum Classic
- opBNB
- Flare
- Core
- Chiliz
- Telos EVM
- Tempo
- Cronos
- Manta Pacific
- Shibarium
- Boba Network
- Arbitrum Nova
- Immutable zkEVM
Frequently asked questions
Does Mode support eth_maxPriorityFeePerGas?
Yes. eth_maxPriorityFeePerGas answered on the SwiftNodes Mode endpoint when our weekly probe called it through the customer path (2026-10-13).
What priority fee should I use on Mode?
The median tip paid over the last 20 blocks was 7,071 wei on 2026-10-13; the node suggested 0.00100 gwei. Take the tip from eth_feeHistory percentiles.
Mode endpoints, live block height and WebSocket status are on the Mode RPC page.
One key covers every chain we serve, and SwiftNodes has a free tier.