Add Your Gateway as a Trusted Peer to the Execution Layer Client
To keep your Gateway reliably connected to your execution client, you must add it as a trusted peer. The bloXroute Gateway connects as a peer to your node. If your node hits its peer limit, untrusted connections (like the Gateway) can be dropped unless explicitly allowed.
Why This Matters
Without adding the Gateway to your trusted peers:
Your node may reject the connection.
You risk losing access to the BDN for transaction/block propagation.
Step 1: Get Your Gateway Enode
Each time the Gateway starts, it generates a new enode unless a private key is specified. To make the enode persistent, use the --private-key flag when starting your Gateway.
Generate Keys (Before Starting the Gateway)
To make your Gateway’s enode persistent across restarts, you’ll need to generate a private/public key pair.
Use this guide to generate your key pair: 👉 Generate Gateway Keys (gist)
Once generated, supply the private key using the
--private-keyflag when starting the Gateway to ensure the enode stays consistent.
Get Your Enode (If Gateway Is Already Running)
Option 1: Check startup logs Look for a line like:
Started P2P networking self=enode://<GW_PUBLIC_KEY>Option 2: Use
bxcliwith gRPC Run:docker exec -it bxgateway-go bxcli statusLook under
gateway_info → gateway_public_key.
Step 2: Add Gateway as a Trusted Peer in Your Node
You can choose from the following options:
Temporary (does not persist after restart):
Use JSON-RPC:
Use Geth console:
Recommended (persistent): Edit your Geth config file and add the enode under the
[Node.P2P]section:You can generate a config from your current setup using:
Last updated