RICHXCHAIN

Ask PAUL.

PAUL speaks for RichX Chain. Pick a question — he answers from the published documentation, nothing else.

Tap a question.

Read live from the node.

RPC · reading…

Add RichX Chain to your wallet.

• Network RichX Chain · Chain ID 20260903 (0x1352827)
• RPC https://rpc.richxchain.com
• Currency RICHX · 18 decimals · Explorer richxscan.com

{
 "chainId": "0x1352827",
 "chainName": "RichX Chain",
 "nativeCurrency": {
  "name": "RichX Coin",
  "symbol": "RICHX",
  "decimals": 18
 },
 "rpcUrls": [
  "https://rpc.richxchain.com"
 ],
 "blockExplorerUrls": [
  "https://richxscan.com"
 ]
}

Talk to the chain.

Standard Ethereum JSON-RPC over HTTPS. Every EVM library works out of the box — no custom SDK.

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

# response shape: {"jsonrpc":"2.0","id":1,"result":"0x…"}   (hex block height)

COPY// ethers v6
import { JsonRpcProvider, formatEther } from 'ethers';
const provider = new JsonRpcProvider('https://rpc.richxchain.com', 20260903);
const block = await provider.getBlockNumber();
const wei = await provider.getBalance('0xYOUR_ADDRESS');
console.log(formatEther(wei), 'RICHX');

COPY// ethers v5
const { ethers } = require('ethers');
const provider = new ethers.providers.JsonRpcProvider('https://rpc.richxchain.com');
const block = await provider.getBlockNumber();
const wei = await provider.getBalance('0xYOUR_ADDRESS');
console.log(ethers.utils.formatEther(wei), 'RICHX');

COPY// web3.js v4
const { Web3 } = require('web3');
const web3 = new Web3('https://rpc.richxchain.com');
const block = await web3.eth.getBlockNumber();
const wei = await web3.eth.getBalance('0xYOUR_ADDRESS');
console.log(web3.utils.fromWei(wei, 'ether'), 'RICHX');

Compile for London.

RichX Chain targets the London EVM. Shanghai and later emit the PUSH0 opcode, which this chain does not recognise — deployment or execution fails. Always compile with --evm-version london.

COPY// hardhat.config.js
module.exports = {
  solidity: {
    version: '0.8.20',
    settings: { optimizer: { enabled: true, runs: 200 }, evmVersion: 'london' }
  },
  networks: {
    richxchain: { url: 'https://rpc.richxchain.com', chainId: 20260903, accounts: [process.env.PRIVATE_KEY] }
  }
};
// deploy:  npx hardhat run scripts/deploy.js --network richxchain

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

• Solidity 0.6.x – 0.8.x · gas paid in RICHX · minimum gas price 1 gwei
• Remix: Advanced Configurations → EVM version london, optimisation 200 → Environment “Browser Extension” → check Custom (20260903)

RXC-20 — fully compatible with ERC-20.

The token standard on RichX Chain: the ERC-20 interface with the same function signatures and the same events, so wallets, routers, indexers and exchanges work unchanged. RXC-20 is the standard. RICHX is the coin.

• name · symbol · decimals · totalSupply · balanceOf · allowance · transfer · approve · transferFrom
• Transfer(address,address,uint256) · Approval(address,address,uint256)
• Transfer topic 0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef
• Gas is always paid in RICHX — never in the token itself

Ethicoin integration.

9 decimals, not 18. Read decimals() from the contract — assuming 18 misprices every balance by a factor of a billion. No transfer fee. No mint function.

COPY// ethers v6 — read ETHIC+ correctly (9 decimals, read them from the contract)
const ETHIC = '0x7023Bb290be415b05491bBBaa45f4D15e4407E46';
const abi = ['function decimals() view returns (uint8)', 'function balanceOf(address) view returns (uint256)',
             'function maxTxAmount() view returns (uint256)', 'function paused() view returns (bool)'];
const t = new Contract(ETHIC, abi, provider);
const d = await t.decimals();                       // 9 — never hardcode 18
console.log(formatUnits(await t.balanceOf('0xWALLET'), d), 'ETHIC+');

COPY{"jsonrpc":"2.0","method":"eth_getLogs","params":[{
  "fromBlock":"0x…","toBlock":"0x…",
  "address":"0x7023Bb290be415b05491bBBaa45f4D15e4407E46",
  "topics":["0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"]
}],"id":1}

Listing RICHX and ETHIC+.

• Finality: one confirmation is final. If policy needs a count, 3 blocks = 15 seconds.
• RICHX deposits: poll blocks, match tx.to + value > 0, confirm receipt status 0x1. Withdrawal ≈ 0.000021 RICHX gas.
• ETHIC+ deposits: Transfer logs on the contract, credit the indexed “to”, confirm status 0x1. Withdrawal ≈ 0.000052 RICHX gas.
• Exchange wallets must be exempted from the per-tx cap before large movements — send deposit, hot and cold addresses; every exemption emits a public event.
• Custom errors: OverTxLimit · IsPaused · Blacklisted_ · InsufficientBalance · NotApproved · ZeroAddress

Disclosure: ETHIC+ has two administrative keys (owner and guardian) on separate devices. Neither can create tokens or add a fee; ownership transfer needs a 48-hour public timelock. Addresses can be frozen only after a public proposal and a ten-minute wait.

Proof of authority — said plainly.

Validators are admitted by vote of the existing validator set through the QBFT voting API. It is not permissionless. The set is small today; if block production stops, transfers stop until it is restored — balances are unaffected. Expansion is planned through voting, with no new genesis and no change to any contract address. Validators receive no block reward.

• Ubuntu 22.04 LTS · Hyperledger Besu 26.8.1+ · Java 25 (Temurin)
• 2 cores · 4 GB RAM · 50 GB SSD · static IP
• P2P 30303 open · RPC 8545 bound to localhost only — never public without authentication and rate limits
• Validator key generated on the machine itself, never transmitted; encrypted off-machine backup

Two things not to confuse.

RichX Chain is the only home of ETHIC+. The BNB Chain route is closed — do not send tokens to the old bridge addresses. Holders of the legacy BNB Chain token migrate one for one by arrangement: support@richxchain.com.

Historical record, not instructions: BNB bridge 0xbE2BBce3CE7377Da0fBD897535C8F769B62b9E9D · RichX side 0x914B911A60Ab3f09970189cAfE9c3B4D5d575894

A separate chain that only timestamps published content (SHA-256 hashes). It carries no value and no claim; about a thousand verification links point at it, so it keeps running. Never build on it. Use chain 20260903 and https://rpc.richxchain.com for everything.

Common errors.

• Chain ID mismatch — Use 20260903 (0x1352827).
• Transaction underpriced — Gas price at least 1 gwei.
• Insufficient funds — The wallet needs RICHX for gas.
• Invalid opcode / deploy fails — Recompile with --evm-version london (no PUSH0).
• Nonce too low — Reset the account nonce in the wallet.
• Contract not found — Check the address and that you are on chain 20260903, not the notary chain.
• OverTxLimit (ETHIC+) — Split the transfer or request an exemption.
• IsPaused (ETHIC+) — The contract is paused — check paused(), retry when resumed.

RichX Chain on your home screen.

One tap, no app store. The documentation and the live network status open full-screen like an app, and work offline for the pages you have read.