How to add the OMC testnet to your wallet (MetaMask, 4 fields)

OMC settles its compute jobs on BNB Chain. While the network is in public testnet, the place to practise is BNB Smart Chain Testnet — the same EVM tooling as mainnet BNB Chain, with free gas and a disposable token called tOMC that exists purely so you can stake it, pay fees with it and watch it move.

You need two separate things, and it's worth keeping them apart: adding the network (so your wallet can talk to the chain) and importing the token (so the tOMC balance shows up in your wallet UI). The network is mandatory for anything to work; the token import is cosmetic but makes the whole thing much less confusing.

The four fields you need

This is the table OMC publishes on omc.network/testnet. We re-checked it on 2026-10-09 by calling eth_chainId on the RPC endpoint and reading the token contract — the values below are what the chain actually returns.

Add it in MetaMask

1. Open MetaMask and click the network selector at the top left (it shows your current network name).
2. Choose Add a custom network (older builds: Settings → Networks → Add a network → Add a network manually).
3. Paste the values from the table above. Network name and symbol are free text — chain ID and RPC URL are what actually matter.
4. Save and switch to it. Your tBNB balance will show as 0 until you get test gas — that is expected, not an error.
5. Get free test gas: open the BNB Chain faucet, paste your address, request tBNB. This covers gas for every testnet transaction.
6. If you also need tOMC (for staking on the testnet, or to see the token in your wallet), use the testnet faucet linked on omc.network/testnet, then import the token — next section.

Importing tOMC

In MetaMask: Import tokens → paste the contract address below → the symbol and decimals should fill in automatically. If they don't, type them manually. Both should match the table — we read them straight from the contract, so a mismatch means you're on the wrong chain or pasted the wrong address.

To confirm independently, paste the address into testnet.bscscan.com. If the contract page doesn't exist, you're on mainnet BscScan rather than the testnet explorer.

The five things that actually go wrong

• "Could not fetch chain ID" / RPC timeouts. Public testnet RPCs rate-limit. Wait thirty seconds and retry; if it persists, use a different public BNB testnet RPC — any node synced to chain 97 works.
• The token shows 0 after importing. Importing a token doesn't mint anything. The balance stays 0 until the faucet sends you some, or until you receive a testnet transfer.
• Balance shows 0 after switching networks. Correct behaviour — the same address holds different balances on mainnet and testnet. Check the network selector before you panic.
• Anything asking you to "swap" or "bridge" tOMC. There is nothing to swap. tOMC is a test token with no market, no liquidity and no value. A swap prompt for it is either a bug or a scam.
• "Add token" requests you didn't initiate. Tokens appearing in your wallet unprompted are a standard dusting trick. Nothing about adding a custom network requires you to interact with an unknown contract.

Once the network is added and you have test gas, the rest of the testnet opens up: staking a deposit and registering a node heartbeat if you have a GPU, or simply watching jobs and balances move. The two follow-up guides cover both paths — the wallet is the boring prerequisite for either.