The method page now says which chain the Data Desk's figures describe: the one mempool.space and Blockstream's Esplora serve, under Bitcoin Core's consensus rules, named by its block at height 961,632, 00000000000000000000d1e01392faa65ceeaed307f0a3159144b84146ff24ba, whose version, 0x20006000, does not set bit 4, which BIP 110 required of blocks 961,632 to 963,647. Bitcoin Knots releases that enforce BIP 110, from 29.3.knots20260508, and from 29.4.1 a BLAKE2b proof of work, follow a different chain, which these figures do not cover. Naming the chain takes no side on relay policy. Nodes & releases now also counts the peers announcing Knots' two service flags, NODE_BLAKE2B (bit 28) and NODE_REDUCED_DATA (bit 27), over all connected peers and among the Knots peers: in KIT's snapshot of 30 September, 408 of the 1,003 Knots peers announced the BLAKE2b flag, 133 the reduced-data flag only and 462 neither. Flags are self-announced, and the desk cannot see which chain a peer follows. The three snapshots already recorded gained the count only after each file, read again, matched its recorded sha256 and gave every count the row holds; no recorded figure changed. Node software method 1.1.0.
Data Desk