Developer Documentation

Get current block number

curl -X POST https://rpc.richxchain.com \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Using ethers.js

const { ethers } = require('ethers');
const provider = new ethers.providers.JsonRpcProvider(
  'https://rpc.richxchain.com'
);
const block = await provider.getBlockNumber();
const balance = await provider.getBalance('YOUR_ADDRESS');
console.log(ethers.utils.formatEther(balance), 'RXC');

Using Web3.js

const Web3 = require('web3');
const web3 = new Web3('https://rpc.richxchain.com');
const block = await web3.eth.getBlockNumber();

Hardhat config

// hardhat.config.js
module.exports = {
  solidity: '0.8.19',
  networks: {
    richxchain: {
      url: 'https://rpc.richxchain.com',
      chainId: 20260903,
      accounts: [process.env.PRIVATE_KEY]
    }
  }
};

Deploy

npx hardhat run scripts/deploy.js --network richxchain

Remix IDE

Open remix.ethereum.org → Solidity Compiler → Advanced Configurations → set EVM Version to london, tick Optimization, 200 runs → Compile. Then Deploy & Run → Environment → "Browser Extension" (older Remix calls this "Injected Provider") → confirm the panel reads Custom (20260903) → Deploy.

Why the name

The "20" is a ticket number, not a version. The token interface was filed as request for comments number 20 on Ethereum in 2015 and the number stuck. BNB Chain calls the same interface BEP-20, Tron calls it TRC-20. RXC-20 is the same thing on RichX Chain, and naming it that way tells an engineer immediately that their existing code applies.

Compiling for this chain

RichX Chain targets the London EVM. Shanghai introduced the PUSH0 opcode, which this chain does not recognise — a contract compiled for Shanghai or later will fail here.

solc --optimize --optimize-runs 200 --evm-version london MyToken.sol

# hardhat.config.js
solidity: {
  version: '0.8.20',
  settings: {
    optimizer: { enabled: true, runs: 200 },
    evmVersion: 'london'
  }
}

Tokens live on this chain

Reading balance

const ETHIC_ADDRESS = '0x7023Bb290be415b05491bBBaa45f4D15e4407E46';
const ETHIC_ABI = [
  'function balanceOf(address) view returns (uint256)',
  'function transfer(address to, uint256 amount) returns (bool)'
];
const contract = new ethers.Contract(ETHIC_ADDRESS, ETHIC_ABI, provider);
const balance = await contract.balanceOf('WALLET_ADDRESS');
console.log(ethers.utils.formatUnits(balance, 9), 'ETHIC+');

Note: ETHIC+ has 9 decimals, not 18. One ETHIC+ is 1,000,000,000 base units. Read decimals() from the contract rather than hardcoding it — assuming 18 will misprice every balance by a factor of a billion.

No transfer fee. Send 1,000 ETHIC+ and the recipient receives 1,000. Earlier versions of this token charged 1% on transfer; the deployed contract on RichX Chain does not, and no fee code was compiled into it.

Per-transaction cap. Transfers above maxTxAmount() revert with OverTxLimit. The current cap is 1,000,000,000 ETHIC+. Exchange and treasury addresses can be exempted — contact us with the addresses and we will grant it. Check with isExemptFromTxLimit(address).

What it does

The notary chain records a SHA-256 hash of published content at the moment of publication. Roughly a thousand pages across the wider network carry a verification link pointing at it, so the chain keeps running and those links keep resolving. It is a timestamping service, and its coin has no market and is not intended to.

Why it was not migrated

Two reasons. Replacing it would break every existing verification link, and a content stamp whose proof returns a 404 is worse than no stamp at all. And a notary does not need what a financial network needs — immediate finality, a maintained client, exchange integration. Retiring it would have destroyed something valuable to solve a problem it does not have.

What this means for you

Nothing on the notary chain carries value or any claim. A token deployed there is deprecated and holds no relationship to the live contracts. Use chain 20260903 and https://rpc.richxchain.com for everything. If you find an older document referencing chain 20260618 as the main network, it predates September 2026 and is superseded by this page.