On the consensus layer (eth2) network, we offer direct peering connections to our nodes. As a result, your connected beacon node will receive blocks over the P2P connection as soon as our network sees them. This can result in a significant latency decrease compared to the standard P2P network: anywhere from 500ms to 2 seconds. For more information about FiberGuard, check out this section in the use cases.
We assume that you've signed up for the FiberGuard plan and we have your peer ID and ENR registered in our system.
To get this information about your node, you can query the following endpoint:
Once you've signed up for the plan, you will have received the multiaddress of
one of our nodes based on your location. A multiaddress looks like this:
multiaddress encodes the network information (IP address and TCP port), as well as the P2P peer ID (
Static Peer ID
Ideally, you have configured your node with a static peer ID so we don't have to go through the process of registering your information every time you restart your beacon node. Instructions on how to do that for the major consensus clients can be found below:
Enabled by default.
Add the following CLI option to the startup command:
Enabled by default.
Specify a file that contains a private key using the following option:
For ensuring the most reliable connection, your beacon node should add the Fiber peer as a static and trusted peer. Static means the connection will always be retried on failure. Trusted means the peer is safe from any peer scoring systems or pruning routines. Below we outline how to do this for the different consensus clients:
Lighthouse requires 2 options to be set. Static multiaddress:
With Prysm, you can add a trusted, static peer with the following flag:
Teku provides multiple ways to add a static, trusted peer: https://docs.teku.consensys.net/development/reference/cli#p2p-static-peers.
The easiest way is to add the following CLI flag to the startup command:
With Nimbus, you can add a trusted, static peer with the following flag:
Checking the Connection
If everything went well, your beacon node should now be connected to our Fiber node. You can check the connection status by querying the beacon API (usually on port 5052).
<PEER_ID> is the peer ID of the Fiber node.
The response should indicate a
connected state like in the example response below: