THORChain Churn & P2P Monitor

Waiting for churn
Creating new vaults
Moving funds

Connecting to the node…

Current block —

Next churn —

Vaults

—

New vaults

—

receiving funds

Old vaults

—

emptying, then retired

Being created

—

keygen done, not active yet

Vault creation (keygen) — last 600 blocks

Succeeded —

Failed —

Churn attempts

—

Blocks	Succeeded	Failed	Result

Nodes blamed for failures

—

Failures	Node

Browser-only view. The original tci nodes debug-p2p fans out to http://<ip>:6040/status/p2p on every node — a browser can't reach those (mixed content + CORS). What you see here: the bifrost peer registry from /thorchain/nodes and the Tendermint P2P view from the selected RPC's /net_info, cross-referenced by IP.

Candidates

—

Active + Ready ≥ threshold

Tendermint Peers

—

connected to selected RPC

Reachable

—

candidates matched by IP

Bond Threshold

Filters the candidate set: nodes with total bond ≥ this threshold are expected to be peers of every other candidate. Default 300,000 matches the CLI's --threshold.

Bifrost Peer Registry

—

Status	Operator	Node	Bond	IP	Peer ID	RPC sees

Tendermint Peers

—

Run the Full P2P Audit

For per-node fan-out (port 6040), use the inspector CLI:

tci nodes debug-p2p --threshold 300000

THORCHAIN

Vaults

Funds moving to the new vaults

Active nodes not in any new vault

Vault creation (keygen) — last 600 blocks

Churn attempts

Nodes blamed for failures

Bond Threshold

Bifrost Peer Registry

Tendermint Peers

Run the Full P2P Audit

Vaults

Funds moving to the new vaults i How the move works Loading network settings…

Active nodes not in any new vault

Vault creation (keygen) — last 600 blocks

Churn attempts

Nodes blamed for failures

Bond Threshold

Bifrost Peer Registry

Tendermint Peers

Run the Full P2P Audit

Funds moving to the new vaults