What Is a Custom Network?¶
Bitgold is not on the default network list of most wallets. This page explains the five values that connect a wallet to Bitgold, so you can add the network and recognize a bad configuration.
Who this is for¶
Anyone adding Bitgold to an EVM wallet for the first time, or checking a profile someone else gave them. If Bitgold already shows a balance, skip to the task pages.
What it is¶
A custom network is five values that tell an EVM wallet which chain to read, how to label it, and where to open its history. Wallets ship with a short default list chosen by the wallet maker, usually Ethereum and a few large chains.
Bitgold is an independent, EVM-compatible Layer 1, so it is not on that list. You add it the same way as any other EVM chain.
The values for each Bitgold network:
| Field | Mainnet | Testnet |
|---|---|---|
| Network name | Bitgold Mainnet | Bitgold Testnet |
| RPC URL | https://mainnet1.bitgold.network |
https://testnet1.bitgold.network |
| Chain ID | 618 |
617 |
| Currency symbol | BTG |
tBTG |
| Block explorer URL | https://www.bitgold.live |
https://testnet.bitgold.live |
If mainnet1 is slow or unreachable, the same service answers on mainnet2 through mainnet6, and on mainnet-jp, mainnet-sg, and rpc, all under bitgold.network. Testnet backups are testnet2 and testnet3. Change only the leading label and keep the full https:// URL.
Each field has one job:
- Network name is a label in the wallet's network list. A wrong name is only confusing.
- RPC URL is the endpoint your wallet uses to read balances and broadcast transactions. A dead URL leaves the wallet blank; a dishonest one can report false data.
- Chain ID identifies the actual chain, and your wallet signs it into every transaction. A wrong chain ID puts you on another network or makes the wallet reject the profile. Mainnet is decimal
618; some forms ask for hex, which is0x26a. - Currency symbol is the ticker shown for the native coin. BTG uses 18 decimals. A wrong symbol changes the label, not the balance or the amount.
- Block explorer URL only builds the "view on explorer" links. A wrong one breaks those links and nothing else.
Why it matters¶
Mainnet and testnet are separate ledgers. Mainnet BTG has value and testnet tBTG does not; a testnet balance will never appear on mainnet, and the Bitgold faucet only issues tBTG. Use testnet to practice, then repeat on mainnet.
A custom RPC is a trust decision. The endpoint sees your IP and every address you look up, and it can return a false balance or hide a transaction.
It cannot sign for you, but it can show a convincing false result. Treat any RPC from a stranger as unsafe, and compare its hostname with the table above.
Common misunderstandings¶
- "Adding a custom network creates a new wallet." It does not. The same recovery phrase produces the same address on every EVM chain; the network profile only changes which chain the wallet displays.
- "A zero balance means the funds are gone." Check the chain ID and the explorer first. A wallet on the wrong network, or behind a bad RPC, often shows nothing.
- "Any RPC that loads is trustworthy." A fast endpoint can still lie; working is not the same as honest.
Key takeaways¶
- A custom network is five values: name, RPC URL, chain ID, symbol, and explorer URL.
- Mainnet is chain ID
618with symbolBTG; testnet is617withtBTG. - The chain ID decides which chain you are on; the RPC decides what you are shown.
- Use the official endpoints, and switch to a backup label if one fails.
Next steps¶
- Add Bitgold Network (TokenPocket) — add the profile on a phone.
- Add Bitgold Network (MetaMask) — add the same profile in a browser.
- How to Safely Use Custom Nodes — how a third-party RPC can mislead you.