Background Image

Public Highly-Optimized FIBRE Network

As there is significant benefit in having at least one publicly-available high-speed relay network, I maintain one (with the help of my sponsors).



Connection Details

Each FIBRE node in the network exposes its Bitcoin P2P Port to registered users (see the bottom of the page). The FIBRE codebase running on each is optimized to ensure that Compact Blocks for each new block are made available to peers after only SPV validation of new blocks, without blocking for lock acquisition. While you can connect to FIBRE nodes using clients which do not support Compact Blocks, your block-availability latency will be significantly harmed.

Note that, because bitcoind (for versions of Bitcoin Core prior to 0.14, as well as other forks) treats the -addnode argument as an extra seednode it may use, and not as a connection which it should maintain, it is recommended that you use an external daemon to keep the connection reliable. There is a simple connect-two-bitcoinds-together client available in the Relay Network Client Source Tree (called fibrenetworkclient after you run make) which takes, as arguments, two bitcoind instances, and connects them to each other, reliably reconnecting if one goes down. For those using Bitcoin Core version 0.14 or later, simply using -addnode or the equivalent RPC commands is preferred. Note that Bitcoin Core 0.14 ignores any -addnodes after the first 8, so no more than 8 should be used at any given time.

There are currently 6 nodes, distributed around the globe in order to minimize latency for clients no matter where they are (see map). Per source IP, only one connection to any server on the network is allowed, as connecting multiple times or to multiple locations will not only reduce availability for other users, but will actually increase your own latency (as it will increase the likelihood of packet loss).

IP Address Whitelist

Because this network is targeted at those who need incredibly low-latency block relay (ie miners only), its nodes do not accept connections from anyone, by default. Instead, you must add your source IP address to the whitelist using the form below. The hostnames of the nodes will be displayed after your IP has been whitelisted.

Connection Source IP (v4 or v6):

Relay Network Map