⚡Using Node as RPC URL endpoint
How to connect your ETH wallet to your own node's RPC endpoint
How to connect your ETH wallet to your own node's RPC endpoint
Privacy: No spying by middleman between you and the blockchain
Trustless verification: Ability to verify the ETH transaction data you see is raw and not manipulated
Decentralization: No need to depend on Infura or other centralized 3rd parties
Coolness and credibility: Using Ethereum as it was meant to be, a step towards being more sovereign
Before continuing please understand the following:
As this method uses SSH tunneling, no changes are required to your firewall or router's port forwarding
Double check that your node is listening on port 8545
For example, here's the output for Besu with RPC enabled.
Port 8545 is NOT listening or using Geth or Besu?
Note: Nethermind and Erigon enable RPC by default.
The following flags on the ExecStart
line are required to enable RPC.
Geth
Besu
Changes can be made to the systemd unit file execution.service,
To exit and save, press Ctrl
+ X
, then Y
, then Enter
.
Make sure to reload and restart.
Every time you want to use your node as an RPC endpoint, you must open a SSH tunnel connection with port 8545 forwarded.
Exception: Local nodes (i.e. using Ubuntu Desktop) - if you're accessing your wallet on the same machine as your node, skip this step.
Example of how to create a SSH tunnel in Linux or MacOS:
When configuring your wallet, you can reference the following network information:
Here are steps to configure popular wallets to use a custom RPC URL endpoint.
Great job! You're now using your own node as your own RPC URL endpoint.
Network | Chain ID | Block Explorer | Currency |
---|---|---|---|
Mainnet
1
ETH
Holešky
17000
HoleskyETH
Goerli
5
GoerliETH
Sepolia
11155111
SepoliaETH