eth_protocolVersion - zkSync RPC Method
Get the current Ethereum protocol version on zkSync Era. Useful for client compatibility checks and identifying version-gated features.
Returns the current Ethereum protocol version used by the zkSync Era node.
Why zkSync? Build on Matter Labs' flagship zkEVM powering the Elastic Network of interoperable hyperchains with ZK Stack modular framework, hyperchain interoperability, native account abstraction, and $1.9B in tokenized real-world assets.
When to Use This Method
eth_protocolVersion is useful for ZK developers, RWA tokenization teams, and builders launching custom L2/L3 chains:
- Client Compatibility — Verify that a node supports the protocol version your application requires
- Version-Gated Features — Enable or disable features based on the protocol version (e.g., EIP-1559 support)
- Multi-Client Environments — Ensure consistent protocol versions across a fleet of nodes
- Debugging — Diagnose issues caused by protocol version mismatches between clients
Code Examples
Common Use Cases
1. Node Compatibility Check
Verify protocol version before enabling features:
async function checkCompatibility(provider, minVersion) {
const result = await provider.send('eth_protocolVersion', []);
const version = parseInt(result, 16);
if (version >= minVersion) {
console.log(`Node supports required protocol version ${minVersion}`);
return true;
} else {
console.warn(`Node protocol version ${version} is below required ${minVersion}`);
return false;
}
}2. Multi-Node Version Audit
Check protocol consistency across a fleet of zkSync nodes:
async function auditNodeVersions(endpoints) {
const results = await Promise.all(
endpoints.map(async (endpoint) => {
const provider = new JsonRpcProvider(endpoint);
const [protocolVersion, clientVersion] = await Promise.all([
provider.send('eth_protocolVersion', []),
provider.send('web3_clientVersion', [])
]);
return {
endpoint,
protocolVersion: parseInt(protocolVersion, 16),
clientVersion
};
})
);
const versions = new Set(results.map(r => r.protocolVersion));
if (versions.size > 1) {
console.warn('Protocol version mismatch detected across nodes');
}
return results;
}3. Feature Detection
Enable features based on the protocol version:
async function getNodeCapabilities(provider) {
try {
const version = parseInt(await provider.send('eth_protocolVersion', []), 16);
return {
protocolVersion: version,
supportsEIP1559: version >= 65,
supportsSnapSync: version >= 66
};
} catch {
// Some clients (e.g., post-Merge) may not support this method
return { protocolVersion: null, supportsEIP1559: true, supportsSnapSync: true };
}
}Error Handling
Common errors and solutions:
| Error Code | Description | Solution |
|---|---|---|
| -32601 | Method not found | Some post-Merge clients no longer support this method |
| -32603 | Internal error | Node may be initializing — retry after delay |
| -32005 | Rate limit exceeded | Reduce request frequency |
Related Methods
web3_clientVersion— Get the client software version stringnet_version— Get the network IDeth_chainId— Get the chain ID (EIP-155)
web3_sha3
Compute the Keccak-256 hash of given data on zkSync Era. Useful for hash verification, smart contract development, and data integrity checks.
eth_mining
Check the legacy eth_mining compatibility method on zkSync Era. Public endpoints often return a client-specific unsupported-method response instead of a boolean.