An RPC endpoint is
not a node: one address can front a whole fleet of
them, and none of these publish a peer list, so they cannot be counted
alongside the census above. What can be checked is what each one serves.
BDAGScan's nodes run the older protocol and cannot peer with ours,
which is why they never appear in the node list — this is the only
view we have of that side of the network.
- Chain is decided by hash, never by height. Every endpoint is
asked for the block at a settled height well below both heads, and the
answers are compared. Matching hashes mean one chain; different hashes
at the same height mean a fork, whatever the heights say.
- These heights are EVM block numbers, which is a different count
from the DAG main-chain height in the node list above. Compare them with
each other, not with the table above.