eth_subscribe on Lisk
Everything below was measured on 2026-11-08 by calling eth_subscribe on Lisk through the same endpoint customers use, and is re-measured weekly.
What eth_subscribe does
Opens a subscription over WebSocket: newHeads pushes each new block header, logs pushes matching events, and newPendingTransactions pushes mempool transaction hashes where the node exposes them. It replaces polling, and it only works over WebSocket, not HTTP.
eth_subscribe on Lisk: what we measured
| newHeads | supported |
|---|---|
| First header after subscribing | 422 ms |
| Median gap between headers | 1.7 s |
| Headers in 15 seconds | 8 |
| logs | not supported: The free plan supports new-head subscriptions only (eth_subscribe "newHeads"). Logs, pending transactions and other feeds need a paid plan, from Starter at $49/ |
| newPendingTransactions | not supported: The free plan supports new-head subscriptions only (eth_subscribe "newHeads"). Logs, pending transactions and other feeds need a paid plan, from Starter at $49/ |
What this means on Lisk
Headers pushed over WebSocket are not identical to eth_getBlockByNumber over HTTP on Lisk. Only the HTTP block has size, withdrawals. Fetch the block over HTTP if you need those fields.
newPendingTransactions is not available, so mempool watching on Lisk is not possible through this endpoint. Rollups with a single sequencer have no public mempool to stream.
Subscriptions end when the connection drops. Reconnect with backoff and, after reconnecting, fetch the blocks you missed with eth_getBlockByNumber.
Example request
wscat -c "wss://rpc.swiftnodes.io/ws/lisk?key=YOUR_API_KEY"
> {"jsonrpc":"2.0","id":1,"method":"eth_subscribe","params":["newHeads"]}import { createPublicClient, webSocket } from "viem";
const client = createPublicClient({
transport: webSocket("wss://rpc.swiftnodes.io/ws/lisk?key=YOUR_API_KEY", { reconnect: true }),
});
const unwatch = client.watchBlocks({
onBlock: (block) => console.log(block.number, block.hash),
});Other methods on Lisk
- eth_blockNumberSupported
- eth_chainIdSupported
- eth_getBalanceSupported
- eth_getBlockByNumberSupported
- eth_getTransactionByHashSupported
- eth_getTransactionReceiptNot measured
- eth_callSupported
- eth_estimateGasSupported
- eth_gasPriceSupported
- eth_maxPriorityFeePerGasSupported
- eth_sendRawTransactionSupported
- eth_getTransactionCountSupported
- eth_getCodeSupported
- eth_getLogsSupported
- eth_getBlockReceiptsSupported
- eth_feeHistorySupported
- eth_getProofSupported
- eth_createAccessListSupported
- debug_traceCallSupported
- trace_blockSupported
- trace_transactionSupported
eth_subscribe on other chains
- Ethereum
- Base
- Arbitrum
- Optimism
- Polygon
- BNB Smart Chain
- Avalanche
- Sonic
- Linea
- Scroll
- zkSync Era
- Mantle
- Gnosis
- Celo
- Berachain
- Monad
- Unichain
- Kaia
- PulseChain
- World Chain
- Ronin
- Abstract
- ApeChain
- MegaETH
- Fantom
- Hemi
- X Layer
- BOB
- Plasma
- Fraxtal
- Zora
- Story
- Soneium
- Sei
- Hyperliquid
- Taiko
- Morph
- Ink
- Katana
- Ethereum Classic
- opBNB
- Mode
- Flare
- Core
- Chiliz
- Telos EVM
- Tempo
- Cronos
- Manta Pacific
- Shibarium
- Boba Network
- Arbitrum Nova
- Immutable zkEVM
Frequently asked questions
Does Lisk support eth_subscribe?
Yes. eth_subscribe answered on the SwiftNodes Lisk endpoint when our weekly probe called it through the customer path (2026-11-08).
Does Lisk support WebSocket subscriptions?
Yes. newHeads worked through wss://rpc.swiftnodes.io/ws/lisk on 2026-11-08; logs subscriptions did not.
Can I watch the Lisk mempool?
No: newPendingTransactions is not available.
Lisk endpoints, live block height and WebSocket status are on the Lisk RPC page.
One key covers every chain we serve, and SwiftNodes has a free tier.