Peers

Active, healthy BTX peers our node has been observing. Use these to bootstrap a new node or recover from a stuck peer set.

Filter by region
Region Address Subver Score Tip agreement Ping Last seen
loading…

Score combines observation rate, tip agreement, and ping. Tip agreement is the fraction of observations where the peer's reported chain tip matched ours. Peers with <50% tip agreement are excluded.

How to add peers

Temporary (runtime, no restart)

Adds the peer to your live btxd connection set. Lost on restart. Good for testing a peer before committing it to config.

btx-cli addnode "1.2.3.4:19333" add

Use onetry instead of add for a one-off attempt without adding to the persistent addnode list. Use remove to drop a previously-added entry.

Long term (config file)

Survives restarts. Add one or more lines to your btx.conf:

# ~/.btx/btx.conf or %APPDATA%\BTX\btx.conf
addnode=1.2.3.4:19333
addnode=5.6.7.8:19333

Then restart btxd. The addnode directive instructs btxd to keep a persistent outbound connection to that peer (in addition to its normal peer discovery).

Bulk-add the visible list

Once you've filtered the table to a region, you can copy every row's address and add them all at once:

btx-cli addnode "<addr>" add
How fresh is this list? Our node observes peers continuously; this page refreshes every 10 seconds. We rank by tip agreement and ping over a rolling window. Don't pick a peer from this list — pick three or four; redundancy matters.