Skip to content
Satoshi Gazette
Data DeskDated snapshot

Nodes & releases

Which software the reachable nodes in one research monitor say they run, and whether bitcoincore.org still maintains it.

Which software the reachable clearnet nodes KIT was connected to run

87.6%

of the 8,859 peers KIT’s monitor was connected to at advertised Bitcoin Core

Share of peers by the software they advertise: all connected peers, and those whose connection opened within 24 hours
SoftwareAll8,859Within 24 h1,998
Bitcoin Core87.6%7,76188.6%1,771
Bitcoin Knots10.9%96710.1%201
btcd0.3%240.4%8
Other software1.1%950.7%14
Unknown user agent0.1%120.2%4

Bitcoin Knots peers, by the service flags they announce

Knots peers · 967

Bitcoin Knots peers, and all connected peers, by the Knots service flags they announced
Flags announcedKnots967All peers8,859
BLAKE2b flag51%4965.6%499
Reduced-data flag only8%741.2%110
Neither flag41%39793.0%8,238
Flags not readable0%00.1%12

Knots’ source defines the BLAKE2b flag as its BLAKE2b hard-fork rules, reduced-data rules included, so a peer announcing both flags counts as BLAKE2b. Flags are self-announced: a node can set any bit, and the Gazette cannot see which chain a peer follows.

Most reachable nodes in the snapshot say they run Bitcoin Core. Bitcoin Knots is the next largest. Since 29.3.knots20260508 its releases include the BIP 110 soft fork, and since 29.4.1 a hard fork to BLAKE2b proof of work; Bitcoin Core includes neither.

Clearnet only: no Tor, I2P or non-listening nodes; a node can advertise any user agent, so the shares count what nodes say they run.

Calculation + Heuristic · self-reported user agents ·KIT’s network monitor ·snapshot , the newest day on file ·Node software on reachable nodes: KIT network monitor data ↗

Dates, sources & limits

KIT KASTEL DSN Bitcoin Network Monitor (CC BY 4.0 ↗). Per-peer records reduced to daily counts by implementation, IP version, Bitcoin Core release line and two announced service flags, and aggregated by Satoshi Gazette; the opened_24h population is additionally filtered to connections that began within 24 hours of the snapshot. No per-peer data is republished. Cite as: Neudecker, Till; Grundmann, Matthias; Hartenstein, Hannes. Bitcoin Peer-To-Peer Network Monitoring. Zenodo. doi:10.5281/zenodo.14627525.

Snapshot 20261115_125331 (KIT snapshot ↗).

Snapshots recorded

KIT snapshots recorded: peers in each population and the Core and Knots shares
Snapshot (UTC)ConnectedWithin 24 hCoreKnots
8,8591,99887.6%10.9%
9,1722,57287.8%10.8%
9,1772,64487.2%11.0%
9,1952,42086.9%11.1%
9,1452,42787.3%11.0%
9,3252,45487.2%10.9%
9,2862,36787.2%11.2%
9,2992,32887.0%11.2%
9,3972,38086.8%11.2%
9,1502,18086.5%11.6%
9,4182,58386.7%11.4%
9,2872,46786.4%11.6%
9,3692,57886.9%11.3%
9,2872,46686.8%11.7%
9,2622,37786.8%11.7%
Not recorded: no KIT snapshot
9,3682,90386.2%11.7%
9,4262,70886.4%11.6%
9,4712,36186.5%11.7%
Not recorded: no KIT snapshot
9,6582,47286.9%11.6%
9,6882,59987.0%11.3%
9,6732,69487.0%11.3%
9,6812,63786.8%11.3%
9,7172,80186.7%11.5%
9,8372,84087.1%11.1%
9,8152,76986.8%11.3%
9,7012,85387.2%11.3%
9,6912,70786.9%11.3%
9,6822,64387.0%11.4%
Recorded as read: 2,643 peers connected within the day, against a median of 1,873 over the seven days before; reachable peers rose from 8,704 on 15 October to 9,682.
Not recorded: 69 of the 2,700 peers seen opened in a day announced no readable software, over the rule's 2 percent, against 2 to 8 on every day before
8,7041,83886.8%11.8%
8,6931,89086.7%11.7%
8,8331,87386.8%11.8%
8,9061,78286.8%11.8%
8,8301,78686.8%11.8%
8,9461,87887.0%11.6%
9,0321,99987.2%11.4%
8,6951,74786.9%11.6%
8,7231,77687.2%11.2%
8,9291,93587.4%11.1%
8,9191,93387.5%11.0%
8,9661,91887.4%11.1%
8,9591,88087.2%11.2%
9,0101,97887.3%11.1%
9,0112,02587.1%11.3%
8,9462,04587.2%11.2%
9,0002,00486.9%11.5%
KIT's file held exactly 9,000 peers; this may be a cap.
8,9511,87987.0%11.3%

