Reachable nodes
countDistinct nodes that accepted a connection during the latest day's crawl.
Dashboard · VantagePlanned
Bitcoin Node Count: Bitcoin Core vs Knots Share
How many reachable Bitcoin nodes run Bitcoin Knots instead of Bitcoin Core?
Reachable Bitcoin nodes by client and version: how many run Bitcoin Core, how many run Bitcoin Knots and how fast v30 is being adopted.
ShareEmail it
Blueprint
What the dashboard will show.
The dashboard as it will open in Vantage. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.
Clients
Reachable nodes by client, and how fast v30 is being adopted.
Bitcoin Core share
%Reachable nodes whose user agent parses as Bitcoin Core, as a share of all reachable nodes.
Bitcoin Knots share
%Reachable nodes whose user agent names Bitcoin Knots, as a share of all reachable nodes.
Core nodes on v30 or later
%Share of reachable Bitcoin Core nodes reporting v30 or a later release.
Nodes by client
countReachable nodes per day split into Bitcoin Core, Bitcoin Knots and other clients over the selected period.
Versions and networks
Releases in use, the networks nodes are reached on and what miners include.
Reached over Tor
%Share of reachable nodes found at a Tor onion address in the latest day's crawl.
Blocks with large OP_RETURN data, 30 days
countBlocks mined in the last 30 days that include OP_RETURN data over the old 80-byte default.
Nodes by network
countReachable nodes on IPv4, IPv6, Tor, I2P and CJDNS in the latest day's crawl.
Core and Knots releases in use
countReachable nodes by client and release, newest first, from the version in each user agent.
- Period
- Last 30, 90 or 365 days
About
What it answers, and for whom.
Bitcoin nodes announce their software in the user agent they send when two nodes connect. Crawling the network every day and recording those user agents gives a count of reachable nodes by client and version: Bitcoin Core, Bitcoin Knots and the rest. This dashboard shows those counts and how they moved through the dispute over Bitcoin Core v30's OP_RETURN policy.
The counts have limits that matter. Only nodes that accept incoming connections can be reached, so nodes behind firewalls go uncounted, and a user agent is self-reported, so it can be changed or faked. Read a share as the share of reachable nodes that claim a client, not as the share of all Bitcoin users, and read it beside what miners actually put in blocks, which relay policy alone does not decide.
Method
How it will be measured.
Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.
How receipts work →- A crawler connects to every reachable node it can find on IPv4, IPv6, Tor, I2P and CJDNS each day and records the user agent and protocol version from each version message.
- User agents are parsed into client and version: Bitcoin Core, other implementations and Bitcoin Knots, which adds its own name and release to the string. Strings that do not parse count as other.
- A node is counted once per day by its address; a node reachable on several networks can appear once per network, and the page says so beside each total.
- The miner-side tile counts blocks that include OP_RETURN data over the old 80-byte default, read from the blocks themselves rather than from the crawl.
The data it needs
Mostly off-chain sources, cited
- bitcoin_network_dailyTo buildBitcoin network by dayBlocks, hashrate implied by difficulty, difficulty, fees, transaction counts, block weight and miner revenue (subsidy plus fees) per day.
- A daily crawl of the Bitcoin P2P network on IPv4, IPv6, Tor, I2P and CJDNS
- Version messages from each reachable node: user agent, protocol version and services
- OP_RETURN outputs in each block, for blocks carrying data over the old default
Questions
Questions people ask.
How many Bitcoin nodes are there?
Reachable nodes, the ones that accept incoming connections, can be counted by crawling, and this page shows that count each day. Many nodes do not accept incoming connections and cannot be counted this way, so the total number of nodes is larger than any crawl shows.
What is Bitcoin Knots?
A full node implementation derived from Bitcoin Core and maintained separately, with more restrictive default policies on what it relays, including OP_RETURN data. It follows the same consensus rules, so Knots and Core nodes accept the same blocks.
Why did Bitcoin Knots gain nodes?
Interest rose with the debate over Bitcoin Core v30, which relaxed the default OP_RETURN limit. Some operators who opposed the change switched to Knots and others stayed on older Core releases; the version chart shows both moves.
Can node counts be faked?
Yes. A user agent is just a string a node sends, and one machine can run many nodes. The page reports what reachable nodes claim and does not weight them, so a share is an indicator, not a vote.
Do node shares decide what goes into blocks?
No. Miners choose the transactions in their blocks, and any transaction that follows the consensus rules is valid. Relay policy only affects how easily a transaction reaches miners, which is why blocks with large OP_RETURN data are shown beside the node shares.
- Reachable node
- A node that accepts incoming connections from other nodes, so a crawler can connect to it.
- User agent
- The software name and version a node reports when it connects to a peer.
- Relay policy
- The rules a node applies to unconfirmed transactions before passing them on, stricter than the consensus rules.
Related
More apps like this.
Bitcoin OP_RETURN Usage After Bitcoin Core v30
OP_RETURN outputs in Bitcoin blocks each day: how many, how large, their share of block space and how many top the old 80-byte limit.
BitcoinBitcoin Mining Pools: Hashrate Share by Pool
Which pools found Bitcoin's blocks over the last day, week and month, the hashrate share each implies and how concentrated mining is.
BitcoinBitcoin Ordinals, Runes and BRC-20 Activity
Ordinals inscriptions, Runes activity and BRC-20 operations on Bitcoin each day, with the fees they paid and the block space they used.
BitcoinBitcoin Hashrate and Mining Difficulty
Bitcoin's estimated network hashrate and mining difficulty, epoch by epoch, with every retarget, record and drop read from block headers.
BitcoinBitcoin Halving Countdown and Block Reward
Blocks left until the next Bitcoin halving, its date projected from recent block times and the block reward before and after it.
BitcoinBitcoin Transaction Fees and Mempool Tracker
The fee rate to confirm a Bitcoin transaction in the next block, an hour or a day, with mempool size and the fees recent blocks really paid.
BitcoinBuild Bitcoin Node Count: Bitcoin Core vs Knots Share on verified data.
Start free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.