eth_chainId - zkSync
Example code for the eth_chainId JSON-RPC method. Сomplete guide on how to use eth_chainId JSON-RPC in GetBlock.io Web3 documentation.
Returns the chain ID of the connected network. For zkSync Era mainnet the result is 0x144 (324 in decimal); for Sepolia testnet it is 0x12c (300). Chain ID is required for EIP-155 signed transactions to prevent replay attacks across chains.
Parameters
None
Request Example
curl --location --request POST 'https://shared.eu-central-1.getblock.io/<ACCESS-TOKEN>/' \
--header 'Content-Type: application/json' \
--data-raw '{
"jsonrpc": "2.0",
"method": "eth_chainId",
"params": [],
"id": "getblock.io"
}'import axios from 'axios';
const data = JSON.stringify({
"jsonrpc": "2.0",
"method": "eth_chainId",
"params": [],
"id": "getblock.io"
});
const config = {
method: 'post',
url: 'https://shared.eu-central-1.getblock.io/<ACCESS-TOKEN>/',
headers: {
'Content-Type': 'application/json'
},
data: data
};
axios(config)
.then(response => console.log(JSON.stringify(response.data, null, 2)))
.catch(error => console.log(error));Response Example
{
"jsonrpc": "2.0",
"id": "getblock.io",
"result": "0x144"
}Response Parameters
result
string
Chain ID in hexadecimal (0x144 = 324 mainnet, 0x12c = 300 Sepolia testnet)
Use Cases
Constructing EIP-155 signed transactions
Validating that a wallet is connected to zkSync Era
Multi-chain dApps that branch logic by chain ID
Error Handling
403
Forbidden
Missing or invalid <ACCESS-TOKEN>
-32602
Invalid params
Request parameters are missing or malformed
429
Too Many Requests
Rate limit exceeded for your plan
SDK Integration
Last updated
Was this helpful?