Shares are of all connected peers.

Bitcoin Core on a maintained release line among KIT’s connected peers

55.1%

of the 7,761 Bitcoin Core peers ran a release line bitcoincore.org still maintains

All connected Core peers · 7,761

Bitcoin Core peers by the status of their release line: all connected, and those whose connection opened within 24 hours
Release lineAll Core7,761Within 24 h1,771
Maintained55.1%4,27349.7%881
Ended43.2%3,35449.3%873
Not yet released1.7%1321.0%17
Not listed0.0%20.0%0

One group on 30 October 2026: 781 peers on 25.x with services number 1037 on five hosting networks, every connection opened within 24 hours. Without it that day’s shares read 41.5% of all Core peers and 32.4% within 24 hours.

43.2% ran a line past its end of life, which generally gets no security fixes; among connections opened within 24 hours, 49.3%.

The version is the one a node says it runs; the lifecycle covers Bitcoin Core only, so Knots is not classified.

Calculation + Heuristic · self-reported user agents ·KIT snapshot , the newest day on file ·lifecycle table as read on  ·Node software on reachable nodes: KIT network monitor data ↗

Core release lines among KIT’s connected peers

3release lines maintained

32.x, 31.x and 30.x, by the lifecycle table read ; 33.x not yet released

Release lines and Knots releases
Bitcoin Core release lines: release, end of life, status and peers in the snapshot
LineReleasedEnd of lifeStatusPeers
33.xTBAafter v36.0Not yet released0
32.x27 Oct 2026after v35.0Maintained1,375
31.x19 Apr 2026after v34.0Maintained2,301
30.x10 Oct 2025after v33.0Maintained597
29.x14 Apr 202527 Oct 2026Ended549
28.x2 Oct 202419 Apr 2026Ended1,002
27.x16 Apr 202410 Oct 2025Ended427
26.x6 Dec 202314 Apr 2025Ended151
25.x18 May 20232 Oct 2024Ended766
24.x24 Nov 20222 Apr 2024Ended78
23.x25 Apr 20221 Dec 2023Ended45
22.x13 Sep 20211 Apr 2023Ended129
0.21.x15 Jan 20211 Oct 2022Ended54
0.20.x3 Jun 20201 Feb 2022Ended67
0.19.x24 Nov 20191 Aug 2021Ended10
0.18.x2 May 20191 Feb 2021Ended29
0.17.x3 Oct 20181 Aug 2020Ended15
0.16.x26 Feb 20181 Feb 2020Ended7
0.15.x15 Sep 20171 Aug 2019Ended5
0.14.x8 Mar 20171 Feb 2019Ended5
0.13.x23 Aug 20161 Aug 2018Ended5
0.12.x23 Feb 201628 Feb 2018Ended6
0.11.x12 Jul 20151 Aug 2017Ended1
0.10.x16 Feb 201528 Feb 2017Ended0
0.9.x19 Mar 201428 Feb 2016Ended1
0.8.x19 Feb 201331 Dec 2015Ended2

Security advisories →

Bitcoin Knots releases

A release line past its end of life generally gets no security fixes.

A maintained line ends open and hatched: its end of life waits on a later release, never projected. Not drawn: 132 peers on development builds and 2 on unlisted versions.

Issuer · bitcoincore.org, read  ·Knots feed, read  ·peers: KIT snapshot  ·Node software releases: Life cycle table ↗

Releases of LND, Core Lightning, Eclair and BTCPay Server

11final releases

published on GitHub by the four projects in the 30 days to

The newest final release of each project, with the day GitHub published it
ProjectNewest final releasePublished
LND0.21.8-beta ↗
Core Lightning26.06.10 ↗
Eclair0.14.6 ↗
BTCPay Server2.4.7 ↗

A release candidate or other pre-release is not counted. A release is dated by the time GitHub says it was published, in UTC.

Issuer · GitHub’s release record of each project, read

Files