state_getRuntimeVersion | Hydration RPC Docs

Get the runtime version on Hydration. Essential for compatibility checking, upgrade detection, and transaction construction on Polkadot's leading DEX with $200M+ TVL, Omnipool AMM, and native HOLLAR stablecoin.

Returns the runtime version information for Hydration, including the spec name, spec version, implementation version, and supported API versions.

Why Hydration? Build on Polkadot's leading DEX with $200M+ TVL, Omnipool AMM, and native HOLLAR stablecoin with Omnipool with reduced slippage, permissioned listings, 3M DOT DAO allocation, and 200%+ APR farm yields.

When to Use This Method

state_getRuntimeVersion is essential for DeFi developers, liquidity providers, and DAOs requiring capital-efficient trading:

Version Checking — Verify runtime compatibility before constructing transactions on Hydration
Upgrade Detection — Monitor for runtime upgrades that may change chain behavior for single-sided liquidity provision, cross-chain trading (SOL, KSM, tBTC), and HOLLAR decentralized stablecoin
Transaction Construction — Include the correct specVersion and transactionVersion in signed extrinsics
API Compatibility — Check which runtime APIs are available and at what version

Code Examples

Common Use Cases

1. Runtime Upgrade Monitor

Detect runtime upgrades on Hydration in real time:

JavaScript

async function monitorUpgrades(api) {
  let currentVersion = (await api.rpc.state.getRuntimeVersion()).specVersion.toNumber();
  console.log(`Starting monitor at spec version: ${currentVersion}`);

  const unsub = await api.rpc.chain.subscribeNewHeads(async (header) => {
    const version = await api.rpc.state.getRuntimeVersion(header.hash);
    const newVersion = version.specVersion.toNumber();

    if (newVersion !== currentVersion) {
      console.log(`Runtime upgrade detected! ${currentVersion} -> ${newVersion}`);
      currentVersion = newVersion;
      // Trigger reconnection or metadata refresh
    }
  });

  return unsub;
}

2. Transaction Construction with Correct Version

Include the correct version fields when constructing signed extrinsics:

JavaScript

async function getSigningPayloadInfo(api) {
  const version = await api.rpc.state.getRuntimeVersion();
  const genesisHash = await api.rpc.chain.getBlockHash(0);

  return {
    specVersion: version.specVersion.toNumber(),
    transactionVersion: version.transactionVersion.toNumber(),
    genesisHash: genesisHash.toHex(),
    // These fields are required for signing extrinsics
  };
}

3. Historical Version Comparison

Compare runtime versions across blocks to identify upgrade boundaries:

JavaScript

async function findUpgradeBlock(api, startBlock, endBlock) {
  const startHash = await api.rpc.chain.getBlockHash(startBlock);
  const startVersion = (await api.rpc.state.getRuntimeVersion(startHash)).specVersion.toNumber();

  // Binary search for upgrade block
  let low = startBlock;
  let high = endBlock;

  while (low < high) {
    const mid = Math.floor((low + high) / 2);
    const midHash = await api.rpc.chain.getBlockHash(mid);
    const midVersion = (await api.rpc.state.getRuntimeVersion(midHash)).specVersion.toNumber();

    if (midVersion === startVersion) {
      low = mid + 1;
    } else {
      high = mid;
    }
  }

  console.log(`Runtime upgraded at block #${low}`);
  return low;
}

Error Handling

Error Code	Description	Solution
-32603	Internal error	Node may be syncing — retry with backoff
-32602	Invalid params	Verify block hash format is valid hex with `0x` prefix
-32601	Method not found	Verify the node supports this RPC method
-32005	Rate limit exceeded	Implement client-side rate limiting

state_getMetadata — Get full runtime metadata for decoding
system_version — Get node software version
chain_subscribeFinalizedHeads — Subscribe to detect upgrade blocks

state_getRuntimeVersion - Hydration RPC Method

When to Use This Method

Code Examples

Common Use Cases

1. Runtime Upgrade Monitor

2. Transaction Construction with Correct Version

3. Historical Version Comparison

Error Handling

On this page