Docs

system_version - XX Network RPC Method

Get the node implementation version on XX Network. Essential for compatibility checking, runtime upgrades, and monitoring node deployments across the a privacy-focused decentralized messaging and payment platform network.

Returns the node implementation version string on XX Network. This version reflects the client software version (e.g., 0.9.43-ba6af1743a0), not the on-chain runtime version.

Why XX Network? Build on a privacy-focused decentralized messaging and payment platform with quantum-resistant cryptography and metadata privacy through cMix.

When to Use This Method

system_version is essential for XX Network developers building privacy-preserving applications:

  • Compatibility Checking -- Verify the node client version supports the features your application requires on XX Network
  • Upgrade Monitoring -- Track node software versions across your validator or collator fleet after runtime upgrades
  • Diagnostics and Debugging -- Include version information in bug reports and support requests for secure messaging, private payments, and quantum-resistant cryptography
  • Multi-Node Management -- Ensure all nodes in your infrastructure are running consistent versions

Code Examples

Common Use Cases

1. Node Fleet Version Monitoring

Track version consistency across multiple XX Network nodes:

JavaScript
import { ApiPromise, WsProvider } from '@polkadot/api';

async function checkFleetVersions(endpoints) {
  const versions = await Promise.all(
    endpoints.map(async (endpoint) => {
      const provider = new WsProvider(endpoint);
      const api = await ApiPromise.create({ provider });
      const version = await api.rpc.system.version();
      const name = await api.rpc.system.name();
      await api.disconnect();
      return { endpoint, version: version.toString(), name: name.toString() };
    })
  );

  const unique = new Set(versions.map((v) => v.version));
  if (unique.size > 1) {
    console.warn('Version mismatch detected across fleet!');
  }

  versions.forEach((v) => {
    console.log(`${v.endpoint}: ${v.name} v${v.version}`);
  });
}

2. Pre-Upgrade Compatibility Check

Verify node version before executing operations:

JavaScript
async function ensureMinVersion(api, minVersion) {
  const version = await api.rpc.system.version();
  const versionStr = version.toString();
  const [major, minor, patch] = versionStr.split('-')[0].split('.').map(Number);
  const [minMajor, minMinor, minPatch] = minVersion.split('.').map(Number);

  if (
    major < minMajor ||
    (major === minMajor && minor < minMinor) ||
    (major === minMajor && minor === minMinor && patch < minPatch)
  ) {
    throw new Error(
      `Node version ${versionStr} is below minimum ${minVersion}`
    );
  }

  console.log(`Node version ${versionStr} meets minimum ${minVersion}`);
  return true;
}

3. Node Identity Dashboard

Gather full node identity information:

JavaScript
async function getNodeIdentity(api) {
  const [version, name, chain, properties] = await Promise.all([
    api.rpc.system.version(),
    api.rpc.system.name(),
    api.rpc.system.chain(),
    api.rpc.system.properties()
  ]);

  return {
    client: name.toString(),
    version: version.toString(),
    chain: chain.toString(),
    tokenSymbol: properties.tokenSymbol.toString(),
    ss58Format: properties.ss58Format.toString()
  };
}

Error Handling

Common errors and solutions:

Error CodeDescriptionSolution
-32603Internal errorNode may be starting up -- retry after delay
-32005Rate limit exceededReduce request frequency or implement client-side rate limiting
Connection refusedNode unreachableVerify the RPC endpoint URL and that the node is running