Using Node as RPC URL endpoint
How to connect your ETH wallet to your own node's RPC endpoint
π Reasons to use your own NODE as RPC URL 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
π€ How to use your NODE as a RPC endpoint
1. Verify RPC port 8545 is listening
Double check that your node is listening on port 8545
ss -ntlp | grep 8545
For example, here's the output for Besu with RPC enabled.
LISTEN 0 128 [::ffff:127.0.0.1]:8545 *:* users:(("java",pid=26453,fd=433))
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
--http
Besu
--rpc-http-enabled=true
--rpc-http-cors-origins="*"
Changes can be made to the systemd unit file execution.service,
sudo nano /etc/systemd/system/execution.service
To exit and save, press Ctrl
+ X
, then Y
, then Enter
.
Make sure to reload and restart.
sudo systemctl daemon-reload
sudo systemctl restart execution
2. Create a SSH tunnel
Example of how to create a SSH tunnel in Linux or MacOS:
ssh -N -v <user>@<staking.node.ip.address> -L 8545:localhost:8545
#Full Example
ssh -N -v ethereum@192.168.1.69 -L 8545:localhost:8545
3. Configure wallet to use RPC URL
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.
Last updated