How to Safely Use Custom Nodes¶
This page shows you how to choose a custom RPC endpoint, check whether it is telling you the truth, and remove it if it is not.
The trust boundary
A third-party node sees your IP address and the addresses you query, and it decides what your wallet displays. It cannot sign for you. It can mislead you until you do.
Who this is for¶
Read this if you added a custom RPC, are considering one, or your wallet shows a balance you cannot explain. If you use the default Bitgold endpoint and it works, skim the checks and move on.
Before you start¶
- A wallet with Bitgold added, and the RPC URL you are using now.
- Your address, and the explorer at www.bitgold.live bookmarked.
- The name of whoever gave you the new endpoint. "A group chat" is not a source.
Steps¶
1. Write down the endpoint you have¶
Note the current RPC URL before anything changes. The mainnet entry point is https://mainnet1.bitgold.network; keep it somewhere you can copy from. If the new node misbehaves, this line is how you get back.
2. Compare one address in two places¶
Enter your address on the explorer and read the balance and the last few transactions. Then look at the same address in your wallet with the custom node active. The numbers should match, including the newest transaction.
3. Send a test amount before you trust it¶
Move a small amount of BTG and confirm the recipient and the amount on the wallet screen before you approve. Then check that the explorer shows the same transfer. A node that hides or rewrites a pending transaction is showing you its own version of the chain.
4. Switch back to a trusted endpoint¶
Open the network settings for Bitgold and replace the RPC URL with a Bitgold endpoint. Menu paths differ between wallet versions, so look for the network list rather than a specific label. Save, then reload the wallet.
5. Delete the custom network if anything disagreed¶
If balances, transactions, or confirmation screens did not match, remove the network entry and add Bitgold again from the official fields. An entry left in place keeps returning the same wrong data.
If you typed your recovery phrase into a node dashboard, a "sync" page, or a support form at any point, stop treating that wallet as safe. Create a new wallet and move the balance. No legitimate node needs your phrase.
Verify it worked¶
- Your wallet balance and the explorer balance agree.
- The most recent transaction in the wallet is one the explorer also shows.
- The network list contains only endpoints you can name a source for.
- No approval or transfer appears that you did not start.
Troubleshooting¶
| Problem | What to do |
|---|---|
| The wallet shows a balance the explorer does not | The endpoint is stale or lying. Switch back to a Bitgold endpoint before you spend or sign anything. |
| The custom RPC fails to connect | The URL is wrong or the provider is down. Restore https://mainnet1.bitgold.network and check the entry character by character. |
| A transaction stays pending in the wallet but is confirmed on the explorer | The node stopped relaying. Switch endpoints; the transaction itself is already settled. |
| The provider asks you to "validate" the wallet by entering a phrase | Never enter it. Remove the endpoint, then treat the wallet as exposed and move the balance. |
| The wallet keeps reverting to the old endpoint | Delete the network entry. Some wallets keep a cached URL until you remove it. |
Next steps¶
- Fake RPC Nodes, Fake Balances — how a node fakes a balance and what that changes.
- Beware of Custom RPC Node Scams — why "a faster node" is a request to shape what you sign.
- How to Verify the Wallet App — check the app before you check its settings.
Self-check¶
- I can name who provided the RPC URL currently in use.
- My wallet balance matches the explorer balance.
- I have never entered a recovery phrase into a node dashboard.
- I know how to delete a network entry from my wallet.