{"latest_posts":[{"id":534,"name":"Strakeljahn","username":"jorisstrakeljahn","avatar_template":"/user_avatar/bnoc.xyz/jorisstrakeljahn/{size}/275_2.png","created_at":"2026-07-08T19:15:09.278Z","cooked":"<p>While working on the <a href=\"https://jorisstrakeljahn.github.io/asmap-dashboard/#network\" rel=\"noopener nofollow ugc\">ASmap dashboard</a> I collected a list of crawlers and DNS seeders. Ended up checking quite a few of them, so in case it helps someone, here is the list:</p>\n<h2><a name=\"p-534-crawlers-node-datasets-1\" class=\"anchor\" href=\"#p-534-crawlers-node-datasets-1\" aria-label=\"Heading link\"></a>Crawlers / node datasets</h2>\n<p>(Every DNS seeder runs its own network crawler internally - some operators publish that crawler’s full view as a dump, which is why I put several of the seeders from the section below also in here)</p>\n<div class=\"md-table\">\n<table>\n<thead>\n<tr>\n<th>Source</th>\n<th>What you get</th>\n<th>Code</th>\n<th>Status</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><a href=\"https://mainnet.achownodes.xyz/\" rel=\"noopener nofollow ugc\">https://mainnet.achownodes.xyz/</a></td>\n<td>Full dnsseed.dump of achow101’s crawler: one line per known node with uptime stats (2h to 30d), block height, services, user agent. A <code>makeseeds.py</code> source with the widest service-bit coverage.</td>\n<td><a href=\"https://github.com/achow101/dnsseedrs\" rel=\"noopener nofollow ugc\">achow101/dnsseedrs</a></td>\n<td>live, fresh</td>\n</tr>\n<tr>\n<td><a href=\"https://bitcoin.fish.foo/\" rel=\"noopener nofollow ugc\">https://bitcoin.fish.foo/</a></td>\n<td>Same dump format from Will Clark’s <a href=\"https://github.com/willcl-ark/dnsseedrs\" rel=\"noopener nofollow ugc\">dnsseedrs instance</a>. Not in Core’s vSeeds, so an independent vantage point</td>\n<td></td>\n<td>live, fresh</td>\n</tr>\n<tr>\n<td><a href=\"https://bitnod.es/\" rel=\"noopener nofollow ugc\">https://bitnod.es/</a></td>\n<td>BitMEX Research node explorer: one cumulative “last seen” CSV per day with IP, country, ISP, services, user agent, height. Daily since 2026-06-26, weekly before. The site credits <a href=\"https://github.com/ayeowch/bitnodes\" rel=\"noopener nofollow ugc\">ayeowch/bitnodes</a> as its network crawler.</td>\n<td><a href=\"https://github.com/ayeowch/bitnodes\" rel=\"noopener nofollow ugc\">ayeowch/bitnodes</a></td>\n<td>live, fresh</td>\n</tr>\n<tr>\n<td><a href=\"https://btcnodes.io/\" rel=\"noopener nofollow ugc\">https://btcnodes.io/</a></td>\n<td>Revival of the original <a href=\"http://bitnodes.io\" rel=\"noopener nofollow ugc\">bitnodes.io</a> crawler. Full snapshots including Tor/I2P/CJDNS via <a href=\"https://btcnodes.io/api/v1/snapshots/latest/\" rel=\"noopener nofollow ugc\"><code>/api/v1/snapshots/latest/</code></a>; API history back to 2026-05-10.</td>\n<td><a href=\"https://github.com/brunneis/btcnodes\" rel=\"noopener nofollow ugc\">brunneis/btcnodes</a> (bitnodes fork)</td>\n<td>live, fresh</td>\n</tr>\n<tr>\n<td><a href=\"https://www.dsn.kastel.kit.edu/bitcoin/\" rel=\"noopener nofollow ugc\">dsn.kastel.kit.edu/bitcoin</a></td>\n<td>KIT DSN group research crawl: one dossier per day with per-node whois/ASN annotations under <a href=\"https://www.dsn.kastel.kit.edu/bitcoin/snapshots/\" rel=\"noopener nofollow ugc\"><code>/bitcoin/snapshots/</code></a>. The public index goes back to 2015-07</td>\n<td></td>\n<td>live, fresh</td>\n</tr>\n<tr>\n<td><a href=\"https://haf.ovh/seed.txt\" rel=\"noopener nofollow ugc\">https://haf.ovh/seed.txt</a></td>\n<td>Full <code>dnsseed.dump</code> from <code>seed.bitcoin.haf.ovh</code>, run by <a href=\"https://github.com/Retropex\" rel=\"noopener nofollow ugc\">Retropex</a>. Not in Core’s vSeeds, so another independent vantage point</td>\n<td></td>\n<td>live, fresh</td>\n</tr>\n<tr>\n<td><a href=\"https://21.ninja/seeds.txt.gz\" rel=\"noopener nofollow ugc\">https://21.ninja/seeds.txt.gz</a></td>\n<td>virtu’s crawler, also a <code>makeseeds.py</code> source. The dump is frozen since 2026-05-22; the <a href=\"https://21.ninja/\" rel=\"noopener nofollow ugc\">21.ninja</a> data site itself is still up.</td>\n<td><a href=\"https://github.com/virtu/p2p-crawler\" rel=\"noopener nofollow ugc\">virtu/p2p-crawler</a></td>\n<td>stale since 2026-05</td>\n</tr>\n<tr>\n<td><a href=\"https://bitcoin.sipa.be/seeds.txt.gz\" rel=\"noopener nofollow ugc\">https://bitcoin.sipa.be/seeds.txt.gz</a></td>\n<td>sipa’s <code>dnsseed.dump</code>, the published file is frozen since 2025-11-22, even though the DNS seed itself is fine</td>\n<td><a href=\"https://github.com/sipa/bitcoin-seeder\" rel=\"noopener nofollow ugc\">sipa/bitcoin-seeder</a></td>\n<td>stale since 2025-11</td>\n</tr>\n<tr>\n<td><a href=\"https://blockchair.com/bitcoin/nodes\" rel=\"noopener nofollow ugc\">blockchair.com/bitcoin/nodes</a></td>\n<td>Only a filtered “recently active” subset via <a href=\"https://api.blockchair.com/bitcoin/nodes\" rel=\"noopener nofollow ugc\">api.blockchair.com/bitcoin/nodes</a>, not a full crawl</td>\n<td></td>\n<td>live, fresh</td>\n</tr>\n</tbody>\n</table>\n</div><h2><a name=\"p-534-dns-seeders-2\" class=\"anchor\" href=\"#p-534-dns-seeders-2\" aria-label=\"Heading link\"></a>DNS seeders</h2>\n<ul>\n<li>The eight mainnet seeds from Bitcoin Core: <a href=\"https://github.com/bitcoin/bitcoin/blob/f0da26cfc8a42e917fb8144530c03fbb2f319d8c/src/kernel/chainparams.cpp#L168-L175\" rel=\"noopener nofollow ugc\">chainparams.cpp</a></li>\n<li><a href=\"https://wiz.biz/bitcoin/seed\" rel=\"noopener nofollow ugc\">seed.bitcoin.wiz.biz</a> returns IPv4 addresses only (no IPv6 records) and publishes no crawler dump, just an HTML status page (<a href=\"https://github.com/wiz/dnsseed-rust\" rel=\"noopener nofollow ugc\">wiz/dnsseed-rust</a>)</li>\n<li><a href=\"https://bitcoin.fish.foo/\" rel=\"noopener nofollow ugc\">seed.bitcoin.fish.foo</a> is a ninth, non-Core seeder run by willcl-ark that also answers (its dump is in the table above)</li>\n<li><a href=\"https://haf.ovh/leo.html\" rel=\"noopener nofollow ugc\">seed.bitcoin.haf.ovh</a> is a tenth, non-Core seeder run by <a href=\"https://github.com/Retropex\" rel=\"noopener nofollow ugc\">retropex</a> that also answers and publishes a full dump (in the table above)</li>\n<li>Two former Core seeds are still live and answering: <code>dnsseed.bitcoin.dashjr-list-of-p2p-nodes.us</code> (removed from vSeeds in <a href=\"https://github.com/bitcoin/bitcoin/pull/33723\" rel=\"noopener nofollow ugc\">Dec 2025</a>, still in <a href=\"https://github.com/bitcoinknots/bitcoin/blob/28.x-knots/src/kernel/chainparams.cpp\" rel=\"noopener nofollow ugc\">Knots’ chainparams.cpp</a>) and <code>seed.bitcoinstats.com</code> (removed in <a href=\"https://github.com/bitcoin/bitcoin/commit/c88a7dc53e3be7489605c3326cf768df5437393a\" rel=\"noopener nofollow ugc\">Aug 2024</a>)</li>\n</ul>\n<p><a href=\"https://octavio.xyz/projects/dns-monitoring/\" rel=\"noopener nofollow ugc\">octavio.xyz</a> monitors the quality of some of these seeds daily (advertised, reachable, stale, pristine, duplicate) via a small JSON API, own measurements since 2026-05-17. It also hosts virtu’s older series (Oct 2022 to Nov 2025, originally at <a href=\"https://21.ninja/dns-seeds/\" rel=\"noopener nofollow ugc\">21.ninja/dns-seeds</a>) as static CSVs under <code>demo-data/</code></p>\n<h2><a name=\"p-534-related-but-no-raw-node-data-3\" class=\"anchor\" href=\"#p-534-related-but-no-raw-node-data-3\" aria-label=\"Heading link\"></a>Related, but no raw node data</h2>\n<ul>\n<li>the <a href=\"https://willcl-ark.github.io/dnsseedrs/\" rel=\"noopener nofollow ugc\">dnsseedrs dashboard</a> is willcl-ark’s frontend for his fish.foo dump above</li>\n<li><a href=\"https://census.yonson.dev/\" rel=\"noopener nofollow ugc\">census.yonson.dev</a> publishes feature-acceptance aggregates</li>\n<li><a href=\"https://dns-seed.github.io/\" rel=\"noopener nofollow ugc\">Seed Coat</a> only record counts per seeder</li>\n<li><a href=\"https://bitdis.org/\" rel=\"noopener nofollow ugc\">bitdis.org</a> only Core/Knots totals</li>\n</ul>\n<p>If you know a live source I missed, I’d be happy to hear about it. Thanks!</p>","post_number":1,"post_type":1,"posts_count":1,"updated_at":"2026-07-08T19:15:09.278Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":4,"reads":3,"readers_count":2,"score":50.6,"yours":false,"topic_id":153,"topic_slug":"live-bitcoin-dns-seeders-and-crawler-datasets","topic_title":"Live Bitcoin DNS seeders and crawler datasets","topic_html_title":"Live Bitcoin DNS seeders and crawler datasets","category_id":5,"display_username":"Strakeljahn","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"While working on the [ASmap dashboard](https://jorisstrakeljahn.github.io/asmap-dashboard/#network) I collected a list of crawlers and DNS seeders. Ended up checking quite a few of them, so in case it helps someone, here is the list:\n\n## Crawlers / node datasets\n(Every DNS seeder runs its own network crawler internally - some operators publish that crawler's full view as a dump, which is why I put several of the seeders from the section below also in here)\n\n| Source | What you get | Code | Status |\n|----|----|----|----|\n| https://mainnet.achownodes.xyz/ | Full dnsseed.dump of achow101's crawler: one line per known node with uptime stats (2h to 30d), block height, services, user agent. A `makeseeds.py` source with the widest service-bit coverage. | [achow101/dnsseedrs](https://github.com/achow101/dnsseedrs) | live, fresh |\n| https://bitcoin.fish.foo/ | Same dump format from Will Clark's [dnsseedrs instance](https://github.com/willcl-ark/dnsseedrs). Not in Core's vSeeds, so an independent vantage point | | live, fresh |\n| https://bitnod.es/ | BitMEX Research node explorer: one cumulative \"last seen\" CSV per day with IP, country, ISP, services, user agent, height. Daily since 2026-06-26, weekly before. The site credits [ayeowch/bitnodes](https://github.com/ayeowch/bitnodes) as its network crawler. | [ayeowch/bitnodes](https://github.com/ayeowch/bitnodes) | live, fresh |\n| https://btcnodes.io/ | Revival of the original bitnodes.io crawler. Full snapshots including Tor/I2P/CJDNS via [`/api/v1/snapshots/latest/`](https://btcnodes.io/api/v1/snapshots/latest/); API history back to 2026-05-10. | [brunneis/btcnodes](https://github.com/brunneis/btcnodes) (bitnodes fork) | live, fresh |\n| [dsn.kastel.kit.edu/bitcoin](https://www.dsn.kastel.kit.edu/bitcoin/) | KIT DSN group research crawl: one dossier per day with per-node whois/ASN annotations under [`/bitcoin/snapshots/`](https://www.dsn.kastel.kit.edu/bitcoin/snapshots/). The public index goes back to 2015-07 | | live, fresh |\n| https://haf.ovh/seed.txt | Full `dnsseed.dump` from `seed.bitcoin.haf.ovh`, run by [Retropex](https://github.com/Retropex). Not in Core's vSeeds, so another independent vantage point | | live, fresh |\n| https://21.ninja/seeds.txt.gz | virtu's crawler, also a `makeseeds.py` source. The dump is frozen since 2026-05-22; the [21.ninja](https://21.ninja/) data site itself is still up. | [virtu/p2p-crawler](https://github.com/virtu/p2p-crawler) | stale since 2026-05 |\n| https://bitcoin.sipa.be/seeds.txt.gz | sipa's `dnsseed.dump`, the published file is frozen since 2025-11-22, even though the DNS seed itself is fine | [sipa/bitcoin-seeder](https://github.com/sipa/bitcoin-seeder) | stale since 2025-11 |\n| [blockchair.com/bitcoin/nodes](https://blockchair.com/bitcoin/nodes) | Only a filtered \"recently active\" subset via [api.blockchair.com/bitcoin/nodes](https://api.blockchair.com/bitcoin/nodes), not a full crawl | | live, fresh |\n\n## DNS seeders\n\n* The eight mainnet seeds from Bitcoin Core: [chainparams.cpp](https://github.com/bitcoin/bitcoin/blob/f0da26cfc8a42e917fb8144530c03fbb2f319d8c/src/kernel/chainparams.cpp#L168-L175)\n* [seed.bitcoin.wiz.biz](https://wiz.biz/bitcoin/seed) returns IPv4 addresses only (no IPv6 records) and publishes no crawler dump, just an HTML status page ([wiz/dnsseed-rust](https://github.com/wiz/dnsseed-rust))\n* [seed.bitcoin.fish.foo](https://bitcoin.fish.foo/) is a ninth, non-Core seeder run by willcl-ark that also answers (its dump is in the table above)\n* [seed.bitcoin.haf.ovh](https://haf.ovh/leo.html) is a tenth, non-Core seeder run by [retropex](https://github.com/Retropex) that also answers and publishes a full dump (in the table above)\n* Two former Core seeds are still live and answering: `dnsseed.bitcoin.dashjr-list-of-p2p-nodes.us` (removed from vSeeds in [Dec 2025](https://github.com/bitcoin/bitcoin/pull/33723), still in [Knots' chainparams.cpp](https://github.com/bitcoinknots/bitcoin/blob/28.x-knots/src/kernel/chainparams.cpp)) and `seed.bitcoinstats.com` (removed in [Aug 2024](https://github.com/bitcoin/bitcoin/commit/c88a7dc53e3be7489605c3326cf768df5437393a))\n\n[octavio.xyz](https://octavio.xyz/projects/dns-monitoring/) monitors the quality of some of these seeds daily (advertised, reachable, stale, pristine, duplicate) via a small JSON API, own measurements since 2026-05-17. It also hosts virtu's older series (Oct 2022 to Nov 2025, originally at [21.ninja/dns-seeds](https://21.ninja/dns-seeds/)) as static CSVs under `demo-data/`\n\n## Related, but no raw node data\n\n* the [dnsseedrs dashboard](https://willcl-ark.github.io/dnsseedrs/) is willcl-ark's frontend for his fish.foo dump above\n* [census.yonson.dev](https://census.yonson.dev/) publishes feature-acceptance aggregates\n* [Seed Coat](https://dns-seed.github.io/) only record counts per seeder\n* [bitdis.org](https://bitdis.org/) only Core/Knots totals\n\nIf you know a live source I missed, I'd be happy to hear about it. Thanks!","actions_summary":[{"id":2,"count":2}],"moderator":false,"admin":false,"staff":false,"user_id":86,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"While working on the <a href=\"https://jorisstrakeljahn.github.io/asmap-dashboard/#network\" rel=\"noopener nofollow ugc\">ASmap dashboard</a> I collected a list of crawlers and DNS seeders. Ended up checking quite a few of them, so in case it helps someone, here is the list: \n<a name=\"p-534-crawlers-node-datasets-1\" class=\"anchor\" href=\"#p-534-crawlers-node-datasets-1\" aria-label=\"Heading link\"></a>Crawlers / node datasets\n(Every DNS seeder runs its own network crawler internally - some operators publish that crawler’s full &hellip;","truncated":true,"post_url":"/t/live-bitcoin-dns-seeders-and-crawler-datasets/153/1","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null,"can_vote":false},{"id":533,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-07-08T11:10:12.273Z","cooked":"<p>I had a look at my peer-observer node IPs in this data:</p>\n<ul>\n<li>Most of them are correctly identified as <code>Linux</code></li>\n<li>Two of them are marked as <code>Unknown</code>. I think these have a stricter firewall on the hoster side</li>\n<li>One of them is marked as <code>Other/Device</code>, but it also sits behind a stricter firewall</li>\n</ul>\n<p>If someone is running a node on Windows, it would be interesting to look it up in the CSV and report if it’s correctly identified.</p>","post_number":3,"post_type":1,"posts_count":3,"updated_at":"2026-07-08T11:10:12.273Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":8,"readers_count":7,"score":16.6,"yours":false,"topic_id":152,"topic_slug":"os-fingerprints-of-16-6k-bitcoin-nodes","topic_title":"OS fingerprints of ~16.6k Bitcoin nodes","topic_html_title":"OS fingerprints of ~16.6k Bitcoin nodes","category_id":5,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"I had a look at my peer-observer node IPs in this data:\n\n- Most of them are correctly identified as `Linux`\n- Two of them are marked as `Unknown`. I think these have a stricter firewall on the hoster side\n- One of them is marked as `Other/Device`, but it also sits behind a stricter firewall\n\n\nIf someone is running a node on Windows, it would be interesting to look it up in the CSV and report if it's correctly identified.","actions_summary":[{"id":2,"count":1}],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"I had a look at my peer-observer node IPs in this data: \n\nMost of them are correctly identified as Linux\nTwo of them are marked as Unknown. I think these have a stricter firewall on the hoster side\nOne of them is marked as Other/Device, but it also sits behind a stricter firewall\n\nIf someone is runn&hellip;","truncated":true,"post_url":"/t/os-fingerprints-of-16-6k-bitcoin-nodes/152/3","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":532,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-07-08T11:00:23.520Z","cooked":"<p>Thanks for posting!</p>\n<p>In <a href=\"https://github.com/peer-observer/peer-observer/issues/141#issuecomment-4908665074\" class=\"inline-onebox\">Implement more extractors · Issue #141 · peer-observer/peer-observer · GitHub</a> , I had a brief look at the Windows IPs. I thought many of these were probably hosted at Azure, but it turns out, many of them are actually on an ISP, not hosted. Here’s a quick and dirty <a href=\"https://0xb10c.github.io/asmap-web/?ip=1.10.248.178,100.35.228.43,101.188.99.97,101.98.25.223,102.140.79.221,103.228.170.74,103.241.122.39,104.171.249.65,104.184.65.200,104.228.209.40,104.250.170.171,104.55.74.35,104.62.145.108,107.193.245.33,107.217.160.112,107.222.16.143,108.16.14.171,108.167.57.40,108.204.165.42,108.212.90.47,108.217.67.241,108.232.35.212,108.248.107.246,108.249.26.161,108.255.193.173,108.39.125.98,108.48.35.82,108.82.180.34,108.85.158.196,109.160.25.136,109.164.111.129,109.247.135.249,113.119.24.91,113.150.87.158,114.201.207.72,116.64.11.104,118.194.235.42,120.156.213.137,120.88.124.175,121.91.78.2,121.98.205.100,122.199.30.140,129.228.59.214,131.150.177.18,134.22.104.129,135.125.163.82,135.129.154.242,135.135.168.83,135.148.150.198,135.181.111.231,136.243.174.119,136.35.54.224,136.51.20.119,136.59.13.227,136.62.117.115,138.201.132.222,139.68.231.75,140.228.150.188,141.126.228.189,141.149.57.92,141.255.167.250,141.95.85.55,142.56.43.134,144.137.29.181,146.59.15.26,146.71.69.103,146.90.189.86,147.81.53.12,148.251.140.28,151.177.152.134,151.67.100.128,152.243.146.128,152.44.185.166,155.4.82.77,156.146.140.123,157.180.11.159,158.220.83.76,162.197.163.32,162.200.4.171,162.202.246.164,162.204.36.245,162.247.214.205,162.249.228.218,163.123.214.76,164.215.119.118,165.188.179.98,167.248.15.113,167.88.165.17,168.228.80.14,170.203.128.89,171.96.86.230,172.94.109.225,173.208.236.58,173.208.243.38,173.24.200.71,173.241.227.243,173.63.86.43,173.86.227.73,174.100.131.254,174.160.140.219,174.173.199.30,174.20.136.103,174.21.90.70,174.26.6.50,174.76.54.122,176.106.242.172,176.38.46.162,176.76.67.83,176.9.41.164,177.32.50.167,178.140.36.127,178.200.144.108,178.252.118.74,178.39.104.171,179.152.86.9,179.43.161.186,18.162.208.118,180.129.37.31,182.209.238.48,182.52.108.223,184.152.217.8,184.171.208.109,184.58.150.3,184.58.187.79,184.95.13.14,184.96.129.12,185.12.15.13,185.141.60.36,185.152.138.74,185.154.2.3,185.157.161.87,185.24.53.34,185.97.200.21,188.137.233.39,188.237.167.51,188.243.153.116,189.55.5.201,192.164.70.224,192.182.23.82,192.253.229.123,193.104.222.143,193.110.165.111,193.94.43.171,193.95.249.3,194.145.199.26,194.8.238.108,195.140.226.154,195.240.111.6,198.28.177.96,198.48.148.76,198.53.191.83,199.167.149.246,199.230.127.169,2.248.28.126,2.58.66.98,2001:41d0:8:6aa0::1,2001:470:59b4::ff,2001:861:c66:2ca0:9085:2491:7d4f:9e93,2001:861:c66:2ca0:ccbd:c1b8:2e10:7ef,2001:9b1:10d:2e::4:912f,2001:b011:2009:90dd:19ff:bcc2:dc6e:caa3,2001:b011:2009:90dd:7928:d2c3:34af:b394,202.146.222.14,202.150.90.102,203.118.186.226,203.88.121.47,204.111.163.114,204.12.245.4,207.135.130.143,207.216.253.116,209.127.20.106,211.208.192.98,212.16.76.138,212.47.78.147,213.109.236.129,213.136.83.223,213.141.198.207,213.142.182.169,213.221.206.78,213.226.192.122,213.47.64.105,216.213.164.96,216.229.47.84,216.245.184.202,217.155.3.184,217.170.124.170,218.200.42.52,218.31.113.245,220.86.56.164,222.153.177.16,222.154.33.254,23.245.136.142,24.109.211.59,24.113.59.144,24.130.18.203,24.147.222.239,24.16.54.70,24.176.32.127,24.178.124.26,24.187.40.71,24.19.135.184,24.198.156.216,24.202.147.219,24.226.203.186,24.88.204.156,2400:2412:1c2:ed00:8c8:795b:afbb:ad7d,2405:9800:bca0:75d0:b947:eadf:25c5:5fe4,2407:4b00:4c0d:8fd:9e81:c77b:b20a:77f8,2407:4b00:4c0d:8fd:ff:ff:ff:3d,2408:8234:616:3334:3130:8c10:89b3:e1fb,2600:4041:2054:da00::17fe,2600:8801:2f80:ac::173e,2603:900b:e400:1df:ad07:ea3e:9c6e:c60a,27.252.98.12,27.32.87.112,2804:14c:34:219b::4f5,2804:6950:e:5630:2066:b7f2:c9b3:a4d4,2804:c9c:1:354c:f174:6e99:a597:1ffb,2806:2f0:5240:f865:cfb8:b896:a098:e5dc,2a00:23c8:f80e:6d01:8c5e:b515:1925:bd41,2a00:f2a:e08e:41a0:14a6:43ea:798e:a76a,2a01:e0a:154:3380:d800:a6a8:ecb5:7304,2a01:e0a:e86:2960:b98:53b0:21f4:6228,2a01:e0a:f0:13b0:7948:43c7:4333:39d2,2a02:220b:2000:f800:f52d:9a26:d179:b5cb,2a02:220b:2000:f800:fb46:25d3:84c7:20c0,2a06:63c5:8303:7b00:50f9:52e:4265:b3ee,3.16.175.255,3.211.180.220,31.190.223.238,31.21.210.206,31.46.42.22,34.208.54.193,35.129.55.111,35.133.160.185,35.140.123.29,35.82.222.134,35.83.165.92,35.83.182.185,37.114.42.51,37.128.245.86,37.25.47.141,37.34.175.124,37.34.245.49,37.59.47.160,38.179.98.161,38.34.178.137,44.219.125.103,45.23.63.218,45.249.246.224,45.47.36.160,45.93.114.178,46.175.178.3,46.19.141.178,46.227.66.138,46.24.64.60,46.249.191.157,47.141.45.50,47.144.115.243,47.149.41.219,47.160.10.230,47.183.243.207,47.187.92.112,47.45.255.48,49.158.136.43,5.161.219.121,5.183.131.110,5.196.119.233,5.56.9.159,5.8.205.138,5.9.79.112,50.113.73.100,50.125.82.209,50.175.156.202,50.213.123.122,50.5.249.23,51.38.86.114,52.90.226.234,58.168.225.214,58.226.12.148,59.14.15.215,61.245.159.236,61.77.246.20,62.195.252.247,62.210.217.126,62.80.166.146,62.93.65.111,64.118.245.38,64.223.96.231,64.253.104.118,65.30.102.222,66.129.161.70,66.160.128.215,66.52.20.190,67.180.143.80,67.193.65.177,67.225.3.243,67.240.128.50,67.241.49.48,67.85.196.122,68.101.119.121,68.103.253.106,68.129.90.52,68.146.142.211,68.185.183.72,68.203.5.191,68.21.162.120,68.98.61.233,69.206.99.57,69.226.232.231,69.36.52.44,70.113.210.71,70.16.128.65,70.170.9.35,70.70.14.92,70.78.184.60,70.82.138.163,71.10.126.229,71.126.164.150,71.183.185.118,71.204.146.116,71.227.207.165,71.237.44.127,71.247.165.11,71.31.177.1,71.79.109.128,71.85.54.8,72.179.148.45,72.187.175.134,72.206.123.63,72.224.188.0,72.249.87.49,72.255.188.46,72.66.71.155,72.81.139.70,73.154.107.37,73.160.188.10,73.181.132.4,73.186.15.145,73.190.47.58,73.208.251.19,73.213.196.110,73.231.150.185,74.131.226.86,74.214.214.84,74.91.112.145,74.96.150.228,75.132.65.164,75.143.205.69,75.67.138.54,75.84.91.224,76.18.121.164,76.235.98.101,76.28.254.53,76.64.65.183,76.73.142.42,76.86.62.33,76.9.167.215,78.108.96.228,78.153.4.77,78.46.66.29,79.116.71.137,80.102.12.58,80.244.26.192,81.95.140.101,82.116.38.140,82.2.140.5,82.37.80.176,82.66.159.237,82.66.197.211,82.67.99.238,82.68.85.205,82.76.172.101,83.167.79.9,83.217.162.87,83.252.62.212,84.202.197.114,84.38.22.135,84.47.73.41,85.118.207.197,85.191.19.95,85.195.54.157,85.220.32.157,85.255.89.244,85.50.45.74,86.110.220.58,86.128.75.32,86.150.5.215,86.201.225.172,86.238.183.93,86.253.244.62,86.28.104.37,86.52.27.8,86.60.153.66,87.124.183.82,87.196.5.240,87.79.94.221,88.13.249.4,88.134.40.111,88.147.244.250,88.98.214.124,89.139.48.172,89.171.13.82,9.138.0.151,90.184.11.207,90.240.179.255,90.248.155.122,91.127.232.108,91.153.92.32,91.155.85.151,91.157.142.175,91.190.197.20,91.201.255.25,91.204.149.107,91.215.91.254,92.154.24.7,92.189.23.141,92.205.27.36,92.27.11.82,92.27.11.86,92.27.11.87,93.123.135.12,93.125.121.226,93.240.3.172,94.19.128.204,94.198.51.247,94.198.55.181,95.138.220.244,95.141.35.117,95.216.27.32,95.31.188.110,95.79.52.193,95.84.162.152,96.244.212.63,96.245.12.214,96.52.245.135,96.59.17.81,96.81.219.106,97.85.14.255,97.96.51.52,98.121.99.54,98.165.59.5,98.191.193.194,98.193.88.70,98.210.17.106,98.225.38.106,98.230.8.85,99.109.104.206,99.157.243.27,99.17.251.211,99.172.29.2,99.255.159.147&amp;asmap=2026/1780588800_asmap_unfilled.dat\">overview</a>.</p>\n<p>Feel free to continue posting the monthly updates here too.</p>","post_number":2,"post_type":1,"posts_count":3,"updated_at":"2026-07-08T11:00:23.520Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":8,"readers_count":7,"score":16.6,"yours":false,"topic_id":152,"topic_slug":"os-fingerprints-of-16-6k-bitcoin-nodes","topic_title":"OS fingerprints of ~16.6k Bitcoin nodes","topic_html_title":"OS fingerprints of ~16.6k Bitcoin nodes","category_id":5,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"Thanks for posting!\n\nIn https://github.com/peer-observer/peer-observer/issues/141#issuecomment-4908665074 , I had a brief look at the Windows IPs. I thought many of these were probably hosted at Azure, but it turns out, many of them are actually on an ISP, not hosted. Here’s a quick and dirty [overview](https://0xb10c.github.io/asmap-web/?ip=1.10.248.178,100.35.228.43,101.188.99.97,101.98.25.223,102.140.79.221,103.228.170.74,103.241.122.39,104.171.249.65,104.184.65.200,104.228.209.40,104.250.170.171,104.55.74.35,104.62.145.108,107.193.245.33,107.217.160.112,107.222.16.143,108.16.14.171,108.167.57.40,108.204.165.42,108.212.90.47,108.217.67.241,108.232.35.212,108.248.107.246,108.249.26.161,108.255.193.173,108.39.125.98,108.48.35.82,108.82.180.34,108.85.158.196,109.160.25.136,109.164.111.129,109.247.135.249,113.119.24.91,113.150.87.158,114.201.207.72,116.64.11.104,118.194.235.42,120.156.213.137,120.88.124.175,121.91.78.2,121.98.205.100,122.199.30.140,129.228.59.214,131.150.177.18,134.22.104.129,135.125.163.82,135.129.154.242,135.135.168.83,135.148.150.198,135.181.111.231,136.243.174.119,136.35.54.224,136.51.20.119,136.59.13.227,136.62.117.115,138.201.132.222,139.68.231.75,140.228.150.188,141.126.228.189,141.149.57.92,141.255.167.250,141.95.85.55,142.56.43.134,144.137.29.181,146.59.15.26,146.71.69.103,146.90.189.86,147.81.53.12,148.251.140.28,151.177.152.134,151.67.100.128,152.243.146.128,152.44.185.166,155.4.82.77,156.146.140.123,157.180.11.159,158.220.83.76,162.197.163.32,162.200.4.171,162.202.246.164,162.204.36.245,162.247.214.205,162.249.228.218,163.123.214.76,164.215.119.118,165.188.179.98,167.248.15.113,167.88.165.17,168.228.80.14,170.203.128.89,171.96.86.230,172.94.109.225,173.208.236.58,173.208.243.38,173.24.200.71,173.241.227.243,173.63.86.43,173.86.227.73,174.100.131.254,174.160.140.219,174.173.199.30,174.20.136.103,174.21.90.70,174.26.6.50,174.76.54.122,176.106.242.172,176.38.46.162,176.76.67.83,176.9.41.164,177.32.50.167,178.140.36.127,178.200.144.108,178.252.118.74,178.39.104.171,179.152.86.9,179.43.161.186,18.162.208.118,180.129.37.31,182.209.238.48,182.52.108.223,184.152.217.8,184.171.208.109,184.58.150.3,184.58.187.79,184.95.13.14,184.96.129.12,185.12.15.13,185.141.60.36,185.152.138.74,185.154.2.3,185.157.161.87,185.24.53.34,185.97.200.21,188.137.233.39,188.237.167.51,188.243.153.116,189.55.5.201,192.164.70.224,192.182.23.82,192.253.229.123,193.104.222.143,193.110.165.111,193.94.43.171,193.95.249.3,194.145.199.26,194.8.238.108,195.140.226.154,195.240.111.6,198.28.177.96,198.48.148.76,198.53.191.83,199.167.149.246,199.230.127.169,2.248.28.126,2.58.66.98,2001:41d0:8:6aa0::1,2001:470:59b4::ff,2001:861:c66:2ca0:9085:2491:7d4f:9e93,2001:861:c66:2ca0:ccbd:c1b8:2e10:7ef,2001:9b1:10d:2e::4:912f,2001:b011:2009:90dd:19ff:bcc2:dc6e:caa3,2001:b011:2009:90dd:7928:d2c3:34af:b394,202.146.222.14,202.150.90.102,203.118.186.226,203.88.121.47,204.111.163.114,204.12.245.4,207.135.130.143,207.216.253.116,209.127.20.106,211.208.192.98,212.16.76.138,212.47.78.147,213.109.236.129,213.136.83.223,213.141.198.207,213.142.182.169,213.221.206.78,213.226.192.122,213.47.64.105,216.213.164.96,216.229.47.84,216.245.184.202,217.155.3.184,217.170.124.170,218.200.42.52,218.31.113.245,220.86.56.164,222.153.177.16,222.154.33.254,23.245.136.142,24.109.211.59,24.113.59.144,24.130.18.203,24.147.222.239,24.16.54.70,24.176.32.127,24.178.124.26,24.187.40.71,24.19.135.184,24.198.156.216,24.202.147.219,24.226.203.186,24.88.204.156,2400:2412:1c2:ed00:8c8:795b:afbb:ad7d,2405:9800:bca0:75d0:b947:eadf:25c5:5fe4,2407:4b00:4c0d:8fd:9e81:c77b:b20a:77f8,2407:4b00:4c0d:8fd:ff:ff:ff:3d,2408:8234:616:3334:3130:8c10:89b3:e1fb,2600:4041:2054:da00::17fe,2600:8801:2f80:ac::173e,2603:900b:e400:1df:ad07:ea3e:9c6e:c60a,27.252.98.12,27.32.87.112,2804:14c:34:219b::4f5,2804:6950:e:5630:2066:b7f2:c9b3:a4d4,2804:c9c:1:354c:f174:6e99:a597:1ffb,2806:2f0:5240:f865:cfb8:b896:a098:e5dc,2a00:23c8:f80e:6d01:8c5e:b515:1925:bd41,2a00:f2a:e08e:41a0:14a6:43ea:798e:a76a,2a01:e0a:154:3380:d800:a6a8:ecb5:7304,2a01:e0a:e86:2960:b98:53b0:21f4:6228,2a01:e0a:f0:13b0:7948:43c7:4333:39d2,2a02:220b:2000:f800:f52d:9a26:d179:b5cb,2a02:220b:2000:f800:fb46:25d3:84c7:20c0,2a06:63c5:8303:7b00:50f9:52e:4265:b3ee,3.16.175.255,3.211.180.220,31.190.223.238,31.21.210.206,31.46.42.22,34.208.54.193,35.129.55.111,35.133.160.185,35.140.123.29,35.82.222.134,35.83.165.92,35.83.182.185,37.114.42.51,37.128.245.86,37.25.47.141,37.34.175.124,37.34.245.49,37.59.47.160,38.179.98.161,38.34.178.137,44.219.125.103,45.23.63.218,45.249.246.224,45.47.36.160,45.93.114.178,46.175.178.3,46.19.141.178,46.227.66.138,46.24.64.60,46.249.191.157,47.141.45.50,47.144.115.243,47.149.41.219,47.160.10.230,47.183.243.207,47.187.92.112,47.45.255.48,49.158.136.43,5.161.219.121,5.183.131.110,5.196.119.233,5.56.9.159,5.8.205.138,5.9.79.112,50.113.73.100,50.125.82.209,50.175.156.202,50.213.123.122,50.5.249.23,51.38.86.114,52.90.226.234,58.168.225.214,58.226.12.148,59.14.15.215,61.245.159.236,61.77.246.20,62.195.252.247,62.210.217.126,62.80.166.146,62.93.65.111,64.118.245.38,64.223.96.231,64.253.104.118,65.30.102.222,66.129.161.70,66.160.128.215,66.52.20.190,67.180.143.80,67.193.65.177,67.225.3.243,67.240.128.50,67.241.49.48,67.85.196.122,68.101.119.121,68.103.253.106,68.129.90.52,68.146.142.211,68.185.183.72,68.203.5.191,68.21.162.120,68.98.61.233,69.206.99.57,69.226.232.231,69.36.52.44,70.113.210.71,70.16.128.65,70.170.9.35,70.70.14.92,70.78.184.60,70.82.138.163,71.10.126.229,71.126.164.150,71.183.185.118,71.204.146.116,71.227.207.165,71.237.44.127,71.247.165.11,71.31.177.1,71.79.109.128,71.85.54.8,72.179.148.45,72.187.175.134,72.206.123.63,72.224.188.0,72.249.87.49,72.255.188.46,72.66.71.155,72.81.139.70,73.154.107.37,73.160.188.10,73.181.132.4,73.186.15.145,73.190.47.58,73.208.251.19,73.213.196.110,73.231.150.185,74.131.226.86,74.214.214.84,74.91.112.145,74.96.150.228,75.132.65.164,75.143.205.69,75.67.138.54,75.84.91.224,76.18.121.164,76.235.98.101,76.28.254.53,76.64.65.183,76.73.142.42,76.86.62.33,76.9.167.215,78.108.96.228,78.153.4.77,78.46.66.29,79.116.71.137,80.102.12.58,80.244.26.192,81.95.140.101,82.116.38.140,82.2.140.5,82.37.80.176,82.66.159.237,82.66.197.211,82.67.99.238,82.68.85.205,82.76.172.101,83.167.79.9,83.217.162.87,83.252.62.212,84.202.197.114,84.38.22.135,84.47.73.41,85.118.207.197,85.191.19.95,85.195.54.157,85.220.32.157,85.255.89.244,85.50.45.74,86.110.220.58,86.128.75.32,86.150.5.215,86.201.225.172,86.238.183.93,86.253.244.62,86.28.104.37,86.52.27.8,86.60.153.66,87.124.183.82,87.196.5.240,87.79.94.221,88.13.249.4,88.134.40.111,88.147.244.250,88.98.214.124,89.139.48.172,89.171.13.82,9.138.0.151,90.184.11.207,90.240.179.255,90.248.155.122,91.127.232.108,91.153.92.32,91.155.85.151,91.157.142.175,91.190.197.20,91.201.255.25,91.204.149.107,91.215.91.254,92.154.24.7,92.189.23.141,92.205.27.36,92.27.11.82,92.27.11.86,92.27.11.87,93.123.135.12,93.125.121.226,93.240.3.172,94.19.128.204,94.198.51.247,94.198.55.181,95.138.220.244,95.141.35.117,95.216.27.32,95.31.188.110,95.79.52.193,95.84.162.152,96.244.212.63,96.245.12.214,96.52.245.135,96.59.17.81,96.81.219.106,97.85.14.255,97.96.51.52,98.121.99.54,98.165.59.5,98.191.193.194,98.193.88.70,98.210.17.106,98.225.38.106,98.230.8.85,99.109.104.206,99.157.243.27,99.17.251.211,99.172.29.2,99.255.159.147&asmap=2026/1780588800_asmap_unfilled.dat).\n\nFeel free to continue posting the monthly updates here too.","actions_summary":[{"id":2,"count":1}],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Thanks for posting! \nIn <a href=\"https://github.com/peer-observer/peer-observer/issues/141#issuecomment-4908665074\" class=\"inline-onebox\">Implement more extractors · Issue #141 · peer-observer/peer-observer · GitHub</a> , I had a brief look at the Windows IPs. I thought many of these were probably hosted at Azure, but it turns out, many of them are actually on an ISP, not hosted. Here’s a quick and dirty <a href=\"https://0xb10c.github.io/asmap-web/?ip=1.10.248.178,100.35.228.43,101.188.99.97,101.98.25.223,102.140.79.221,103.228.170.74,103.241.122.39,104.171.249.65,104.184.65.200,104.228.209.40,104.250.170.171,104.55.74.35,104.62.145.108,107.193.245.33,107.217.160.112,107.222.16.143,108.16.14.171,108.167.57.40,108.204.165.42,108.212.90.47,108.217.67.241,108.232.35.212,108.248.107.246,108.249.26.161,108.255.193.173,108.39.125.98,108.48.35.82,108.82.180.34,108.85.158.196,109.160.25.136,109.164.111.129,109.247.135.249,113.119.24.91,113.150.87.158,114.201.207.72,116.64.11.104,118.194.235.42,120.156.213.137,120.88.124.175,121.91.78.2,121.98.205.100,122.199.30.140,129.228.59.214,131.150.177.18,134.22.104.129,135.125.163.82,135.129.154.242,135.135.168.83,135.148.150.198,135.181.111.231,136.243.174.119,136.35.54.224,136.51.20.119,136.59.13.227,136.62.117.115,138.201.132.222,139.68.231.75,140.228.150.188,141.126.228.189,141.149.57.92,141.255.167.250,141.95.85.55,142.56.43.134,144.137.29.181,146.59.15.26,146.71.69.103,146.90.189.86,147.81.53.12,148.251.140.28,151.177.152.134,151.67.100.128,152.243.146.128,152.44.185.166,155.4.82.77,156.146.140.123,157.180.11.159,158.220.83.76,162.197.163.32,162.200.4.171,162.202.246.164,162.204.36.245,162.247.214.205,162.249.228.218,163.123.214.76,164.215.119.118,165.188.179.98,167.248.15.113,167.88.165.17,168.228.80.14,170.203.128.89,171.96.86.230,172.94.109.225,173.208.236.58,173.208.243.38,173.24.200.71,173.241.227.243,173.63.86.43,173.86.227.73,174.100.131.254,174.160.140.219,174.173.199.30,174.20.136.103,174.21.90.70,174.26.6.50,174.76.54.122,176.106.242.172,176.38.46.162,176.76.67.83,176.9.41.164,177.32.50.167,178.140.36.127,178.200.144.108,178.252.118.74,178.39.104.171,179.152.86.9,179.43.161.186,18.162.208.118,180.129.37.31,182.209.238.48,182.52.108.223,184.152.217.8,184.171.208.109,184.58.150.3,184.58.187.79,184.95.13.14,184.96.129.12,185.12.15.13,185.141.60.36,185.152.138.74,185.154.2.3,185.157.161.87,185.24.53.34,185.97.200.21,188.137.233.39,188.237.167.51,188.243.153.116,189.55.5.201,192.164.70.224,192.182.23.82,192.253.229.123,193.104.222.143,193.110.165.111,193.94.43.171,193.95.249.3,194.145.199.26,194.8.238.108,195.140.226.154,195.240.111.6,198.28.177.96,198.48.148.76,198.53.191.83,199.167.149.246,199.230.127.169,2.248.28.126,2.58.66.98,2001:41d0:8:6aa0::1,2001:470:59b4::ff,2001:861:c66:2ca0:9085:2491:7d4f:9e93,2001:861:c66:2ca0:ccbd:c1b8:2e10:7ef,2001:9b1:10d:2e::4:912f,2001:b011:2009:90dd:19ff:bcc2:dc6e:caa3,2001:b011:2009:90dd:7928:d2c3:34af:b394,202.146.222.14,202.150.90.102,203.118.186.226,203.88.121.47,204.111.163.114,204.12.245.4,207.135.130.143,207.216.253.116,209.127.20.106,211.208.192.98,212.16.76.138,212.47.78.147,213.109.236.129,213.136.83.223,213.141.198.207,213.142.182.169,213.221.206.78,213.226.192.122,213.47.64.105,216.213.164.96,216.229.47.84,216.245.184.202,217.155.3.184,217.170.124.170,218.200.42.52,218.31.113.245,220.86.56.164,222.153.177.16,222.154.33.254,23.245.136.142,24.109.211.59,24.113.59.144,24.130.18.203,24.147.222.239,24.16.54.70,24.176.32.127,24.178.124.26,24.187.40.71,24.19.135.184,24.198.156.216,24.202.147.219,24.226.203.186,24.88.204.156,2400:2412:1c2:ed00:8c8:795b:afbb:ad7d,2405:9800:bca0:75d0:b947:eadf:25c5:5fe4,2407:4b00:4c0d:8fd:9e81:c77b:b20a:77f8,2407:4b00:4c0d:8fd:ff:ff:ff:3d,2408:8234:616:3334:3130:8c10:89b3:e1fb,2600:4041:2054:da00::17fe,2600:8801:2f80:ac::173e,2603:900b:e400:1df:ad07:ea3e:9c6e:c60a,27.252.98.12,27.32.87.112,2804:14c:34:219b::4f5,2804:6950:e:5630:2066:b7f2:c9b3:a4d4,2804:c9c:1:354c:f174:6e99:a597:1ffb,2806:2f0:5240:f865:cfb8:b896:a098:e5dc,2a00:23c8:f80e:6d01:8c5e:b515:1925:bd41,2a00:f2a:e08e:41a0:14a6:43ea:798e:a76a,2a01:e0a:154:3380:d800:a6a8:ecb5:7304,2a01:e0a:e86:2960:b98:53b0:21f4:6228,2a01:e0a:f0:13b0:7948:43c7:4333:39d2,2a02:220b:2000:f800:f52d:9a26:d179:b5cb,2a02:220b:2000:f800:fb46:25d3:84c7:20c0,2a06:63c5:8303:7b00:50f9:52e:4265:b3ee,3.16.175.255,3.211.180.220,31.190.223.238,31.21.210.206,31.46.42.22,34.208.54.193,35.129.55.111,35.133.160.185,35.140.123.29,35.82.222.134,35.83.165.92,35.83.182.185,37.114.42.51,37.128.245.86,37.25.47.141,37.34.175.124,37.34.245.49,37.59.47.160,38.179.98.161,38.34.178.137,44.219.125.103,45.23.63.218,45.249.246.224,45.47.36.160,45.93.114.178,46.175.178.3,46.19.141.178,46.227.66.138,46.24.64.60,46.249.191.157,47.141.45.50,47.144.115.243,47.149.41.219,47.160.10.230,47.183.243.207,47.187.92.112,47.45.255.48,49.158.136.43,5.161.219.121,5.183.131.110,5.196.119.233,5.56.9.159,5.8.205.138,5.9.79.112,50.113.73.100,50.125.82.209,50.175.156.202,50.213.123.122,50.5.249.23,51.38.86.114,52.90.226.234,58.168.225.214,58.226.12.148,59.14.15.215,61.245.159.236,61.77.246.20,62.195.252.247,62.210.217.126,62.80.166.146,62.93.65.111,64.118.245.38,64.223.96.231,64.253.104.118,65.30.102.222,66.129.161.70,66.160.128.215,66.52.20.190,67.180.143.80,67.193.65.177,67.225.3.243,67.240.128.50,67.241.49.48,67.85.196.122,68.101.119.121,68.103.253.106,68.129.90.52,68.146.142.211,68.185.183.72,68.203.5.191,68.21.162.120,68.98.61.233,69.206.99.57,69.226.232.231,69.36.52.44,70.113.210.71,70.16.128.65,70.170.9.35,70.70.14.92,70.78.184.60,70.82.138.163,71.10.126.229,71.126.164.150,71.183.185.118,71.204.146.116,71.227.207.165,71.237.44.127,71.247.165.11,71.31.177.1,71.79.109.128,71.85.54.8,72.179.148.45,72.187.175.134,72.206.123.63,72.224.188.0,72.249.87.49,72.255.188.46,72.66.71.155,72.81.139.70,73.154.107.37,73.160.188.10,73.181.132.4,73.186.15.145,73.190.47.58,73.208.251.19,73.213.196.110,73.231.150.185,74.131.226.86,74.214.214.84,74.91.112.145,74.96.150.228,75.132.65.164,75.143.205.69,75.67.138.54,75.84.91.224,76.18.121.164,76.235.98.101,76.28.254.53,76.64.65.183,76.73.142.42,76.86.62.33,76.9.167.215,78.108.96.228,78.153.4.77,78.46.66.29,79.116.71.137,80.102.12.58,80.244.26.192,81.95.140.101,82.116.38.140,82.2.140.5,82.37.80.176,82.66.159.237,82.66.197.211,82.67.99.238,82.68.85.205,82.76.172.101,83.167.79.9,83.217.162.87,83.252.62.212,84.202.197.114,84.38.22.135,84.47.73.41,85.118.207.197,85.191.19.95,85.195.54.157,85.220.32.157,85.255.89.244,85.50.45.74,86.110.220.58,86.128.75.32,86.150.5.215,86.201.225.172,86.238.183.93,86.253.244.62,86.28.104.37,86.52.27.8,86.60.153.66,87.124.183.82,87.196.5.240,87.79.94.221,88.13.249.4,88.134.40.111,88.147.244.250,88.98.214.124,89.139.48.172,89.171.13.82,9.138.0.151,90.184.11.207,90.240.179.255,90.248.155.122,91.127.232.108,91.153.92.32,91.155.85.151,91.157.142.175,91.190.197.20,91.201.255.25,91.204.149.107,91.215.91.254,92.154.24.7,92.189.23.141,92.205.27.36,92.27.11.82,92.27.11.86,92.27.11.87,93.123.135.12,93.125.121.226,93.240.3.172,94.19.128.204,94.198.51.247,94.198.55.181,95.138.220.244,95.141.35.117,95.216.27.32,95.31.188.110,95.79.52.193,95.84.162.152,96.244.212.63,96.245.12.214,96.52.245.135,96.59.17.81,96.81.219.106,97.85.14.255,97.96.51.52,98.121.99.54,98.165.59.5,98.191.193.194,98.193.88.70,98.210.17.106,98.225.38.106,98.230.8.85,99.109.104.206,99.157.243.27,99.17.251.211,99.172.29.2,99.255.159.147&amp;asmap=2026/1780588800_asmap_unfilled.dat\">overview</a>. \n&hellip;","truncated":true,"post_url":"/t/os-fingerprints-of-16-6k-bitcoin-nodes/152/2","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":531,"name":"stratospher","username":"stratospher","avatar_template":"/user_avatar/bnoc.xyz/stratospher/{size}/134_2.png","created_at":"2026-07-08T07:59:46.886Z","cooked":"<p>interesting! thanks for sharing!</p>\n<aside class=\"quote no-group\" data-username=\"b10c\" data-post=\"3\" data-topic=\"148\">\n<div class=\"title\">\n<div class=\"quote-controls\"></div>\n<img alt=\"\" width=\"24\" height=\"24\" src=\"https://bnoc.xyz/user_avatar/bnoc.xyz/b10c/48/4_2.png\" class=\"avatar\"> b10c:</div>\n<blockquote>\n<p><a href=\"https://bnoc.xyz/t/python-bitcoinlib-0-12-2-client-getting-addr-ratelimited-since-2026-04-10/116\">/python-bitcoinlib:0.12.2</a></p>\n</blockquote>\n</aside>\n<p>DaeConn seems to be a crawler with the <code>connector</code> UA and the hard coded IP is just testing the crawler works.</p>\n<p>maybe the other paper (or some other research) might have this <code>python-bitcoinlib</code> UA and address rate limiting? though the timeline feels a bit short - it was presented in June and the addr spam started in April/May.</p>","post_number":4,"post_type":1,"posts_count":4,"updated_at":"2026-07-08T07:59:46.886Z","reply_count":0,"reply_to_post_number":3,"quote_count":1,"incoming_link_count":0,"reads":5,"readers_count":4,"score":46.0,"yours":false,"topic_id":148,"topic_slug":"continuous-measurement-of-bitcoin-derived-p2p-networks-with-daeconn","topic_title":"Continuous Measurement of Bitcoin-Derived P2P Networks with DaeConn","topic_html_title":"Continuous Measurement of Bitcoin-Derived P2P Networks with DaeConn","category_id":7,"display_username":"stratospher","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"interesting! thanks for sharing!\n\n[quote=\"b10c, post:3, topic:148\"]\n[/python-bitcoinlib:0.12.2](https://bnoc.xyz/t/python-bitcoinlib-0-12-2-client-getting-addr-ratelimited-since-2026-04-10/116)\n[/quote]\n\nDaeConn seems to be a crawler with the `connector` UA and the hard coded IP is just testing the crawler works.\n\nmaybe the other paper (or some other research) might have this `python-bitcoinlib` UA and address rate limiting? though the timeline feels a bit short - it was presented in June and the addr spam started in April/May.","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":43,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"interesting! thanks for sharing! \n\nDaeConn seems to be a crawler with the connector UA and the hard coded IP is just testing the crawler works. \nmaybe the other paper (or some other research) might have this python-bitcoinlib UA and address rate limiting? though the timeline feels a bit short - it w&hellip;","truncated":true,"post_url":"/t/continuous-measurement-of-bitcoin-derived-p2p-networks-with-daeconn/148/4","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":530,"name":"Vinicius Cestari","username":"ViniciusCestarii","avatar_template":"/user_avatar/bnoc.xyz/viniciuscestarii/{size}/315_2.png","created_at":"2026-07-07T22:02:57.389Z","cooked":"<p>I scanned publicly reachable Bitcoin nodes with <code>nmap -O</code> and aggregated the detected operating system as Linux, Windows, BSD, macOS, Other/Device, or Unknown.</p>\n<p>Latest scan (2026-07-07): 16,662 IPv4/IPv6 targets</p>\n<ul>\n<li>Reachable: 10,625 (63.8%)</li>\n<li>Unreachable: 6,037 (36.2%)</li>\n</ul>\n<p>OS classification among reachable hosts (n = 10,625):</p>\n<ul>\n<li>Linux: 6,653 (62.6%)</li>\n<li>Unknown: 2,852 (26.8%)</li>\n<li>Windows: 453 (4.3%)</li>\n<li>Other/Device: 370 (3.5%)</li>\n<li>BSD: 194 (1.8%)</li>\n<li>macOS: 95 (0.9%)</li>\n<li>Other: 6 (0.1%)</li>\n<li>Solaris: 2 (0%)</li>\n</ul>\n<p>Repository with the CSVs, scripts, caveats and full methodology. I plan to monthly scan and update this repo with new data:</p>\n<aside class=\"onebox githubrepo\" data-onebox-src=\"https://github.com/ViniciusCestarii/bitcoin-node-os-fingerprint\">\n  <header class=\"source\">\n\n      <a href=\"https://github.com/ViniciusCestarii/bitcoin-node-os-fingerprint\" target=\"_blank\" rel=\"noopener nofollow ugc\">github.com</a>\n  </header>\n\n  <article class=\"onebox-body\">\n    <div class=\"github-row\" data-github-private-repo=\"false\">\n  <img width=\"690\" height=\"344\" src=\"https://bnoc.xyz/uploads/default/optimized/1X/affe80f1314cd3e3d55076dc362d6061d87bbe80_2_690x344.png\" class=\"thumbnail\" data-dominant-color=\"E5E7E9\">\n\n  <h3><a href=\"https://github.com/ViniciusCestarii/bitcoin-node-os-fingerprint\" target=\"_blank\" rel=\"noopener nofollow ugc\">GitHub - ViniciusCestarii/bitcoin-node-os-fingerprint: Scans publicly reachable Bitcoin nodes with nmap...</a></h3>\n\n    <p><span class=\"github-repo-description\">Scans publicly reachable Bitcoin nodes with nmap -O to guess their operating system</span></p>\n</div>\n\n  </article>\n\n  <div class=\"onebox-metadata\">\n    \n    \n  </div>\n\n  <div style=\"clear: both\"></div>\n</aside>\n","post_number":1,"post_type":1,"posts_count":3,"updated_at":"2026-07-07T22:02:57.389Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":5,"reads":10,"readers_count":9,"score":102.0,"yours":false,"topic_id":152,"topic_slug":"os-fingerprints-of-16-6k-bitcoin-nodes","topic_title":"OS fingerprints of ~16.6k Bitcoin nodes","topic_html_title":"OS fingerprints of ~16.6k Bitcoin nodes","category_id":5,"display_username":"Vinicius Cestari","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"I scanned publicly reachable Bitcoin nodes with `nmap -O` and aggregated the detected operating system as Linux, Windows, BSD, macOS, Other/Device, or Unknown.\n\nLatest scan (2026-07-07): 16,662 IPv4/IPv6 targets\n\n* Reachable: 10,625 (63.8%)\n* Unreachable: 6,037 (36.2%)\n\nOS classification among reachable hosts (n = 10,625):\n\n* Linux: 6,653 (62.6%)\n* Unknown: 2,852 (26.8%)\n* Windows: 453 (4.3%)\n* Other/Device: 370 (3.5%)\n* BSD: 194 (1.8%)\n* macOS: 95 (0.9%)\n* Other: 6 (0.1%)\n* Solaris: 2 (0%)\n\nRepository with the CSVs, scripts, caveats and full methodology. I plan to monthly scan and update this repo with new data:\n\nhttps://github.com/ViniciusCestarii/bitcoin-node-os-fingerprint","actions_summary":[{"id":2,"count":3}],"moderator":false,"admin":false,"staff":false,"user_id":88,"hidden":false,"trust_level":0,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"I scanned publicly reachable Bitcoin nodes with nmap -O and aggregated the detected operating system as Linux, Windows, BSD, macOS, Other/Device, or Unknown. \nLatest scan (2026-07-07): 16,662 IPv4/IPv6 targets \n\nReachable: 10,625 (63.8%)\nUnreachable: 6,037 (36.2%)\n\nOS classification among reachable &hellip;","truncated":true,"post_url":"/t/os-fingerprints-of-16-6k-bitcoin-nodes/152/1","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null,"can_vote":false},{"id":527,"name":"Maycon Fabio","username":"m4ycon","avatar_template":"/user_avatar/bnoc.xyz/m4ycon/{size}/203_2.png","created_at":"2026-07-07T18:09:35.122Z","cooked":"<p>ACK! I totally support this, and agree that a manual way of doing it would be very bad to maintain.</p>\n<p>Brainstorming some ideas:</p>\n<p>I see that it is possible to get information in a json format from this website (<a href=\"https://bnoc.xyz/posts.json\">here</a> and <a href=\"https://bnoc.xyz/latest.json\">here</a>). I think a repository in <a href=\"https://github.com/bitcoin-noc\" rel=\"noopener nofollow ugc\">bitcoin-noc github</a> could have a cron job running an action. When it sees an update, we could feed the data through an llm, so then it could make a commit from it (or a PR?).</p>\n<p>Your reference talks about how can we organize folders/files to serve an llm as context. However, I also see that an interesting format would be the <a href=\"https://bitcoin-noc.github.io/map-of-bitcoin-monitoring/\" rel=\"noopener nofollow ugc\">Map of Bitcoin Monitoring</a>, this organization of graph, it seems a task that a llm would handle well – no need to be that visual but a category/subcategory like sounds good. I think this would be better for human reading, maybe also for llms (?).</p>\n<p>Regarding content on this wiki, I think initially would be good to just gather links and give them some brief context (like I poorly did <a href=\"https://m4ycon.com/bitcoin-datasource-links\" rel=\"noopener nofollow ugc\">here</a> haha). Maybe at some moment, summaries from posts and references for similar ones.</p>","post_number":2,"post_type":1,"posts_count":2,"updated_at":"2026-07-07T18:09:35.122Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":7,"readers_count":6,"score":1.4,"yours":false,"topic_id":149,"topic_slug":"setting-up-a-bnoc-wiki","topic_title":"Setting up a BNOC wiki?","topic_html_title":"Setting up a BNOC wiki?","category_id":2,"display_username":"Maycon Fabio","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"ACK! I totally support this, and agree that a manual way of doing it would be very bad to maintain.\n\nBrainstorming some ideas:\n\nI see that it is possible to get information in a json format from this website ([here](https://bnoc.xyz/posts.json) and [here](https://bnoc.xyz/latest.json)). I think a repository in [bitcoin-noc github](https://github.com/bitcoin-noc) could have a cron job running an action. When it sees an update, we could feed the data through an llm, so then it could make a commit from it (or a PR?).\n\nYour reference talks about how can we organize folders/files to serve an llm as context. However, I also see that an interesting format would be the [Map of Bitcoin Monitoring](https://bitcoin-noc.github.io/map-of-bitcoin-monitoring/), this organization of graph, it seems a task that a llm would handle well – no need to be that visual but a category/subcategory like sounds good. I think this would be better for human reading, maybe also for llms (?).\n\nRegarding content on this wiki, I think initially would be good to just gather links and give them some brief context (like I poorly did [here](https://m4ycon.com/bitcoin-datasource-links) haha). Maybe at some moment, summaries from posts and references for similar ones.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":72,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"ACK! I totally support this, and agree that a manual way of doing it would be very bad to maintain. \nBrainstorming some ideas: \nI see that it is possible to get information in a json format from this website (<a href=\"https://bnoc.xyz/posts.json\">here</a> and <a href=\"https://bnoc.xyz/latest.json\">here</a>). I think a repository in <a href=\"https://github.com/bitcoin-noc\" rel=\"noopener nofollow ugc\">bitcoin-noc github</a> could have a cron job running an&hellip;","truncated":true,"post_url":"/t/setting-up-a-bnoc-wiki/149/2","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":526,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-07-07T11:27:46.426Z","cooked":"<p>I’ve been thinking about a BNOC wiki for all sorts of topics. One idea was to have a sort of <a href=\"https://www.mindstudio.ai/blog/andrej-karpathy-llm-wiki-knowledge-base-claude-code\">llm-wiki</a> style wiki feed with resources, links and ideas from this forum and others. Opening this for discussion here.</p>\n<p>I also thought about a manual wiki, but this will probably be out-date and stale at some point.</p>","post_number":1,"post_type":1,"posts_count":2,"updated_at":"2026-07-07T11:28:48.706Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":2,"reads":7,"readers_count":6,"score":11.4,"yours":false,"topic_id":149,"topic_slug":"setting-up-a-bnoc-wiki","topic_title":"Setting up a BNOC wiki?","topic_html_title":"Setting up a BNOC wiki?","category_id":2,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"I’ve been thinking about a BNOC wiki for all sorts of topics. One idea was to have a sort of [llm-wiki](https://www.mindstudio.ai/blog/andrej-karpathy-llm-wiki-knowledge-base-claude-code) style wiki feed with resources, links and ideas from this forum and others. Opening this for discussion here.\n\nI also thought about a manual wiki, but this will probably be out-date and stale at some point.","actions_summary":[],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"I’ve been thinking about a BNOC wiki for all sorts of topics. One idea was to have a sort of <a href=\"https://www.mindstudio.ai/blog/andrej-karpathy-llm-wiki-knowledge-base-claude-code\">llm-wiki</a> style wiki feed with resources, links and ideas from this forum and others. Opening this for discussion here. \nI also thought about a manual wiki, but this will probably be out-date and stale at som&hellip;","truncated":true,"post_url":"/t/setting-up-a-bnoc-wiki/149/1","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null,"can_vote":false},{"id":525,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-07-07T11:20:24.147Z","cooked":"<p>It seems I don’t have access to this paper.</p>\n<p>We recently saw <a href=\"https://bnoc.xyz/t/python-bitcoinlib-0-12-2-client-getting-addr-ratelimited-since-2026-04-10/116\" class=\"inline-onebox\">/python-bitcoinlib:0.12.2/ client getting addr-ratelimited (since 2026-04-10)</a> from Uni Zurich, but looking at the DaeConn tool a bit, it has a different UA.</p>\n<aside class=\"onebox githubblob\" data-onebox-src=\"https://github.com/DogukanBaysal/DaeConn/blob/e183a43006d1a514a33ce2509c91da4d1a1bbb6e/app/network/scanner.py#L90\">\n  <header class=\"source\">\n\n      <a href=\"https://github.com/DogukanBaysal/DaeConn/blob/e183a43006d1a514a33ce2509c91da4d1a1bbb6e/app/network/scanner.py#L90\" target=\"_blank\" rel=\"noopener\">github.com/DogukanBaysal/DaeConn</a>\n  </header>\n\n  <article class=\"onebox-body\">\n    <h4><a href=\"https://github.com/DogukanBaysal/DaeConn/blob/e183a43006d1a514a33ce2509c91da4d1a1bbb6e/app/network/scanner.py#L90\" target=\"_blank\" rel=\"noopener\">app/network/scanner.py</a></h4>\n\n<div class=\"git-blob-info\">\n  <a href=\"https://github.com/DogukanBaysal/DaeConn/blob/e183a43006d1a514a33ce2509c91da4d1a1bbb6e/app/network/scanner.py#L90\" rel=\"noopener\"><code>e183a4300</code></a>\n</div>\n\n\n\n    <pre class=\"onebox\"><code class=\"lang-py\">\n      <ol class=\"start lines\" start=\"80\" style=\"counter-reset: li-counter 79 ;\">\n          <li>def build_msg(cmd: str, payload: bytes) -&gt; bytes:</li>\n          <li>    name = cmd.encode(\"ascii\")</li>\n          <li>    if len(name) &gt; 12: raise ValueError(\"command too long\")</li>\n          <li>    header = struct.pack(\"&lt;I\", MAGIC) + name + b\"\\x00\"*(12-len(name))</li>\n          <li>    header += struct.pack(\"&lt;I\", len(payload)) + sha256d(payload)[:4]</li>\n          <li>    return header + payload</li>\n          <li></li>\n          <li>def build_version_payload() -&gt; bytes:</li>\n          <li>    version = VERSION; services = 0; ts = int(time.time())</li>\n          <li>    nonce = int.from_bytes(sha256d(str(ts).encode())[:8], \"little\")</li>\n          <li class=\"selected\">    ua = b\"/connector/\"</li>\n          <li>    payload  = struct.pack(\"&lt;iQq\", version, services, ts)</li>\n          <li>    payload += struct.pack(\"&lt;Q\", services) + ip6_from_ipv4(\"0.0.0.0\") + struct.pack(\"&gt;H\", DEFAULT_PORT)</li>\n          <li>    payload += struct.pack(\"&lt;Q\", services) + ip6_from_ipv4(\"0.0.0.0\") + struct.pack(\"&gt;H\", 0)</li>\n          <li>    payload += struct.pack(\"&lt;Q\", nonce)</li>\n          <li>    payload += bytes([len(ua)]) + ua</li>\n          <li>    payload += struct.pack(\"&lt;i\", 0) + b\"\\x00\" </li>\n          <li>    return payload</li>\n          <li></li>\n          <li>def build_ping_payload(nonce: int) -&gt; bytes:</li>\n          <li>    return struct.pack(\"&lt;Q\", nonce)</li>\n      </ol>\n    </code></pre>\n\n\n\n  </article>\n\n  <div class=\"onebox-metadata\">\n    \n    \n  </div>\n\n  <div style=\"clear: both\"></div>\n</aside>\n\n<p>and seems to also hardcode an IP I haven’t seen here before:</p>\n<aside class=\"onebox githubblob\" data-onebox-src=\"https://github.com/DogukanBaysal/DaeConn/blob/e183a43006d1a514a33ce2509c91da4d1a1bbb6e/app/network/scanner.py#L309\">\n  <header class=\"source\">\n\n      <a href=\"https://github.com/DogukanBaysal/DaeConn/blob/e183a43006d1a514a33ce2509c91da4d1a1bbb6e/app/network/scanner.py#L309\" target=\"_blank\" rel=\"noopener\">github.com/DogukanBaysal/DaeConn</a>\n  </header>\n\n  <article class=\"onebox-body\">\n    <h4><a href=\"https://github.com/DogukanBaysal/DaeConn/blob/e183a43006d1a514a33ce2509c91da4d1a1bbb6e/app/network/scanner.py#L309\" target=\"_blank\" rel=\"noopener\">app/network/scanner.py</a></h4>\n\n<div class=\"git-blob-info\">\n  <a href=\"https://github.com/DogukanBaysal/DaeConn/blob/e183a43006d1a514a33ce2509c91da4d1a1bbb6e/app/network/scanner.py#L309\" rel=\"noopener\"><code>e183a4300</code></a>\n</div>\n\n\n\n    <pre class=\"onebox\"><code class=\"lang-py\">\n      <ol class=\"start lines\" start=\"299\" style=\"counter-reset: li-counter 298 ;\">\n          <li>        self.sock = None</li>\n          <li></li>\n          <li>def scan_peer(host: str, port: int = DEFAULT_PORT) -&gt; Optional[List[Dict]]:</li>\n          <li>    cli = DogeLiveScanner(host, port)</li>\n          <li>    if not cli.connect(): return None</li>\n          <li>    print(f\"[+] Connected to {host}:{port}\")</li>\n          <li>    cli.handshake()</li>\n          <li>    return cli.run()</li>\n          <li></li>\n          <li>if __name__ == \"__main__\":</li>\n          <li class=\"selected\">    host = sys.argv[1] if len(sys.argv) &gt; 1 else \"185.252.234.250\"</li>\n          <li>    port = int(sys.argv[2]) if len(sys.argv) &gt; 2 else DEFAULT_PORT</li>\n          <li>    rows = scan_peer(host, port)</li>\n          <li>    if not rows:</li>\n          <li>        print(\"[-] No peers found.\")</li>\n          <li>    else:</li>\n          <li>        print(f\"[+] Rows: {len(rows)}\")</li>\n          <li>        for r in rows[:5]:</li>\n          <li>            print(r)</li>\n      </ol>\n    </code></pre>\n\n\n\n  </article>\n\n  <div class=\"onebox-metadata\">\n    \n    \n  </div>\n\n  <div style=\"clear: both\"></div>\n</aside>\n","post_number":3,"post_type":1,"posts_count":4,"updated_at":"2026-07-07T11:20:24.147Z","reply_count":1,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":8,"readers_count":7,"score":6.6,"yours":false,"topic_id":148,"topic_slug":"continuous-measurement-of-bitcoin-derived-p2p-networks-with-daeconn","topic_title":"Continuous Measurement of Bitcoin-Derived P2P Networks with DaeConn","topic_html_title":"Continuous Measurement of Bitcoin-Derived P2P Networks with DaeConn","category_id":7,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"It seems I don’t have access to this paper.\n\nWe recently saw https://bnoc.xyz/t/python-bitcoinlib-0-12-2-client-getting-addr-ratelimited-since-2026-04-10/116 from Uni Zurich, but looking at the DaeConn tool a bit, it has a different UA. \n\nhttps://github.com/DogukanBaysal/DaeConn/blob/e183a43006d1a514a33ce2509c91da4d1a1bbb6e/app/network/scanner.py#L90\n\nand seems to also hardcode an IP I haven’t seen here before:\n\nhttps://github.com/DogukanBaysal/DaeConn/blob/e183a43006d1a514a33ce2509c91da4d1a1bbb6e/app/network/scanner.py#L309","actions_summary":[],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"It seems I don’t have access to this paper. \nWe recently saw <a href=\"https://bnoc.xyz/t/python-bitcoinlib-0-12-2-client-getting-addr-ratelimited-since-2026-04-10/116\" class=\"inline-onebox\">/python-bitcoinlib:0.12.2/ client getting addr-ratelimited (since 2026-04-10)</a> from Uni Zurich, but looking at the DaeConn tool a bit, it has a different UA. \n\n\nand seems to also hardcode an IP I haven’t seen here before:","truncated":true,"post_url":"/t/continuous-measurement-of-bitcoin-derived-p2p-networks-with-daeconn/148/3","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":524,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-07-07T11:07:22.029Z","cooked":"<p>There’s also <a href=\"https://bitcoin-noc.github.io/map-of-bitcoin-monitoring/\" class=\"inline-onebox\">Map of Bitcoin Monitoring</a> (a bit out of date, updates welcome)</p>\n<p><div class=\"lightbox-wrapper\"><a class=\"lightbox\" href=\"https://bnoc.xyz/uploads/default/original/1X/0b689ac7e997ab16cc432a6a7a46e1ebe8030923.jpeg\" data-download-href=\"https://bnoc.xyz/uploads/default/0b689ac7e997ab16cc432a6a7a46e1ebe8030923\" title=\"image\"><img src=\"https://bnoc.xyz/uploads/default/optimized/1X/0b689ac7e997ab16cc432a6a7a46e1ebe8030923_2_690x462.jpeg\" alt=\"image\" data-base62-sha1=\"1CVmIV3tytg6fIhiUU59GCvfc0X\" width=\"690\" height=\"462\" srcset=\"https://bnoc.xyz/uploads/default/optimized/1X/0b689ac7e997ab16cc432a6a7a46e1ebe8030923_2_690x462.jpeg, https://bnoc.xyz/uploads/default/optimized/1X/0b689ac7e997ab16cc432a6a7a46e1ebe8030923_2_1035x693.jpeg 1.5x, https://bnoc.xyz/uploads/default/optimized/1X/0b689ac7e997ab16cc432a6a7a46e1ebe8030923_2_1380x924.jpeg 2x\" data-dominant-color=\"F8F8F8\"><div class=\"meta\"><svg class=\"fa d-icon d-icon-far-image svg-icon\" aria-hidden=\"true\"><use href=\"#far-image\"></use></svg><span class=\"filename\">image</span><span class=\"informations\">1855×1243 235 KB</span><svg class=\"fa d-icon d-icon-discourse-expand svg-icon\" aria-hidden=\"true\"><use href=\"#discourse-expand\"></use></svg></div></a></div></p>\n<p>and a dedicated thread for it: <a href=\"https://bnoc.xyz/t/resources-monitoring-and-network-data/37\" class=\"inline-onebox\">Resources: monitoring and network data</a></p>\n<p>and jlopp maintains a page with links too: <a href=\"https://www.lopp.net/bitcoin-information.html\" class=\"inline-onebox\">Bitcoin Information &amp; Educational Resources</a></p>\n<p>I think this needs a collaborative way of maintaining it. Maybe some kind of BNOC wiki?</p>","post_number":9,"post_type":1,"posts_count":8,"updated_at":"2026-07-07T11:07:45.669Z","reply_count":0,"reply_to_post_number":7,"quote_count":0,"incoming_link_count":0,"reads":6,"readers_count":5,"score":0.8,"yours":false,"topic_id":147,"topic_slug":"f2pool-mines-two-blocks-at-height-956337","topic_title":"F2Pool mines two blocks at height 956337","topic_html_title":"F2Pool mines two blocks at height 956337","category_id":8,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"reply_to_user":{"id":63,"username":"sudocarlos","name":"Sudocarlos","avatar_template":"/user_avatar/bnoc.xyz/sudocarlos/{size}/176_2.png"},"bookmarked":false,"raw":"There’s also https://bitcoin-noc.github.io/map-of-bitcoin-monitoring/ (a bit out of date, updates welcome)\n\n![image|690x462](upload://1CVmIV3tytg6fIhiUU59GCvfc0X.jpeg)\n\nand a dedicated thread for it: https://bnoc.xyz/t/resources-monitoring-and-network-data/37\n\nand jlopp maintains a page with links too: https://www.lopp.net/bitcoin-information.html\n\nI think this needs a collaborative way of maintaining it. Maybe some kind of BNOC wiki?","actions_summary":[{"id":2,"count":1}],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"There’s also <a href=\"https://bitcoin-noc.github.io/map-of-bitcoin-monitoring/\" class=\"inline-onebox\">Map of Bitcoin Monitoring</a> (a bit out of date, updates welcome) \n <a class=\"lightbox\" href=\"https://bnoc.xyz/uploads/default/original/1X/0b689ac7e997ab16cc432a6a7a46e1ebe8030923.jpeg\" data-download-href=\"https://bnoc.xyz/uploads/default/0b689ac7e997ab16cc432a6a7a46e1ebe8030923\" title=\"image\">[image]</a> \nand a dedicated thread for it: <a href=\"https://bnoc.xyz/t/resources-monitoring-and-network-data/37\" class=\"inline-onebox\">Resources: monitoring and network data</a> \nand jlopp maintains a page with links too: <a href=\"https://www.lopp.net/bitcoin-information.html\" class=\"inline-onebox\">Bitcoin Information &amp; Educational Resources</a> \nI think this needs a collaborative way of maintaining &hellip;","truncated":true,"post_url":"/t/f2pool-mines-two-blocks-at-height-956337/147/9","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":523,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-07-07T11:01:14.008Z","cooked":"<p><div class=\"lightbox-wrapper\"><a class=\"lightbox\" href=\"https://bnoc.xyz/uploads/default/original/1X/c99dd8abd96d2992b4876bc99dd1a4b1c18f20b8.png\" data-download-href=\"https://bnoc.xyz/uploads/default/c99dd8abd96d2992b4876bc99dd1a4b1c18f20b8\" title=\"image\"><img src=\"https://bnoc.xyz/uploads/default/optimized/1X/c99dd8abd96d2992b4876bc99dd1a4b1c18f20b8_2_690x429.png\" alt=\"image\" data-base62-sha1=\"sLA9F68P411uMDXCzBbQUwmcUo8\" width=\"690\" height=\"429\" srcset=\"https://bnoc.xyz/uploads/default/optimized/1X/c99dd8abd96d2992b4876bc99dd1a4b1c18f20b8_2_690x429.png, https://bnoc.xyz/uploads/default/optimized/1X/c99dd8abd96d2992b4876bc99dd1a4b1c18f20b8_2_1035x643.png 1.5x, https://bnoc.xyz/uploads/default/optimized/1X/c99dd8abd96d2992b4876bc99dd1a4b1c18f20b8_2_1380x858.png 2x\" data-dominant-color=\"F7F7F8\"><div class=\"meta\"><svg class=\"fa d-icon d-icon-far-image svg-icon\" aria-hidden=\"true\"><use href=\"#far-image\"></use></svg><span class=\"filename\">image</span><span class=\"informations\">2112×1314 118 KB</span><svg class=\"fa d-icon d-icon-discourse-expand svg-icon\" aria-hidden=\"true\"><use href=\"#discourse-expand\"></use></svg></div></a></div></p>\n<p>added a height based countdown feature for halving/soft-forks/special heights to fork-observer: <a href=\"https://github.com/0xB10C/fork-observer/pull/142\" class=\"inline-onebox\">add: per-network height countdown by 0xB10C · Pull Request #142 · 0xB10C/fork-observer · GitHub</a></p>","post_number":8,"post_type":1,"posts_count":8,"updated_at":"2026-07-07T11:01:14.008Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":8,"readers_count":7,"score":1.4,"yours":false,"topic_id":139,"topic_slug":"brainstorming-what-data-to-collect-and-monitor-during-the-bip-110-bip-300-forks-in-august-2026","topic_title":"Brainstorming: What data to collect and monitor during the BIP-110 & BIP-300 forks in August 2026?","topic_html_title":"Brainstorming: What data to collect and monitor during the BIP-110 &amp; BIP-300 forks in August 2026?","category_id":5,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"![image|690x429](upload://sLA9F68P411uMDXCzBbQUwmcUo8.png)\n\nadded a height based countdown feature for halving/soft-forks/special heights to fork-observer: https://github.com/0xB10C/fork-observer/pull/142","actions_summary":[],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"<a class=\"lightbox\" href=\"https://bnoc.xyz/uploads/default/original/1X/c99dd8abd96d2992b4876bc99dd1a4b1c18f20b8.png\" data-download-href=\"https://bnoc.xyz/uploads/default/c99dd8abd96d2992b4876bc99dd1a4b1c18f20b8\" title=\"image\">[image]</a> \nadded a height based countdown feature for halving/soft-forks/special heights to fork-observer: <a href=\"https://github.com/0xB10C/fork-observer/pull/142\" class=\"inline-onebox\">add: per-network height countdown by 0xB10C · Pull Request #142 · 0xB10C/fork-observer · GitHub</a>","truncated":true,"post_url":"/t/brainstorming-what-data-to-collect-and-monitor-during-the-bip-110-bip-300-forks-in-august-2026/139/8","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":522,"name":"Matthias Grundmann","username":"matthias","avatar_template":"/user_avatar/bnoc.xyz/matthias/{size}/39_2.png","created_at":"2026-07-07T08:44:13.017Z","cooked":"<p>Related to this, the same authors simulated the Bitcoin P2P network and analyzed the simulated network’s topology and how blocks are propagated in a simulated network:</p>\n<ul>\n<li><a href=\"https://ieeexplore.ieee.org/document/11575505\" rel=\"noopener nofollow ugc\">Protocol Driven Dynamics of the Bitcoin Peer-to-Peer Network under Churn</a></li>\n<li><a href=\"https://ieeexplore.ieee.org/document/11575512\" rel=\"noopener nofollow ugc\">Non-Monotonic Effects of Node Churn on Block Synchronization in Bitcoin</a></li>\n</ul>","post_number":2,"post_type":1,"posts_count":4,"updated_at":"2026-07-07T08:44:13.017Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":9,"readers_count":8,"score":61.8,"yours":false,"topic_id":148,"topic_slug":"continuous-measurement-of-bitcoin-derived-p2p-networks-with-daeconn","topic_title":"Continuous Measurement of Bitcoin-Derived P2P Networks with DaeConn","topic_html_title":"Continuous Measurement of Bitcoin-Derived P2P Networks with DaeConn","category_id":7,"display_username":"Matthias Grundmann","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"Related to this, the same authors simulated the Bitcoin P2P network and analyzed the simulated network’s topology and how blocks are propagated in a simulated network:\n\n* [Protocol Driven Dynamics of the Bitcoin Peer-to-Peer Network under Churn](https://ieeexplore.ieee.org/document/11575505)\n* [Non-Monotonic Effects of Node Churn on Block Synchronization in Bitcoin](https://ieeexplore.ieee.org/document/11575512)","actions_summary":[{"id":2,"count":2}],"moderator":false,"admin":false,"staff":false,"user_id":12,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Related to this, the same authors simulated the Bitcoin P2P network and analyzed the simulated network’s topology and how blocks are propagated in a simulated network: \n\n<a href=\"https://ieeexplore.ieee.org/document/11575505\" rel=\"noopener nofollow ugc\">Protocol Driven Dynamics of the Bitcoin Peer-to-Peer Network under Churn</a>\n<a href=\"https://ieeexplore.ieee.org/document/11575512\" rel=\"noopener nofollow ugc\">Non-Monotonic Effects of Node Churn on Block Synchronizat&hellip;</a>","truncated":true,"post_url":"/t/continuous-measurement-of-bitcoin-derived-p2p-networks-with-daeconn/148/2","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":521,"name":"Matthias Grundmann","username":"matthias","avatar_template":"/user_avatar/bnoc.xyz/matthias/{size}/39_2.png","created_at":"2026-07-07T08:34:16.936Z","cooked":"<p>I just came across this recent paper written by a team from Uni Zurich: <a href=\"https://ieeexplore.ieee.org/document/11575443\" rel=\"noopener nofollow ugc\">Demo: Continuous Measurement of Bitcoin-Derived P2P Networks with DaeConn</a></p>\n<p>It describes a measurement tool that finds peers in the network and collects information about them. Thus, the tool is an implementation of a `spy node’ similar to bitnodes. The tool is available at <a href=\"https://github.com/DogukanBaysal/DaeConn\" class=\"inline-onebox\" rel=\"noopener nofollow ugc\">GitHub - DogukanBaysal/DaeConn · GitHub</a></p>","post_number":1,"post_type":1,"posts_count":4,"updated_at":"2026-07-07T08:34:16.936Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":4,"reads":9,"readers_count":8,"score":96.8,"yours":false,"topic_id":148,"topic_slug":"continuous-measurement-of-bitcoin-derived-p2p-networks-with-daeconn","topic_title":"Continuous Measurement of Bitcoin-Derived P2P Networks with DaeConn","topic_html_title":"Continuous Measurement of Bitcoin-Derived P2P Networks with DaeConn","category_id":7,"display_username":"Matthias Grundmann","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"I just came across this recent paper written by a team from Uni Zurich: [Demo: Continuous Measurement of Bitcoin-Derived P2P Networks with DaeConn](https://ieeexplore.ieee.org/document/11575443)\n\nIt describes a measurement tool that finds peers in the network and collects information about them. Thus, the tool is an implementation of a \\`spy node’ similar to bitnodes. The tool is available at https://github.com/DogukanBaysal/DaeConn","actions_summary":[{"id":2,"count":3}],"moderator":false,"admin":false,"staff":false,"user_id":12,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"I just came across this recent paper written by a team from Uni Zurich: <a href=\"https://ieeexplore.ieee.org/document/11575443\" rel=\"noopener nofollow ugc\">Demo: Continuous Measurement of Bitcoin-Derived P2P Networks with DaeConn</a> \nIt describes a measurement tool that finds peers in the network and collects information about them. Thus, the tool is an implementation of a `spy node’ &hellip;","truncated":true,"post_url":"/t/continuous-measurement-of-bitcoin-derived-p2p-networks-with-daeconn/148/1","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null,"can_vote":false},{"id":520,"name":"Maycon Fabio","username":"m4ycon","avatar_template":"/user_avatar/bnoc.xyz/m4ycon/{size}/203_2.png","created_at":"2026-07-06T19:46:11.823Z","cooked":"<p>I used to keep a personal list for myself (and Vinteum’s discord), but I see that it would be better if I had it somewhere public as it can be useful to someone. Here is a gist where I’ve been aggregating some links that I found interesting through my bnoc readings: <a href=\"https://m4ycon.com/bitcoin-datasource-links\" rel=\"noopener nofollow ugc\">Bitcoin datasource links</a>. I still need to describe some of them. And you will probably find all of them here in BNOC (for more context).</p>","post_number":8,"post_type":1,"posts_count":8,"updated_at":"2026-07-06T20:37:35.709Z","reply_count":0,"reply_to_post_number":7,"quote_count":0,"incoming_link_count":0,"reads":7,"readers_count":6,"score":1.0,"yours":false,"topic_id":147,"topic_slug":"f2pool-mines-two-blocks-at-height-956337","topic_title":"F2Pool mines two blocks at height 956337","topic_html_title":"F2Pool mines two blocks at height 956337","category_id":8,"display_username":"Maycon Fabio","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":2,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"reply_to_user":{"id":63,"username":"sudocarlos","name":"Sudocarlos","avatar_template":"/user_avatar/bnoc.xyz/sudocarlos/{size}/176_2.png"},"bookmarked":false,"raw":"I used to keep a personal list for myself (and Vinteum’s discord), but I see that it would be better if I had it somewhere public as it can be useful to someone. Here is a gist where I’ve been aggregating some links that I found interesting through my bnoc readings: [Bitcoin datasource links](https://m4ycon.com/bitcoin-datasource-links). I still need to describe some of them. And you will probably find all of them here in BNOC (for more context).","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":72,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"I used to keep a personal list for myself (and Vinteum’s discord), but I see that it would be better if I had it somewhere public as it can be useful to someone. Here is a gist where I’ve been aggregating some links that I found interesting through my bnoc readings: <a href=\"https://m4ycon.com/bitcoin-datasource-links\" rel=\"noopener nofollow ugc\">Bitcoin datasource links</a>. I still&hellip;","truncated":true,"post_url":"/t/f2pool-mines-two-blocks-at-height-956337/147/8","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":519,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-07-03T15:38:33.933Z","cooked":"<p>Seeing this makes me think we are going to see a bunch of inscriptions being broadcast for a potential BIP-110 compliant block right before around/activation: <a href=\"https://github.com/ordinals/ord/pull/4545\" class=\"inline-onebox\">Add BIP-110 compatible envelope parser by lifofifoX · Pull Request #4545 · ordinals/ord · GitHub</a> . Well, there also seems to be <a href=\"https://github.com/bitcoinknots/bitcoin/pull/319\" class=\"inline-onebox\">policy: count bare data envelopes (OP_2DROP/pushnum runs) as datacarrier by kwsantiago · Pull Request #319 · bitcoinknots/bitcoin · GitHub</a> now…</p>","post_number":7,"post_type":1,"posts_count":8,"updated_at":"2026-07-03T15:40:26.210Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":14,"readers_count":13,"score":2.8,"yours":false,"topic_id":139,"topic_slug":"brainstorming-what-data-to-collect-and-monitor-during-the-bip-110-bip-300-forks-in-august-2026","topic_title":"Brainstorming: What data to collect and monitor during the BIP-110 & BIP-300 forks in August 2026?","topic_html_title":"Brainstorming: What data to collect and monitor during the BIP-110 &amp; BIP-300 forks in August 2026?","category_id":5,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"Seeing this makes me think we are going to see a bunch of inscriptions being broadcast for a potential BIP-110 compliant block right before around/activation: https://github.com/ordinals/ord/pull/4545 . Well, there also seems to be https://github.com/bitcoinknots/bitcoin/pull/319 now…","actions_summary":[],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Seeing this makes me think we are going to see a bunch of inscriptions being broadcast for a potential BIP-110 compliant block right before around/activation: <a href=\"https://github.com/ordinals/ord/pull/4545\" class=\"inline-onebox\">Add BIP-110 compatible envelope parser by lifofifoX · Pull Request #4545 · ordinals/ord · GitHub</a> . Well, there also seems to be <a href=\"https://github.com/bitcoinknots/bitcoin/pull/319\" class=\"inline-onebox\">policy: count&hellip;</a>","truncated":true,"post_url":"/t/brainstorming-what-data-to-collect-and-monitor-during-the-bip-110-bip-300-forks-in-august-2026/139/7","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":518,"name":"Sudocarlos","username":"sudocarlos","avatar_template":"/user_avatar/bnoc.xyz/sudocarlos/{size}/176_2.png","created_at":"2026-07-03T13:08:45.238Z","cooked":"<aside class=\"quote no-group\" data-username=\"b10c\" data-post=\"6\" data-topic=\"147\">\n<div class=\"title\">\n<div class=\"quote-controls\"></div>\n<img alt=\"\" width=\"24\" height=\"24\" src=\"https://bnoc.xyz/user_avatar/bnoc.xyz/b10c/48/4_2.png\" class=\"avatar\"> b10c:</div>\n<blockquote>\n<p>On <a class=\"mention\" href=\"/u/boerst\">@boerst</a>’s <a href=\"https://stratum.work/height/956337\" rel=\"noopener nofollow ugc\">Stratum Work</a></p>\n</blockquote>\n</aside>\n<p>Is there a collection of sites like these? I keep discovering more through posts on these boards, but have never seen a single repository of project links.</p>","post_number":7,"post_type":1,"posts_count":8,"updated_at":"2026-07-03T13:08:45.238Z","reply_count":2,"reply_to_post_number":6,"quote_count":1,"incoming_link_count":0,"reads":11,"readers_count":10,"score":12.2,"yours":false,"topic_id":147,"topic_slug":"f2pool-mines-two-blocks-at-height-956337","topic_title":"F2Pool mines two blocks at height 956337","topic_html_title":"F2Pool mines two blocks at height 956337","category_id":8,"display_username":"Sudocarlos","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"[quote=\"b10c, post:6, topic:147\"]\nOn @boerst’s [Stratum Work](https://stratum.work/height/956337)\n[/quote]\n\nIs there a collection of sites like these? I keep discovering more through posts on these boards, but have never seen a single repository of project links.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":63,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Is there a collection of sites like these? I keep discovering more through posts on these boards, but have never seen a single repository of project links.","truncated":true,"post_url":"/t/f2pool-mines-two-blocks-at-height-956337/147/7","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":517,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-07-03T12:54:28.415Z","cooked":"<p>On <a class=\"mention\" href=\"/u/boerst\">@boerst</a>’s <a href=\"https://stratum.work/height/956337\" class=\"inline-onebox\">Stratum Work</a> , the last jobs with an F2Pool coinbase tag were broadcast at</p>\n<ul>\n<li>F2Pool: <code>1782981814</code></li>\n<li>ntminerPool: <code>1782981828</code></li>\n<li>DogPool: <code>1782981828</code></li>\n</ul>\n<p><div class=\"lightbox-wrapper\"><a class=\"lightbox\" href=\"https://bnoc.xyz/uploads/default/original/1X/373cc7f84e77a44e3d4b28140767080f131aad33.png\" data-download-href=\"https://bnoc.xyz/uploads/default/373cc7f84e77a44e3d4b28140767080f131aad33\" title=\"image\"><img src=\"https://bnoc.xyz/uploads/default/optimized/1X/373cc7f84e77a44e3d4b28140767080f131aad33_2_690x113.png\" alt=\"image\" data-base62-sha1=\"7SEtZVaTK35tDM5SpvRJPcsaBa3\" width=\"690\" height=\"113\" srcset=\"https://bnoc.xyz/uploads/default/optimized/1X/373cc7f84e77a44e3d4b28140767080f131aad33_2_690x113.png, https://bnoc.xyz/uploads/default/optimized/1X/373cc7f84e77a44e3d4b28140767080f131aad33_2_1035x169.png 1.5x, https://bnoc.xyz/uploads/default/original/1X/373cc7f84e77a44e3d4b28140767080f131aad33.png 2x\" data-dominant-color=\"282138\"><div class=\"meta\"><svg class=\"fa d-icon d-icon-far-image svg-icon\" aria-hidden=\"true\"><use href=\"#far-image\"></use></svg><span class=\"filename\">image</span><span class=\"informations\">1057×174 42.8 KB</span><svg class=\"fa d-icon d-icon-discourse-expand svg-icon\" aria-hidden=\"true\"><use href=\"#discourse-expand\"></use></svg></div></a></div></p>\n<p>Both ntminerPool and DogPool have a slightly higher coinbase output value of 3.14003902 BTC as the winning and loosing blocks (‎3.13976509 BTC), so my guess is that they were indeed generated later.</p>\n<p>The page also shows:</p>\n<p><div class=\"lightbox-wrapper\"><a class=\"lightbox\" href=\"https://bnoc.xyz/uploads/default/original/1X/6a95802bd19caf1d5052fc4b9e64879e7cc68d51.png\" data-download-href=\"https://bnoc.xyz/uploads/default/6a95802bd19caf1d5052fc4b9e64879e7cc68d51\" title=\"image\"><img src=\"https://bnoc.xyz/uploads/default/original/1X/6a95802bd19caf1d5052fc4b9e64879e7cc68d51.png\" alt=\"image\" data-base62-sha1=\"fcSULsEKYaWdeEeOW6Dw6bOEAw1\" width=\"690\" height=\"456\" data-dominant-color=\"222242\"><div class=\"meta\"><svg class=\"fa d-icon d-icon-far-image svg-icon\" aria-hidden=\"true\"><use href=\"#far-image\"></use></svg><span class=\"filename\">image</span><span class=\"informations\">1335×883 59.6 KB</span><svg class=\"fa d-icon d-icon-discourse-expand svg-icon\" aria-hidden=\"true\"><use href=\"#discourse-expand\"></use></svg></div></a></div></p>\n<p>Which indicates that big parts of the network were mining on the loosing block. Some pools switched to the winning (but 9s later header-timestamp) block:</p>\n<ul>\n<li>nthminerpool and DogPool after 800ms for very short time period.</li>\n<li>BitFuFu after 3.7s</li>\n<li>Poolin, Ultimus, Binance, CloverPool after about 7s</li>\n</ul>\n<p>F2Pool themself never switched.</p>\n<p>So the timestamp of the winning block might indeed have been rolled to 1782981823, while the loosing block didn’t roll. The loosing block was probably found about 800ms before the winning block. No idea why Antpool’s friends decided to switch, but Antpool not.</p>","post_number":6,"post_type":1,"posts_count":8,"updated_at":"2026-07-03T12:54:28.415Z","reply_count":1,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":11,"readers_count":10,"score":22.2,"yours":false,"topic_id":147,"topic_slug":"f2pool-mines-two-blocks-at-height-956337","topic_title":"F2Pool mines two blocks at height 956337","topic_html_title":"F2Pool mines two blocks at height 956337","category_id":8,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"On @boerst’s https://stratum.work/height/956337 , the last jobs with an F2Pool coinbase tag were broadcast at \n\n* F2Pool: `1782981814`\n* ntminerPool: `1782981828`\n* DogPool: `1782981828`\n\n![image|690x113](upload://7SEtZVaTK35tDM5SpvRJPcsaBa3.png)\n\nBoth ntminerPool and DogPool have a slightly higher coinbase output value of 3.14003902 BTC as the winning and loosing blocks (‎3.13976509 BTC), so my guess is that they were indeed generated later.\n\nThe page also shows:\n\n![image|690x456](upload://fcSULsEKYaWdeEeOW6Dw6bOEAw1.png)\n\nWhich indicates that big parts of the network were mining on the loosing block. Some pools switched to the winning (but 9s later header-timestamp) block:\n\n* nthminerpool and DogPool after 800ms for very short time period.\n* BitFuFu after 3.7s\n* Poolin, Ultimus, Binance, CloverPool after about 7s\n\nF2Pool themself never switched.\n\nSo the timestamp of the winning block might indeed have been rolled to 1782981823, while the loosing block didn’t roll. The loosing block was probably found about 800ms before the winning block. No idea why Antpool’s friends decided to switch, but Antpool not.","actions_summary":[{"id":2,"count":1}],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"On <a class=\"mention\" href=\"/u/boerst\">@boerst</a>’s <a href=\"https://stratum.work/height/956337\" class=\"inline-onebox\">Stratum Work</a> , the last jobs with an F2Pool coinbase tag were broadcast at \n\nF2Pool: 1782981814\nntminerPool: 1782981828\nDogPool: 1782981828\n\n <a class=\"lightbox\" href=\"https://bnoc.xyz/uploads/default/original/1X/373cc7f84e77a44e3d4b28140767080f131aad33.png\" data-download-href=\"https://bnoc.xyz/uploads/default/373cc7f84e77a44e3d4b28140767080f131aad33\" title=\"image\">[image]</a> \nBoth ntminerPool and DogPool have a slightly higher coinbase output value of 3.14003902 BTC as the winning and loosing blocks (‎3.139765&hellip;","truncated":true,"post_url":"/t/f2pool-mines-two-blocks-at-height-956337/147/6","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":515,"name":"Sudocarlos","username":"sudocarlos","avatar_template":"/user_avatar/bnoc.xyz/sudocarlos/{size}/176_2.png","created_at":"2026-07-02T18:19:57.781Z","cooked":"<aside class=\"quote no-group quote-modified\" data-username=\"b10c\" data-post=\"2\" data-topic=\"147\">\n<div class=\"title\">\n<div class=\"quote-controls\"></div>\n<img alt=\"\" width=\"24\" height=\"24\" src=\"https://bnoc.xyz/user_avatar/bnoc.xyz/b10c/48/4_2.png\" class=\"avatar\"> b10c:</div>\n<blockquote>\n<p>The interesting part here is that the winning block has header timestamp <code>1782981823</code> vs <code>1782981814</code> of the loosing block</p>\n</blockquote>\n</aside>\n<p>couldnt it also be a result of using the timestamp to roll nonce? <a href=\"https://groups.google.com/g/bitcoindev/c/fCfbi8hy-AE\" rel=\"noopener nofollow ugc\">https://groups.google.com/g/bitcoindev/c/fCfbi8hy-AE</a></p>","post_number":4,"post_type":1,"posts_count":8,"updated_at":"2026-07-02T18:19:57.781Z","reply_count":0,"reply_to_post_number":2,"quote_count":1,"incoming_link_count":1,"reads":12,"readers_count":11,"score":22.4,"yours":false,"topic_id":147,"topic_slug":"f2pool-mines-two-blocks-at-height-956337","topic_title":"F2Pool mines two blocks at height 956337","topic_html_title":"F2Pool mines two blocks at height 956337","category_id":8,"display_username":"Sudocarlos","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"[quote=\"b10c, post:2, topic:147\"]\nThe interesting part here is that the winning block has header timestamp `1782981823` vs `1782981814` of the loosing block\n\n[/quote]\n\ncouldnt it also be a result of using the timestamp to roll nonce? https://groups.google.com/g/bitcoindev/c/fCfbi8hy-AE","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":63,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"couldnt it also be a result of using the timestamp to roll nonce? <a href=\"https://groups.google.com/g/bitcoindev/c/fCfbi8hy-AE\" rel=\"noopener nofollow ugc\">https://groups.google.com/g/bitcoindev/c/fCfbi8hy-AE</a>","truncated":true,"post_url":"/t/f2pool-mines-two-blocks-at-height-956337/147/4","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":513,"name":"Deadmanoz","username":"deadmanoz","avatar_template":"/user_avatar/bnoc.xyz/deadmanoz/{size}/20_2.png","created_at":"2026-07-02T15:29:08.641Z","cooked":"<p>Yeah, that could be it.. there’s no stratum data for Foundry we could cross-reference right?</p>","post_number":7,"post_type":1,"posts_count":7,"updated_at":"2026-07-02T15:29:08.641Z","reply_count":0,"reply_to_post_number":4,"quote_count":0,"incoming_link_count":1,"reads":11,"readers_count":10,"score":6.8,"yours":false,"topic_id":146,"topic_slug":"introducing-the-merge-mining-monitor","topic_title":"Introducing the Merge Mining Monitor","topic_html_title":"Introducing the Merge Mining Monitor","category_id":7,"display_username":"Deadmanoz","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"reply_to_user":{"id":16,"username":"ajtowns","name":"Anthony Towns","avatar_template":"/user_avatar/bnoc.xyz/ajtowns/{size}/64_2.png"},"bookmarked":false,"raw":"Yeah, that could be it.. there's no stratum data for Foundry we could cross-reference right?","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":7,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Yeah, that could be it.. there’s no stratum data for Foundry we could cross-reference right?","truncated":true,"post_url":"/t/introducing-the-merge-mining-monitor/146/7","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":512,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-07-02T15:23:34.306Z","cooked":"<p>Also didn’t find any of these hashes in my peer-observer debug.logs</p>","post_number":6,"post_type":1,"posts_count":7,"updated_at":"2026-07-02T15:23:34.306Z","reply_count":0,"reply_to_post_number":5,"quote_count":0,"incoming_link_count":1,"reads":11,"readers_count":10,"score":6.8,"yours":false,"topic_id":146,"topic_slug":"introducing-the-merge-mining-monitor","topic_title":"Introducing the Merge Mining Monitor","topic_html_title":"Introducing the Merge Mining Monitor","category_id":7,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"reply_to_user":{"id":2,"username":"b10c","name":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png"},"bookmarked":false,"raw":"Also didn’t find any of these hashes in my peer-observer debug.logs","actions_summary":[],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Also didn’t find any of these hashes in my peer-observer debug.logs","truncated":true,"post_url":"/t/introducing-the-merge-mining-monitor/146/6","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":511,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-07-02T15:08:53.956Z","cooked":"<p>I just had a look through KIT block announcement data shared by <a class=\"mention\" href=\"/u/matthias\">@matthias</a>, and none of the block hashes seem to have been announced to their monitoring nodes (which only receive INVs, not compact blocks).</p>\n<p>These are SOME(!) of the hashes of these blocks:</p>\n<pre><code class=\"lang-auto\">914329 00000000000000000002097c6c16d3e4065640c744d544d35dd797d06189a4ab\n914331 00000000000000000000439817c63926873f46ca396974268b1f9f6eae84b1c1\n914332 0000000000000000000122a9c97762f507cc57df067f07b826ab0a81cb4e787f\n914332 000000000000000000016c286d182701403f8eb2e322a844a019c933ba6082cb\n914334 0000000000000000000092003874d2b869e8b986339f5bcf8c3a03f5dddd972c\n914342 00000000000000000000ba485fa4bbba0416890572ff6b5853cdc24e92d7434f\n914344 0000000000000000000075bdcb14ab9b07e87c6c5a43addb81ff6dd74c14d16e\n914344 000000000000000000020806ba231682bab800c757366c169b2e17259a5e3aaf\n914357 0000000000000000000135a4e20e4402f5f3b5798b2d49ec9f51614feb224c93\n914360 00000000000000000001c7664aeb6f4ce7f29e3f799eb3aafb924255d6643573\n914362 0000000000000000000098d9f82cd465d4a1e55fabb659d1df2464648f796777\n914362 0000000000000000000170e712b2da3ba73fb618753fc44d0e4b6b1db3e3fc4b\n914371 000000000000000000013cad1d0d9a4d168c0b2dbae847fa8a2c3ba0704252c0\n914373 00000000000000000000a4a5644ce7e315feeeb1c586903c077993bb5f7825a2\n</code></pre>","post_number":5,"post_type":1,"posts_count":7,"updated_at":"2026-07-02T15:43:57.248Z","reply_count":1,"reply_to_post_number":4,"quote_count":0,"incoming_link_count":1,"reads":11,"readers_count":10,"score":11.8,"yours":false,"topic_id":146,"topic_slug":"introducing-the-merge-mining-monitor","topic_title":"Introducing the Merge Mining Monitor","topic_html_title":"Introducing the Merge Mining Monitor","category_id":7,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":3,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"reply_to_user":{"id":16,"username":"ajtowns","name":"Anthony Towns","avatar_template":"/user_avatar/bnoc.xyz/ajtowns/{size}/64_2.png"},"bookmarked":false,"raw":"I just had a look through KIT block announcement data shared by @matthias, and none of the block hashes seem to have been announced to their monitoring nodes (which only receive INVs, not compact blocks).\n\nThese are SOME(!) of the hashes of these blocks:\n\n```\n914329 00000000000000000002097c6c16d3e4065640c744d544d35dd797d06189a4ab\n914331 00000000000000000000439817c63926873f46ca396974268b1f9f6eae84b1c1\n914332 0000000000000000000122a9c97762f507cc57df067f07b826ab0a81cb4e787f\n914332 000000000000000000016c286d182701403f8eb2e322a844a019c933ba6082cb\n914334 0000000000000000000092003874d2b869e8b986339f5bcf8c3a03f5dddd972c\n914342 00000000000000000000ba485fa4bbba0416890572ff6b5853cdc24e92d7434f\n914344 0000000000000000000075bdcb14ab9b07e87c6c5a43addb81ff6dd74c14d16e\n914344 000000000000000000020806ba231682bab800c757366c169b2e17259a5e3aaf\n914357 0000000000000000000135a4e20e4402f5f3b5798b2d49ec9f51614feb224c93\n914360 00000000000000000001c7664aeb6f4ce7f29e3f799eb3aafb924255d6643573\n914362 0000000000000000000098d9f82cd465d4a1e55fabb659d1df2464648f796777\n914362 0000000000000000000170e712b2da3ba73fb618753fc44d0e4b6b1db3e3fc4b\n914371 000000000000000000013cad1d0d9a4d168c0b2dbae847fa8a2c3ba0704252c0\n914373 00000000000000000000a4a5644ce7e315feeeb1c586903c077993bb5f7825a2\n```","actions_summary":[],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"I just had a look through KIT block announcement data shared by <a class=\"mention\" href=\"/u/matthias\">@matthias</a>, and none of the block hashes seem to have been announced to their monitoring nodes (which only receive INVs, not compact blocks). \nThese are SOME(!) of the hashes of these blocks: \n914329 00000000000000000002097c6c16d3e406564&hellip;","truncated":true,"post_url":"/t/introducing-the-merge-mining-monitor/146/5","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":510,"name":"Anthony Towns","username":"ajtowns","avatar_template":"/user_avatar/bnoc.xyz/ajtowns/{size}/64_2.png","created_at":"2026-07-02T14:57:27.081Z","cooked":"<p>I wonder if that indicates the foundry blocks were invalid somehow – too many transactions, bad transaction ordering, an invalid transaction in a mempool, or bad math in the coinbase somewhere? That would cause block relay to fail very quickly. As an FPPS pool, presumably individual miners didn’t see an impact.</p>","post_number":4,"post_type":1,"posts_count":7,"updated_at":"2026-07-02T14:57:27.081Z","reply_count":2,"reply_to_post_number":3,"quote_count":0,"incoming_link_count":0,"reads":11,"readers_count":10,"score":26.8,"yours":false,"topic_id":146,"topic_slug":"introducing-the-merge-mining-monitor","topic_title":"Introducing the Merge Mining Monitor","topic_html_title":"Introducing the Merge Mining Monitor","category_id":7,"display_username":"Anthony Towns","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"reply_to_user":{"id":7,"username":"deadmanoz","name":"Deadmanoz","avatar_template":"/user_avatar/bnoc.xyz/deadmanoz/{size}/20_2.png"},"bookmarked":false,"raw":"I wonder if that indicates the foundry blocks were invalid somehow -- too many transactions, bad transaction ordering, an invalid transaction in a mempool, or bad math in the coinbase somewhere? That would cause block relay to fail very quickly. As an FPPS pool, presumably individual miners didn't see an impact.","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":16,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"I wonder if that indicates the foundry blocks were invalid somehow – too many transactions, bad transaction ordering, an invalid transaction in a mempool, or bad math in the coinbase somewhere? That would cause block relay to fail very quickly. As an FPPS pool, presumably individual miners didn’t se&hellip;","truncated":true,"post_url":"/t/introducing-the-merge-mining-monitor/146/4","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":509,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-07-02T13:28:23.303Z","cooked":"<p>Adding the full block and header in <a href=\"https://github.com/bitcoin-data/stale-blocks/pull/111\" class=\"inline-onebox\">Automated: add recent stale block(s) 2026-07-02 by github-actions[bot] · Pull Request #111 · bitcoin-data/stale-blocks · GitHub</a></p>","post_number":3,"post_type":1,"posts_count":8,"updated_at":"2026-07-02T13:28:23.303Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":12,"readers_count":11,"score":2.4,"yours":false,"topic_id":147,"topic_slug":"f2pool-mines-two-blocks-at-height-956337","topic_title":"F2Pool mines two blocks at height 956337","topic_html_title":"F2Pool mines two blocks at height 956337","category_id":8,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"Adding the full block and header in https://github.com/bitcoin-data/stale-blocks/pull/111","actions_summary":[],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Adding the full block and header in <a href=\"https://github.com/bitcoin-data/stale-blocks/pull/111\" class=\"inline-onebox\">Automated: add recent stale block(s) 2026-07-02 by github-actions[bot] · Pull Request #111 · bitcoin-data/stale-blocks · GitHub</a>","truncated":true,"post_url":"/t/f2pool-mines-two-blocks-at-height-956337/147/3","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":508,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-07-02T13:01:24.494Z","cooked":"<p>The blocks seem to have the same contents besides these differences in the coinbase:</p>\n<pre data-code-wrap=\"diff\"><code class=\"lang-diff\">@@ -1,14 +1,14 @@\n {\n-  \"txid\": \"5d938c39c1cd16cac8feae1eec86de553e617d96db7dadb6edde65b81cc928dc\",\n-  \"hash\": \"e70c85897226f8b74d6a266c917ec0f6c91b3e5080a5be87b15a82d0795bf525\",\n+  \"txid\": \"21256b2397fe3734de4f8295aa5259a56876c47613fa4e73033899a9fe6c9134\",\n+  \"hash\": \"7617f3be024129dd9f1d2470a61af74189e7298b3a3d5e9e881ce51e5f91b8b5\",\n   \"version\": 1,\n   \"size\": 535,\n   \"vsize\": 508,\n   \"weight\": 2032,\n-  \"locktime\": 1077898580,\n+  \"locktime\": 1079685856,\n   \"vin\": [\n     {\n-      \"coinbase\": \"03b1970e2cfabe6d6d2d5712e41100d88e6f5129bd69bcb100434f0a7554719ae21e9dea6cf55bac9310000000f09f909f092f4632506f6f6c2f64000000000000000000000000000000000000000000000000000000000000000000000005002c426e00\",\n+      \"coinbase\": \"03b1970e2cfabe6d6d2d5712e41100d88e6f5129bd69bcb100434f0a7554719ae21e9dea6cf55bac9310000000f09f909f092f4632506f6f6c2f65000000000000000000000000000000000000000000000000000000000000000000000005009d8e0e00\",\n       \"txinwitness\": [\n         \"0000000000000000000000000000000000000000000000000000000000000000\"\n       ],\n@@ -100,4 +100,3 @@\n     }\n   ]\n }\n</code></pre>\n<p>With the relevant changes from the header being:</p>\n<pre data-code-wrap=\"diff\"><code class=\"lang-diff\"> {\n-  \"hash\": \"0000000000000000000157a11e2f0d46474721b0753d076500a91695a59fea25\",\n+  \"hash\": \"000000000000000000010cb999e87c6ba72be683a24d94aefa99574a19f63f2d\",\n   \"height\": 956337,\n-  \"version\": 1073733632,\n+  \"version\": 740425728,\n-  \"versionHex\": \"3fffe000\",\n+  \"versionHex\": \"2c220000\",\n-  \"merkleroot\": \"a5fbcf14dd84e023ff9bb2e372b98dcd463730cff9d18149326a6ef8660add43\",\n+  \"merkleroot\": \"7692fe94b98a9f12c8a0b1ee0e497e46c691229fc38696d02f1891a8e8fd9cb6\",\n-  \"time\": 1782981823,\n+  \"time\": 1782981814,\n   \"mediantime\": 1782980765,\n-  \"nonce\": 1482529440,\n+  \"nonce\": 3806002134,\n   \"bits\": \"17021a42\",\n   \"target\": \"000000000000000000021a420000000000000000000000000000000000000000\",\n   \"difficulty\": 133869853540305.4,\n   \"chainwork\": \"0000000000000000000000000000000000000001348d59e5ce33ac605b33eaee\",\n   \"nTx\": 5687,\n   \"previousblockhash\": \"000000000000000000015bdb19b0b3ee0da5328aef896312feeef2119e034755\",\n   \"strippedsize\": 830080,\n   \"size\": 1507586,\n   \"weight\": 3997826,\n</code></pre>\n<p>The interesting part here is that the winning block has header timestamp `1782981823` vs `1782981814` of the loosing block. The winning block timestamp is 9s after the loosing block. Likely due to a slightly older job being worked on.</p>","post_number":2,"post_type":1,"posts_count":8,"updated_at":"2026-07-02T13:01:44.841Z","reply_count":1,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":11,"readers_count":10,"score":7.2,"yours":false,"topic_id":147,"topic_slug":"f2pool-mines-two-blocks-at-height-956337","topic_title":"F2Pool mines two blocks at height 956337","topic_html_title":"F2Pool mines two blocks at height 956337","category_id":8,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"The blocks seem to have the same contents besides these differences in the coinbase:\n\n```diff\n@@ -1,14 +1,14 @@\n {\n-  \"txid\": \"5d938c39c1cd16cac8feae1eec86de553e617d96db7dadb6edde65b81cc928dc\",\n-  \"hash\": \"e70c85897226f8b74d6a266c917ec0f6c91b3e5080a5be87b15a82d0795bf525\",\n+  \"txid\": \"21256b2397fe3734de4f8295aa5259a56876c47613fa4e73033899a9fe6c9134\",\n+  \"hash\": \"7617f3be024129dd9f1d2470a61af74189e7298b3a3d5e9e881ce51e5f91b8b5\",\n   \"version\": 1,\n   \"size\": 535,\n   \"vsize\": 508,\n   \"weight\": 2032,\n-  \"locktime\": 1077898580,\n+  \"locktime\": 1079685856,\n   \"vin\": [\n     {\n-      \"coinbase\": \"03b1970e2cfabe6d6d2d5712e41100d88e6f5129bd69bcb100434f0a7554719ae21e9dea6cf55bac9310000000f09f909f092f4632506f6f6c2f64000000000000000000000000000000000000000000000000000000000000000000000005002c426e00\",\n+      \"coinbase\": \"03b1970e2cfabe6d6d2d5712e41100d88e6f5129bd69bcb100434f0a7554719ae21e9dea6cf55bac9310000000f09f909f092f4632506f6f6c2f65000000000000000000000000000000000000000000000000000000000000000000000005009d8e0e00\",\n       \"txinwitness\": [\n         \"0000000000000000000000000000000000000000000000000000000000000000\"\n       ],\n@@ -100,4 +100,3 @@\n     }\n   ]\n }\n```\n\nWith the relevant changes from the header being:\n\n```diff\n {\n-  \"hash\": \"0000000000000000000157a11e2f0d46474721b0753d076500a91695a59fea25\",\n+  \"hash\": \"000000000000000000010cb999e87c6ba72be683a24d94aefa99574a19f63f2d\",\n   \"height\": 956337,\n-  \"version\": 1073733632,\n+  \"version\": 740425728,\n-  \"versionHex\": \"3fffe000\",\n+  \"versionHex\": \"2c220000\",\n-  \"merkleroot\": \"a5fbcf14dd84e023ff9bb2e372b98dcd463730cff9d18149326a6ef8660add43\",\n+  \"merkleroot\": \"7692fe94b98a9f12c8a0b1ee0e497e46c691229fc38696d02f1891a8e8fd9cb6\",\n-  \"time\": 1782981823,\n+  \"time\": 1782981814,\n   \"mediantime\": 1782980765,\n-  \"nonce\": 1482529440,\n+  \"nonce\": 3806002134,\n   \"bits\": \"17021a42\",\n   \"target\": \"000000000000000000021a420000000000000000000000000000000000000000\",\n   \"difficulty\": 133869853540305.4,\n   \"chainwork\": \"0000000000000000000000000000000000000001348d59e5ce33ac605b33eaee\",\n   \"nTx\": 5687,\n   \"previousblockhash\": \"000000000000000000015bdb19b0b3ee0da5328aef896312feeef2119e034755\",\n   \"strippedsize\": 830080,\n   \"size\": 1507586,\n   \"weight\": 3997826,\n```\n\nThe interesting part here is that the winning block has header timestamp \\`1782981823\\` vs \\`1782981814\\` of the loosing block. The winning block timestamp is 9s after the loosing block. Likely due to a slightly older job being worked on.","actions_summary":[],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"The blocks seem to have the same contents besides these differences in the coinbase: \n@@ -1,14 +1,14 @@\n {\n-  &quot;txid&quot;: &quot;5d938c39c1cd16cac8feae1eec86de553e617d96db7dadb6edde65b81cc928dc&quot;,\n-  &quot;hash&quot;: &quot;e70c85897226f8b74d6a266c917ec0f6c91b3e5080a5be87b15a82d0795bf525&quot;,\n+  &quot;txid&quot;: &quot;21256b2397fe3734de4f829&hellip;","truncated":true,"post_url":"/t/f2pool-mines-two-blocks-at-height-956337/147/2","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":507,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-07-02T09:50:55.121Z","cooked":"<aside class=\"quote no-group\" data-username=\"Antoine\" data-post=\"3\" data-topic=\"60\">\n<div class=\"title\">\n<div class=\"quote-controls\"></div>\n<img alt=\"\" width=\"24\" height=\"24\" src=\"https://bnoc.xyz/user_avatar/bnoc.xyz/antoine/48/36_2.png\" class=\"avatar\"> Antoine:</div>\n<blockquote>\n<p>or are we just observing this behaviour now?</p>\n</blockquote>\n</aside>\n<p>happened again for F2Pool this time: <a href=\"https://bnoc.xyz/t/f2pool-mines-two-blocks-at-height-956337/147\" class=\"inline-onebox\">F2Pool mines two blocks at height 956337</a></p>","post_number":4,"post_type":1,"posts_count":4,"updated_at":"2026-07-02T09:50:55.121Z","reply_count":0,"reply_to_post_number":3,"quote_count":1,"incoming_link_count":0,"reads":11,"readers_count":10,"score":1.8,"yours":false,"topic_id":60,"topic_slug":"antpool-mines-two-blocks-at-height-925051","topic_title":"AntPool mines two blocks at height 925051","topic_html_title":"AntPool mines two blocks at height 925051","category_id":8,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"[quote=\"Antoine, post:3, topic:60\"]\nor are we just observing this behaviour now?\n\n[/quote]\n\nhappened again for F2Pool this time: https://bnoc.xyz/t/f2pool-mines-two-blocks-at-height-956337/147","actions_summary":[],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"happened again for F2Pool this time: <a href=\"https://bnoc.xyz/t/f2pool-mines-two-blocks-at-height-956337/147\" class=\"inline-onebox\">F2Pool mines two blocks at height 956337</a>","truncated":true,"post_url":"/t/antpool-mines-two-blocks-at-height-925051/60/4","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":506,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-07-02T09:49:50.736Z","cooked":"<p>Similar to <a href=\"https://bnoc.xyz/t/antpool-mines-two-blocks-at-height-925051/60\" class=\"inline-onebox\">AntPool mines two blocks at height 925051</a> , F2Pool mined two forks at height 956337. This isn’t too special, as two ASICs or two nodes, or multiple Stratum servers aren’t unlikely. Still, it’s interesting to dive deeper into this and, if possible, compare the blocks.</p>\n<p><div class=\"lightbox-wrapper\"><a class=\"lightbox\" href=\"https://bnoc.xyz/uploads/default/original/1X/d76bb1232378f2128587969db335284c64791989.png\" data-download-href=\"https://bnoc.xyz/uploads/default/d76bb1232378f2128587969db335284c64791989\" title=\"image\"><img src=\"https://bnoc.xyz/uploads/default/optimized/1X/d76bb1232378f2128587969db335284c64791989_2_632x500.png\" alt=\"image\" data-base62-sha1=\"uJHnScK2c5yxZPrcKLbvHuBlKDT\" width=\"632\" height=\"500\" srcset=\"https://bnoc.xyz/uploads/default/optimized/1X/d76bb1232378f2128587969db335284c64791989_2_632x500.png, https://bnoc.xyz/uploads/default/original/1X/d76bb1232378f2128587969db335284c64791989.png 1.5x, https://bnoc.xyz/uploads/default/original/1X/d76bb1232378f2128587969db335284c64791989.png 2x\" data-dominant-color=\"F6F6F6\"><div class=\"meta\"><svg class=\"fa d-icon d-icon-far-image svg-icon\" aria-hidden=\"true\"><use href=\"#far-image\"></use></svg><span class=\"filename\">image</span><span class=\"informations\">854×675 56.1 KB</span><svg class=\"fa d-icon d-icon-discourse-expand svg-icon\" aria-hidden=\"true\"><use href=\"#discourse-expand\"></use></svg></div></a></div></p>","post_number":1,"post_type":1,"posts_count":8,"updated_at":"2026-07-02T09:49:50.736Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":10,"reads":13,"readers_count":12,"score":42.6,"yours":false,"topic_id":147,"topic_slug":"f2pool-mines-two-blocks-at-height-956337","topic_title":"F2Pool mines two blocks at height 956337","topic_html_title":"F2Pool mines two blocks at height 956337","category_id":8,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"Similar to https://bnoc.xyz/t/antpool-mines-two-blocks-at-height-925051/60 , F2Pool mined two forks at height 956337. This isn’t too special, as two ASICs or two nodes, or multiple Stratum servers aren’t unlikely. Still, it’s interesting to dive deeper into this and, if possible, compare the blocks.\n\n![image|632x500](upload://uJHnScK2c5yxZPrcKLbvHuBlKDT.png)","actions_summary":[],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Similar to <a href=\"https://bnoc.xyz/t/antpool-mines-two-blocks-at-height-925051/60\" class=\"inline-onebox\">AntPool mines two blocks at height 925051</a> , F2Pool mined two forks at height 956337. This isn’t too special, as two ASICs or two nodes, or multiple Stratum servers aren’t unlikely. Still, it’s interesting to dive deeper into this and, if possible, compare the blocks. \n <a class=\"lightbox\" href=\"https://bnoc.xyz/uploads/default/original/1X/d76bb1232378f2128587969db335284c64791989.png\" data-download-href=\"https://bnoc.xyz/uploads/default/d76bb1232378f2128587969db335284c64791989\" title=\"image\">[image]</a>","truncated":true,"post_url":"/t/f2pool-mines-two-blocks-at-height-956337/147/1","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null,"can_vote":false},{"id":505,"name":"Deadmanoz","username":"deadmanoz","avatar_template":"/user_avatar/bnoc.xyz/deadmanoz/{size}/20_2.png","created_at":"2026-07-02T09:03:54.083Z","cooked":"<p>Foundry produced a <em><strong>very</strong></em> high number of stale blocks on 11/12th September 2025 as recorded in the records of RSK and Fractal Bitcoin: <a href=\"https://mmm.deadmanoz.xyz/?tree_time=2025-09-18T16%3A21%3A51Z&amp;selected=00000000000000000000ba485fa4bbba0416890572ff6b5853cdc24e92d7434f\" class=\"inline-onebox\" rel=\"noopener nofollow ugc\">Merge Mining Monitor</a></p>\n<p><div class=\"lightbox-wrapper\"><a class=\"lightbox\" href=\"https://bnoc.xyz/uploads/default/original/1X/2594d025a8326d6932bf5ba582cc13b3a2c55fa3.jpeg\" data-download-href=\"https://bnoc.xyz/uploads/default/2594d025a8326d6932bf5ba582cc13b3a2c55fa3\" title=\"Screenshot 2026-07-02 at 4.22.59 pm\"><img src=\"https://bnoc.xyz/uploads/default/optimized/1X/2594d025a8326d6932bf5ba582cc13b3a2c55fa3_2_690x346.jpeg\" alt=\"Screenshot 2026-07-02 at 4.22.59 pm\" data-base62-sha1=\"5msuOgKfdk4ArZpKZsr2kcsErxV\" width=\"690\" height=\"346\" srcset=\"https://bnoc.xyz/uploads/default/optimized/1X/2594d025a8326d6932bf5ba582cc13b3a2c55fa3_2_690x346.jpeg, https://bnoc.xyz/uploads/default/optimized/1X/2594d025a8326d6932bf5ba582cc13b3a2c55fa3_2_1035x519.jpeg 1.5x, https://bnoc.xyz/uploads/default/optimized/1X/2594d025a8326d6932bf5ba582cc13b3a2c55fa3_2_1380x692.jpeg 2x\" data-dominant-color=\"2C322D\"><div class=\"meta\"><svg class=\"fa d-icon d-icon-far-image svg-icon\" aria-hidden=\"true\"><use href=\"#far-image\"></use></svg><span class=\"filename\">Screenshot 2026-07-02 at 4.22.59 pm</span><span class=\"informations\">1920×964 195 KB</span><svg class=\"fa d-icon d-icon-discourse-expand svg-icon\" aria-hidden=\"true\"><use href=\"#discourse-expand\"></use></svg></div></a></div></p>\n<p>I’ve not dug into this deeply at this stage, and this certainly warrants a deeper investigation, but the preliminary (AI-assisted) findings are:</p>\n<ul>\n<li>20 stale Foundry blocks between heights 914261 and 914373, a window of roughly 20 hours running from 2025-09-11 17:48 UTC to 2025-09-12 14:05 UTC. Every stale block in that window is Foundry’s; no other pool lost a single block.</li>\n<li>All 20 are genuine full-difficulty Bitcoin blocks. I re-verified each stored 80-byte header independently of the monitor’s classifier: the header hashes to its claimed block hash, the hash meets the header’s own nBits target, the nBits matches the canonical difficulty epoch at that height, and the prev hash points at the canonical parent.</li>\n<li>These blocks appear never to have reached the Bitcoin network. There are no ForkMonitor/fork.observer/stale-blocks stale-candidate entries near these heights, and I found no discussion of the event anywhere online. The only surviving evidence is the AuxPoW commitments captured by RSK and Fractal Bitcoin.</li>\n<li>The header timestamps support this. In a normal propagation race the competing blocks are seconds apart. Here, 18 of the 20 losing blocks carry timestamps 135 to 1621 seconds (median ~600s) <em>before</em> the canonical winner at the same height. The network wasn’t racing Foundry, it simply kept mining as though Foundry’s blocks didn’t exist. (The other 2 look like ordinary races: one 0s self-race and one 6s loss to F2Pool.)</li>\n<li>Foundry’s canonical share over the window was ~18% (20 of 113 blocks), well below the ~29% it held across the two weeks either side (592 of 2,022 blocks). Counting the stales, the network found 133 full-difficulty solutions in the window (113 canonical + 20 stale) and Foundry found 40 of them (20 + 20), i.e. 30%, right at its normal share. So the pool’s hashrate was fine; roughly half the blocks it found were silently lost. The 20 stales sit at 16 distinct heights (4 heights have two Foundry stales each, and only one block per height can win; at 914261 the winner was Foundry itself), so the incident cost the pool 15 heights it would otherwise almost certainly have won: ~46.9 BTC in foregone subsidy plus fees.</li>\n<li>Every stale builds on a canonical parent and none of them chain onto each other, which suggests the found blocks never even made it back into Foundry’s own block templates. That points at a failure in the block-submission path at the pool layer rather than a network partition.</li>\n<li>Attribution is high-confidence on two independent bases: 13 of the 20 carry the <code>Foundry USA Pool</code> tag in the Bitcoin parent coinbase embedded in Fractal’s AuxPoW proof, and the remaining 7 (RSK-only evidence) pay out to Foundry’s known RSK reward address <code>0xCe7864A8...845D4a</code>.</li>\n</ul>\n<p>The evidence is publicly and independently checkable. For example, for the selected block above (height 914342): Fractal block <a href=\"https://mempool.fractalbitcoin.io/block/3ef4d377b189f08f04d89934e8b5589812c34358f7e6da52b50f835cb0f1e249\" rel=\"noopener nofollow ugc\">1061372</a> is canonical on Fractal and commits to the stale parent, and RSK block <a href=\"https://rootstock.blockscout.com/block/0x45b485e90ea7a46f13b31e2abbac1ff0d0d576fbf9c18ee3b3d6d221e518c280\" rel=\"noopener nofollow ugc\">0x45b485e9…</a> at height 7987912, whose captured AuxPoW embeds the same parent header, is visible on Blockscout as mined by Foundry’s RSK address (that RSK block was itself reorged out, consistent with its Bitcoin parent never propagating, but Blockscout retains it as an uncle).</p>\n<p>One caveat: header timestamps are miner-set, so any single delta could be clock skew. But 18 losses in one direction averaging ~12 minutes, plus zero sightings by Bitcoin network monitors, is hard to read as anything other than ~20 hours of Foundry’s blocks intermittently failing to propagate?</p>\n<p>Regardless, an event that cost them dearly (~46.9 BTC), which could have been openly detected had this monitor been operating!</p>","post_number":3,"post_type":1,"posts_count":7,"updated_at":"2026-07-02T09:03:54.083Z","reply_count":1,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":22,"reads":11,"readers_count":10,"score":156.8,"yours":false,"topic_id":146,"topic_slug":"introducing-the-merge-mining-monitor","topic_title":"Introducing the Merge Mining Monitor","topic_html_title":"Introducing the Merge Mining Monitor","category_id":7,"display_username":"Deadmanoz","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"Foundry produced a ***very*** high number of stale blocks on 11/12th September 2025 as recorded in the records of RSK and Fractal Bitcoin: https://mmm.deadmanoz.xyz/?tree_time=2025-09-18T16%3A21%3A51Z&selected=00000000000000000000ba485fa4bbba0416890572ff6b5853cdc24e92d7434f\n\n![Screenshot 2026-07-02 at 4.22.59 pm|690x346](upload://5msuOgKfdk4ArZpKZsr2kcsErxV.jpeg)\n\nI've not dug into this deeply at this stage, and this certainly warrants a deeper investigation, but the preliminary (AI-assisted) findings are:\n\n- 20 stale Foundry blocks between heights 914261 and 914373, a window of roughly 20 hours running from 2025-09-11 17:48 UTC to 2025-09-12 14:05 UTC. Every stale block in that window is Foundry's; no other pool lost a single block.\n- All 20 are genuine full-difficulty Bitcoin blocks. I re-verified each stored 80-byte header independently of the monitor's classifier: the header hashes to its claimed block hash, the hash meets the header's own nBits target, the nBits matches the canonical difficulty epoch at that height, and the prev hash points at the canonical parent.\n- These blocks appear never to have reached the Bitcoin network. There are no ForkMonitor/fork.observer/stale-blocks stale-candidate entries near these heights, and I found no discussion of the event anywhere online. The only surviving evidence is the AuxPoW commitments captured by RSK and Fractal Bitcoin.\n- The header timestamps support this. In a normal propagation race the competing blocks are seconds apart. Here, 18 of the 20 losing blocks carry timestamps 135 to 1621 seconds (median ~600s) *before* the canonical winner at the same height. The network wasn't racing Foundry, it simply kept mining as though Foundry's blocks didn't exist. (The other 2 look like ordinary races: one 0s self-race and one 6s loss to F2Pool.)\n- Foundry's canonical share over the window was ~18% (20 of 113 blocks), well below the ~29% it held across the two weeks either side (592 of 2,022 blocks). Counting the stales, the network found 133 full-difficulty solutions in the window (113 canonical + 20 stale) and Foundry found 40 of them (20 + 20), i.e. 30%, right at its normal share. So the pool's hashrate was fine; roughly half the blocks it found were silently lost. The 20 stales sit at 16 distinct heights (4 heights have two Foundry stales each, and only one block per height can win; at 914261 the winner was Foundry itself), so the incident cost the pool 15 heights it would otherwise almost certainly have won: ~46.9 BTC in foregone subsidy plus fees.\n- Every stale builds on a canonical parent and none of them chain onto each other, which suggests the found blocks never even made it back into Foundry's own block templates. That points at a failure in the block-submission path at the pool layer rather than a network partition.\n- Attribution is high-confidence on two independent bases: 13 of the 20 carry the `Foundry USA Pool` tag in the Bitcoin parent coinbase embedded in Fractal's AuxPoW proof, and the remaining 7 (RSK-only evidence) pay out to Foundry's known RSK reward address `0xCe7864A8...845D4a`.\n\nThe evidence is publicly and independently checkable. For example, for the selected block above (height 914342): Fractal block [1061372](https://mempool.fractalbitcoin.io/block/3ef4d377b189f08f04d89934e8b5589812c34358f7e6da52b50f835cb0f1e249) is canonical on Fractal and commits to the stale parent, and RSK block [0x45b485e9...](https://rootstock.blockscout.com/block/0x45b485e90ea7a46f13b31e2abbac1ff0d0d576fbf9c18ee3b3d6d221e518c280) at height 7987912, whose captured AuxPoW embeds the same parent header, is visible on Blockscout as mined by Foundry's RSK address (that RSK block was itself reorged out, consistent with its Bitcoin parent never propagating, but Blockscout retains it as an uncle).\n\nOne caveat: header timestamps are miner-set, so any single delta could be clock skew. But 18 losses in one direction averaging ~12 minutes, plus zero sightings by Bitcoin network monitors, is hard to read as anything other than ~20 hours of Foundry's blocks intermittently failing to propagate? \n\nRegardless, an event that cost them dearly (~46.9 BTC), which could have been openly detected had this monitor been operating!","actions_summary":[{"id":2,"count":2}],"moderator":false,"admin":false,"staff":false,"user_id":7,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Foundry produced a very high number of stale blocks on 11/12th September 2025 as recorded in the records of RSK and Fractal Bitcoin: <a href=\"https://mmm.deadmanoz.xyz/?tree_time=2025-09-18T16%3A21%3A51Z&amp;selected=00000000000000000000ba485fa4bbba0416890572ff6b5853cdc24e92d7434f\" class=\"inline-onebox\" rel=\"noopener nofollow ugc\">Merge Mining Monitor</a> \n <a class=\"lightbox\" href=\"https://bnoc.xyz/uploads/default/original/1X/2594d025a8326d6932bf5ba582cc13b3a2c55fa3.jpeg\" data-download-href=\"https://bnoc.xyz/uploads/default/2594d025a8326d6932bf5ba582cc13b3a2c55fa3\" title=\"Screenshot 2026-07-02 at 4.22.59 pm\">[Screenshot 2026-07-02 at 4.22.59 pm]</a> \nI’ve not dug into this deeply at this stage, and this certainly warrants a deeper investigation, but the &hellip;","truncated":true,"post_url":"/t/introducing-the-merge-mining-monitor/146/3","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":504,"name":"Deadmanoz","username":"deadmanoz","avatar_template":"/user_avatar/bnoc.xyz/deadmanoz/{size}/20_2.png","created_at":"2026-07-02T08:16:53.288Z","cooked":"<p>Some data that may be of interest in the following comments</p>","post_number":2,"post_type":1,"posts_count":7,"updated_at":"2026-07-02T08:16:53.288Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":11,"readers_count":10,"score":1.8,"yours":false,"topic_id":146,"topic_slug":"introducing-the-merge-mining-monitor","topic_title":"Introducing the Merge Mining Monitor","topic_html_title":"Introducing the Merge Mining Monitor","category_id":7,"display_username":"Deadmanoz","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"Some data that may be of interest in the following comments","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":7,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Some data that may be of interest in the following comments","truncated":true,"post_url":"/t/introducing-the-merge-mining-monitor/146/2","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":503,"name":"Deadmanoz","username":"deadmanoz","avatar_template":"/user_avatar/bnoc.xyz/deadmanoz/{size}/20_2.png","created_at":"2026-07-02T08:12:45.844Z","cooked":"<p>Following up on my earlier thread about recovering pre-2015 Bitcoin stale blocks from merged-mined chains (<a href=\"https://bnoc.xyz/t/recovering-pre-2015-bitcoin-stale-blocks-from-merged-mined-chains-revisiting-stifter-et-al-2018/120\">here</a>), I kept pulling on that line of work and have created a new tool in service of the Bitcoin monitoring mission: the <a href=\"https://mmm.deadmanoz.xyz/\" rel=\"noopener nofollow ugc\">Merge Mining Monitor</a>.</p>\n<p>As in the original post, Stifter et al. showed that merge-mined child chains preserve the Bitcoin parent headers their miners actually hashed. That makes them a side channel into Bitcoin stale and orphan blocks, as well as a way to associate child-chain blocks with the Bitcoin parent headers they committed to.</p>\n<p>What began as a historical data recovery exercise turned into a live and historical monitor (I did things a bit backwards compared with the original plan, at least in terms of publishing the datasets etc.). The monitor reads AuxPoW evidence across six live producers, 17 recovered child-chain datasets, and ten catalogued chains where data is still missing. It then makes the resulting pool attribution, child-chain attribution, stale-block evidence, and orphan evidence explorable in a fork-observer-like tree view.</p>\n<p>The current record is 2,200+ recovered stale &amp; orphan blocks from current chain tip right back to 2011 when Namecoin started merge-mining with Bitcoin. Many of those blocks have no durable trace left on the Bitcoin network itself.</p>\n<p>Even though direct Bitcoin-network monitoring is much more mature in 2026, the value of this side channel is still apparent. For example, the monitor recovered an F2Pool stale at Bitcoin height 953,715 via RSK, around two weeks ago at time of writing, which does not appear to have propagated widely on the Bitcoin network: <a href=\"https://mmm.deadmanoz.xyz/?tree_window=generated&amp;tree_from=953699&amp;tree_to=953731&amp;tree_height=953715&amp;selected=000000000000000000009d0c8597a8b0ae9dd1e1ef16e9dd8d4a94ed7e486bc7\" rel=\"noopener nofollow ugc\">F2Pool 953715 on RSK</a>. There are many such instances, with this just being the most recent.</p>\n<p>I have plans to add more visualisations, including graphs of merge-mining breakdown over time (blocks per difficulty period for each chain, child-chain difficulty relative to Bitcoin, and so on), and better ways to show the cadence of block production across chains. Some of the facets I want to explore:</p>\n<ul>\n<li>block timestamp differentials, including whether cross-chain timing anomalies point to anything worth investigating;</li>\n<li>mining proxy relationships, including cross-checking 0xB10C’s AntPool-and-friends research from another data source;</li>\n<li>mining pool dynamics, which was the original stale-block data question that set me down this rabbit hole;</li>\n<li>notification capabilities such as RSS;</li>\n<li>auto-publishing into the foundational public dataset at <a href=\"https://github.com/bitcoin-data/stale-blocks\" rel=\"noopener nofollow ugc\">bitcoin-data/stale-blocks</a>.</li>\n</ul>\n<p>Suggestions, corrections, missing-chain leads, and other feedback very welcome!!</p>","post_number":1,"post_type":1,"posts_count":7,"updated_at":"2026-07-02T08:12:45.844Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":5,"reads":12,"readers_count":11,"score":72.0,"yours":false,"topic_id":146,"topic_slug":"introducing-the-merge-mining-monitor","topic_title":"Introducing the Merge Mining Monitor","topic_html_title":"Introducing the Merge Mining Monitor","category_id":7,"display_username":"Deadmanoz","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"Following up on my earlier thread about recovering pre-2015 Bitcoin stale blocks from merged-mined chains ([here](https://bnoc.xyz/t/recovering-pre-2015-bitcoin-stale-blocks-from-merged-mined-chains-revisiting-stifter-et-al-2018/120)), I kept pulling on that line of work and have created a new tool in service of the Bitcoin monitoring mission: the [Merge Mining Monitor](https://mmm.deadmanoz.xyz/).\n\nAs in the original post, Stifter et al. showed that merge-mined child chains preserve the Bitcoin parent headers their miners actually hashed. That makes them a side channel into Bitcoin stale and orphan blocks, as well as a way to associate child-chain blocks with the Bitcoin parent headers they committed to.\n\nWhat began as a historical data recovery exercise turned into a live and historical monitor (I did things a bit backwards compared with the original plan, at least in terms of publishing the datasets etc.). The monitor reads AuxPoW evidence across six live producers, 17 recovered child-chain datasets, and ten catalogued chains where data is still missing. It then makes the resulting pool attribution, child-chain attribution, stale-block evidence, and orphan evidence explorable in a fork-observer-like tree view.\n\nThe current record is 2,200+ recovered stale & orphan blocks from current chain tip right back to 2011 when Namecoin started merge-mining with Bitcoin. Many of those blocks have no durable trace left on the Bitcoin network itself.\n\nEven though direct Bitcoin-network monitoring is much more mature in 2026, the value of this side channel is still apparent. For example, the monitor recovered an F2Pool stale at Bitcoin height 953,715 via RSK, around two weeks ago at time of writing, which does not appear to have propagated widely on the Bitcoin network: [F2Pool 953715 on RSK](https://mmm.deadmanoz.xyz/?tree_window=generated&tree_from=953699&tree_to=953731&tree_height=953715&selected=000000000000000000009d0c8597a8b0ae9dd1e1ef16e9dd8d4a94ed7e486bc7). There are many such instances, with this just being the most recent.\n\nI have plans to add more visualisations, including graphs of merge-mining breakdown over time (blocks per difficulty period for each chain, child-chain difficulty relative to Bitcoin, and so on), and better ways to show the cadence of block production across chains. Some of the facets I want to explore:\n\n* block timestamp differentials, including whether cross-chain timing anomalies point to anything worth investigating;\n* mining proxy relationships, including cross-checking 0xB10C’s AntPool-and-friends research from another data source;\n* mining pool dynamics, which was the original stale-block data question that set me down this rabbit hole;\n* notification capabilities such as RSS;\n* auto-publishing into the foundational public dataset at [bitcoin-data/stale-blocks](https://github.com/bitcoin-data/stale-blocks).\n\nSuggestions, corrections, missing-chain leads, and other feedback very welcome!!","actions_summary":[{"id":2,"count":3}],"moderator":false,"admin":false,"staff":false,"user_id":7,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Following up on my earlier thread about recovering pre-2015 Bitcoin stale blocks from merged-mined chains (<a href=\"https://bnoc.xyz/t/recovering-pre-2015-bitcoin-stale-blocks-from-merged-mined-chains-revisiting-stifter-et-al-2018/120\">here</a>), I kept pulling on that line of work and have created a new tool in service of the Bitcoin monitoring mission: the <a href=\"https://mmm.deadmanoz.xyz/\" rel=\"noopener nofollow ugc\">Merge Mining Monitor</a>. \nAs in the original post, Stifter et al. showed th&hellip;","truncated":true,"post_url":"/t/introducing-the-merge-mining-monitor/146/1","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null,"can_vote":false},{"id":502,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-07-01T09:09:04.478Z","cooked":"<p>I’ve been thinking about adding a visualization of what-is-being-mined-on to fork-observer using stratum data: <a href=\"https://github.com/0xB10C/fork-observer/pull/137\" class=\"inline-onebox\">Show next block based on stratum jobs by 0xB10C · Pull Request #137 · 0xB10C/fork-observer · GitHub</a></p>\n<p><div class=\"lightbox-wrapper\"><a class=\"lightbox\" href=\"https://bnoc.xyz/uploads/default/original/1X/04f72a1a23694fb1f6669fb76eff02786f676a88.png\" data-download-href=\"https://bnoc.xyz/uploads/default/04f72a1a23694fb1f6669fb76eff02786f676a88\" title=\"image\"><img src=\"https://bnoc.xyz/uploads/default/optimized/1X/04f72a1a23694fb1f6669fb76eff02786f676a88_2_517x500.png\" alt=\"image\" data-base62-sha1=\"HVslQUrnx628Cs2uuWqoTGrXUA\" width=\"517\" height=\"500\" srcset=\"https://bnoc.xyz/uploads/default/optimized/1X/04f72a1a23694fb1f6669fb76eff02786f676a88_2_517x500.png, https://bnoc.xyz/uploads/default/optimized/1X/04f72a1a23694fb1f6669fb76eff02786f676a88_2_775x750.png 1.5x, https://bnoc.xyz/uploads/default/original/1X/04f72a1a23694fb1f6669fb76eff02786f676a88.png 2x\" data-dominant-color=\"FBFCFB\"><div class=\"meta\"><svg class=\"fa d-icon d-icon-far-image svg-icon\" aria-hidden=\"true\"><use href=\"#far-image\"></use></svg><span class=\"filename\">image</span><span class=\"informations\">912×881 43.8 KB</span><svg class=\"fa d-icon d-icon-discourse-expand svg-icon\" aria-hidden=\"true\"><use href=\"#discourse-expand\"></use></svg></div></a></div></p>\n<p>An idea for an activation live stream would be to show a Core and Knots+BIP110 node on fork-observer and have them both connected to a ckpool instance each, which are then connected to a stratum-observer instance. This would show which blocks the nodes consider active and which block they are mining on. Could also mix in some of the bigger pools like AntPool, F2Pool, ViaBTC, … Maybe Foundry if we can get pool details too.</p>\n<p>The same works for the eCash activation.</p>","post_number":6,"post_type":1,"posts_count":8,"updated_at":"2026-07-01T09:09:04.478Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":14,"readers_count":13,"score":32.8,"yours":false,"topic_id":139,"topic_slug":"brainstorming-what-data-to-collect-and-monitor-during-the-bip-110-bip-300-forks-in-august-2026","topic_title":"Brainstorming: What data to collect and monitor during the BIP-110 & BIP-300 forks in August 2026?","topic_html_title":"Brainstorming: What data to collect and monitor during the BIP-110 &amp; BIP-300 forks in August 2026?","category_id":5,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"I’ve been thinking about adding a visualization of what-is-being-mined-on to fork-observer using stratum data: https://github.com/0xB10C/fork-observer/pull/137 \n\n![image|517x500](upload://HVslQUrnx628Cs2uuWqoTGrXUA.png)\n\nAn idea for an activation live stream would be to show a Core and Knots+BIP110 node on fork-observer and have them both connected to a ckpool instance each, which are then connected to a stratum-observer instance. This would show which blocks the nodes consider active and which block they are mining on. Could also mix in some of the bigger pools like AntPool, F2Pool, ViaBTC, … Maybe Foundry if we can get pool details too.\n\nThe same works for the eCash activation.","actions_summary":[{"id":2,"count":2}],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"I’ve been thinking about adding a visualization of what-is-being-mined-on to fork-observer using stratum data: <a href=\"https://github.com/0xB10C/fork-observer/pull/137\" class=\"inline-onebox\">Show next block based on stratum jobs by 0xB10C · Pull Request #137 · 0xB10C/fork-observer · GitHub</a> \n <a class=\"lightbox\" href=\"https://bnoc.xyz/uploads/default/original/1X/04f72a1a23694fb1f6669fb76eff02786f676a88.png\" data-download-href=\"https://bnoc.xyz/uploads/default/04f72a1a23694fb1f6669fb76eff02786f676a88\" title=\"image\">[image]</a> \nAn idea for an activation live stream would be to show a Core and Knots+BIP110&hellip;","truncated":true,"post_url":"/t/brainstorming-what-data-to-collect-and-monitor-during-the-bip-110-bip-300-forks-in-august-2026/139/6","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":501,"name":"stratospher","username":"stratospher","avatar_template":"/user_avatar/bnoc.xyz/stratospher/{size}/134_2.png","created_at":"2026-06-29T19:45:03.147Z","cooked":"<p>tried connecting to one ip from a fully synced node (it disconnected me when I wasn’t caught to the tip). basically this just kept happening in a loop: the linode node announces transactions, we send it GETDATA, it doesn’t respond and then seeing <code>timeout of inflight tx</code> . I didn’t connect long enough to see if it does more self advertisement later.</p>","post_number":10,"post_type":1,"posts_count":10,"updated_at":"2026-06-29T19:47:53.580Z","reply_count":0,"reply_to_post_number":9,"quote_count":0,"incoming_link_count":0,"reads":11,"readers_count":10,"score":1.8,"yours":false,"topic_id":121,"topic_slug":"small-getaddr-responses-from-897-nodes-satoshi-27-0-0-on-as63949","topic_title":"Small getaddr responses from 897 nodes (/Satoshi:27.0.0/ on AS63949)","topic_html_title":"Small getaddr responses from 897 nodes (/Satoshi:27.0.0/ on AS63949)","category_id":6,"display_username":"stratospher","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"reply_to_user":{"id":43,"username":"stratospher","name":"stratospher","avatar_template":"/user_avatar/bnoc.xyz/stratospher/{size}/134_2.png"},"bookmarked":false,"raw":"tried connecting to one ip from a fully synced node (it disconnected me when I wasn't caught to the tip). basically this just kept happening in a loop: the linode node announces transactions, we send it GETDATA, it doesn't respond and then seeing `timeout of inflight tx` . I didn't connect long enough to see if it does more self advertisement later.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":43,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"tried connecting to one ip from a fully synced node (it disconnected me when I wasn’t caught to the tip). basically this just kept happening in a loop: the linode node announces transactions, we send it GETDATA, it doesn’t respond and then seeing timeout of inflight tx . I didn’t connect long enough&hellip;","truncated":true,"post_url":"/t/small-getaddr-responses-from-897-nodes-satoshi-27-0-0-on-as63949/121/10","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":500,"name":"stratospher","username":"stratospher","avatar_template":"/user_avatar/bnoc.xyz/stratospher/{size}/134_2.png","created_at":"2026-06-29T19:44:32.696Z","cooked":"<p>this is just analysing the response to GETADDR requests from the network btw. the crawler tried to find all the reachable nodes on the network and sends each of them a GETADDR request and receives the response. I just sorted the individual ADDR responses received based on the count from highest to lowest to decide the celebs.</p>\n<blockquote>\n<p>Does that mean that those nodes are doing more frequent self-advertisements than core, or something else?</p>\n</blockquote>\n<p><a class=\"mention\" href=\"/u/ajtowns\">@ajtowns</a>, I think it’s a mix of:</p>\n<ol>\n<li>the fleet controlling many IPs</li>\n<li>having made it’s way into so many address managers in the real network (and even into tried tables without running a real node (block height = 0) because this linode fleet has <code>listen=1</code> and can accept inbound connections)</li>\n</ol>\n<p>ex: 170.187.181.185 was seen in the GETADDR response of 114 members of it’s own fleet. but 301 nodes on the real network not part of this fleet also sent it in it’s GETADDR response!</p>","post_number":9,"post_type":1,"posts_count":10,"updated_at":"2026-06-29T19:50:18.025Z","reply_count":1,"reply_to_post_number":8,"quote_count":0,"incoming_link_count":0,"reads":11,"readers_count":10,"score":6.8,"yours":false,"topic_id":121,"topic_slug":"small-getaddr-responses-from-897-nodes-satoshi-27-0-0-on-as63949","topic_title":"Small getaddr responses from 897 nodes (/Satoshi:27.0.0/ on AS63949)","topic_html_title":"Small getaddr responses from 897 nodes (/Satoshi:27.0.0/ on AS63949)","category_id":6,"display_username":"stratospher","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":3,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"reply_to_user":{"id":16,"username":"ajtowns","name":"Anthony Towns","avatar_template":"/user_avatar/bnoc.xyz/ajtowns/{size}/64_2.png"},"bookmarked":false,"raw":"this is just analysing the response to GETADDR requests from the network btw. the crawler tried to find all the reachable nodes on the network and sends each of them a GETADDR request and receives the response. I just sorted the individual ADDR responses received based on the count from highest to lowest to decide the celebs.\n\n> Does that mean that those nodes are doing more frequent self-advertisements than core, or something else?\n\n@ajtowns, I think it's a mix of:\n1. the fleet controlling many IPs\n2. having made it's way into so many address managers in the real network (and even into tried tables without running a real node (block height = 0) because this linode fleet has `listen=1` and can accept inbound connections)\n\nex: 170.187.181.185 was seen in the GETADDR response of 114 members of it's own fleet. but 301 nodes on the real network not part of this fleet also sent it in it's GETADDR response!","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":43,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"this is just analysing the response to GETADDR requests from the network btw. the crawler tried to find all the reachable nodes on the network and sends each of them a GETADDR request and receives the response. I just sorted the individual ADDR responses received based on the count from highest to l&hellip;","truncated":true,"post_url":"/t/small-getaddr-responses-from-897-nodes-satoshi-27-0-0-on-as63949/121/9","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":499,"name":"Anthony Towns","username":"ajtowns","avatar_template":"/user_avatar/bnoc.xyz/ajtowns/{size}/64_2.png","created_at":"2026-06-28T16:31:42.068Z","cooked":"<aside class=\"quote no-group\" data-username=\"stratospher\" data-post=\"6\" data-topic=\"121\">\n<div class=\"title\">\n<div class=\"quote-controls\"></div>\n<img alt=\"\" width=\"24\" height=\"24\" src=\"https://bnoc.xyz/user_avatar/bnoc.xyz/stratospher/48/134_2.png\" class=\"avatar\"> stratospher:</div>\n<blockquote>\n<p>these linode nodes seem to be the IPv4 celebs - the most seen ipv4 addresses in GETADDR responses when running virtu’s crawler.</p>\n</blockquote>\n</aside>\n<p>Does that mean that those nodes are doing more frequent self-advertisements than core, or something else?</p>","post_number":8,"post_type":1,"posts_count":10,"updated_at":"2026-06-28T16:31:42.068Z","reply_count":1,"reply_to_post_number":6,"quote_count":1,"incoming_link_count":0,"reads":11,"readers_count":10,"score":21.8,"yours":false,"topic_id":121,"topic_slug":"small-getaddr-responses-from-897-nodes-satoshi-27-0-0-on-as63949","topic_title":"Small getaddr responses from 897 nodes (/Satoshi:27.0.0/ on AS63949)","topic_html_title":"Small getaddr responses from 897 nodes (/Satoshi:27.0.0/ on AS63949)","category_id":6,"display_username":"Anthony Towns","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"[quote=\"stratospher, post:6, topic:121\"]\nthese linode nodes seem to be the IPv4 celebs - the most seen ipv4 addresses in GETADDR responses when running virtu’s crawler.\n[/quote]\n\nDoes that mean that those nodes are doing more frequent self-advertisements than core, or something else?","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":16,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Does that mean that those nodes are doing more frequent self-advertisements than core, or something else?","truncated":true,"post_url":"/t/small-getaddr-responses-from-897-nodes-satoshi-27-0-0-on-as63949/121/8","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":498,"name":"Strakeljahn","username":"jorisstrakeljahn","avatar_template":"/user_avatar/bnoc.xyz/jorisstrakeljahn/{size}/275_2.png","created_at":"2026-06-25T14:24:30.849Z","cooked":"<p>Thanks, great point! New version is live:</p>\n<p>Charts now show an always-visible one-line explanation under the title, so it should be quicker to understand what you’re looking at (think that helps a lot). I also improved the mobile/touch layout so the legend no longer covers the chart.</p>","post_number":5,"post_type":1,"posts_count":5,"updated_at":"2026-06-25T14:24:47.217Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":10,"readers_count":9,"score":46.8,"yours":false,"topic_id":140,"topic_slug":"asmap-dashboard-first-version-looking-for-feedback","topic_title":"ASmap dashboard: first version, looking for feedback","topic_html_title":"ASmap dashboard: first version, looking for feedback","category_id":6,"display_username":"Strakeljahn","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"Thanks, great point! New version is live:\n\nCharts now show an always-visible one-line explanation under the title, so it should be quicker to understand what you’re looking at (think that helps a lot). I also improved the mobile/touch layout so the legend no longer covers the chart.","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":86,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Thanks, great point! New version is live: \nCharts now show an always-visible one-line explanation under the title, so it should be quicker to understand what you’re looking at (think that helps a lot). I also improved the mobile/touch layout so the legend no longer covers the chart.","truncated":true,"post_url":"/t/asmap-dashboard-first-version-looking-for-feedback/140/5","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":497,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-06-25T12:58:36.130Z","cooked":"<p>These IPs might be good candidates for <a href=\"https://github.com/bitcoin-noc/banlist\" class=\"inline-onebox\">GitHub - bitcoin-noc/banlist: An optional, centralized, and incomplete banlist containing the IP addresses of possibly malicious entities on the Bitcoin network. · GitHub</a></p>","post_number":7,"post_type":1,"posts_count":10,"updated_at":"2026-06-25T12:58:36.130Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":13,"readers_count":12,"score":17.0,"yours":false,"topic_id":121,"topic_slug":"small-getaddr-responses-from-897-nodes-satoshi-27-0-0-on-as63949","topic_title":"Small getaddr responses from 897 nodes (/Satoshi:27.0.0/ on AS63949)","topic_html_title":"Small getaddr responses from 897 nodes (/Satoshi:27.0.0/ on AS63949)","category_id":6,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"These IPs might be good candidates for https://github.com/bitcoin-noc/banlist","actions_summary":[{"id":2,"count":1}],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"These IPs might be good candidates for <a href=\"https://github.com/bitcoin-noc/banlist\" class=\"inline-onebox\">GitHub - bitcoin-noc/banlist: An optional, centralized, and incomplete banlist containing the IP addresses of possibly malicious entities on the Bitcoin network. · GitHub</a>","truncated":true,"post_url":"/t/small-getaddr-responses-from-897-nodes-satoshi-27-0-0-on-as63949/121/7","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":496,"name":"stratospher","username":"stratospher","avatar_template":"/user_avatar/bnoc.xyz/stratospher/{size}/134_2.png","created_at":"2026-06-25T11:18:52.432Z","cooked":"<p>came across <code>/Satoshi:27.0.0/</code> nodes on Linode/AS63949 as well. 2,006 IPs and half of them seem dead.</p>\n<p>all of them:</p>\n<ul>\n<li>on block height 0</li>\n<li>send exactly 256 addresses as GETADDR response. every address in the response have:\n<ul>\n<li>timestamp = now</li>\n<li>are also part of this linode cluster</li>\n</ul>\n</li>\n</ul>\n<p>they’re also in ~0.2% of the new table but ~6% of the tried table (most are ~6% but seeing 2-10% range) of different addrman snapshots in peer.observer. it didn’t exist in 2024.</p>\n<p>these linode nodes seem to be the IPv4 celebs - the most seen ipv4 addresses in GETADDR responses when running virtu’s crawler. The overall top 5000 are almost entirely onion addresses - only 9 IPv4 nodes break into that top 5000 and all 9 are from this cluster.</p>","post_number":6,"post_type":1,"posts_count":10,"updated_at":"2026-06-25T11:18:52.432Z","reply_count":2,"reply_to_post_number":5,"quote_count":0,"incoming_link_count":8,"reads":13,"readers_count":12,"score":12.0,"yours":false,"topic_id":121,"topic_slug":"small-getaddr-responses-from-897-nodes-satoshi-27-0-0-on-as63949","topic_title":"Small getaddr responses from 897 nodes (/Satoshi:27.0.0/ on AS63949)","topic_html_title":"Small getaddr responses from 897 nodes (/Satoshi:27.0.0/ on AS63949)","category_id":6,"display_username":"stratospher","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"reply_to_user":{"id":43,"username":"stratospher","name":"stratospher","avatar_template":"/user_avatar/bnoc.xyz/stratospher/{size}/134_2.png"},"bookmarked":false,"raw":"came across `/Satoshi:27.0.0/` nodes on Linode/AS63949 as well. 2,006 IPs and half of them seem dead.\n\nall of them:\n- on block height 0\n- send exactly 256 addresses as GETADDR response. every address in the response have:\n    - timestamp = now\n    - are also part of this linode cluster\n\nthey're also in ~0.2% of the new table but ~6% of the tried table (most are ~6% but seeing 2-10% range) of different addrman snapshots in peer.observer. it didn't exist in 2024.\n\nthese linode nodes seem to be the IPv4 celebs - the most seen ipv4 addresses in GETADDR responses when running virtu's crawler. The overall top 5000 are almost entirely onion addresses - only 9 IPv4 nodes break into that top 5000 and all 9 are from this cluster.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":43,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"came across /Satoshi:27.0.0/ nodes on Linode/AS63949 as well. 2,006 IPs and half of them seem dead. \nall of them: \n\non block height 0\nsend exactly 256 addresses as GETADDR response. every address in the response have:\n\ntimestamp = now\nare also part of this linode cluster\n\n\n\nthey’re also in ~0.2% of &hellip;","truncated":true,"post_url":"/t/small-getaddr-responses-from-897-nodes-satoshi-27-0-0-on-as63949/121/6","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":494,"name":"Martin Zumsande","username":"mzumsande","avatar_template":"/user_avatar/bnoc.xyz/mzumsande/{size}/11_2.png","created_at":"2026-06-24T09:06:55.807Z","cooked":"<p>It is a slow and not very reliable heuristic - we need multiple samples since connections could also fail because our addrman is old/of low quality. it would be ideal if we could detect this immediately and with a high degree of certainty during init but that doesn’t seem to be all that easy given that something like pinging hard-coded popular IPv6 addresses is probably out of the question for privacy reasons.</p>","post_number":14,"post_type":1,"posts_count":14,"updated_at":"2026-06-24T09:06:55.807Z","reply_count":0,"reply_to_post_number":13,"quote_count":0,"incoming_link_count":0,"reads":12,"readers_count":11,"score":2.0,"yours":false,"topic_id":142,"topic_slug":"outbound-connection-success-rates-of-a-bitcoin-node","topic_title":"Outbound connection success rates of a Bitcoin node","topic_html_title":"Outbound connection success rates of a Bitcoin node","category_id":6,"display_username":"Martin Zumsande","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"reply_to_user":{"id":16,"username":"ajtowns","name":"Anthony Towns","avatar_template":"/user_avatar/bnoc.xyz/ajtowns/{size}/64_2.png"},"bookmarked":false,"raw":"It is a slow and not very reliable heuristic - we need multiple samples since connections could also fail because our addrman is old/of low quality. it would be ideal if we could detect this immediately and with a high degree of certainty during init but that doesn’t seem to be all that easy given that something like pinging hard-coded popular IPv6 addresses is probably out of the question for privacy reasons.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":3,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"It is a slow and not very reliable heuristic - we need multiple samples since connections could also fail because our addrman is old/of low quality. it would be ideal if we could detect this immediately and with a high degree of certainty during init but that doesn’t seem to be all that easy given t&hellip;","truncated":true,"post_url":"/t/outbound-connection-success-rates-of-a-bitcoin-node/142/14","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":493,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-06-23T14:08:35.868Z","cooked":"<p>Similar to <a href=\"https://delvingbitcoin.org/t/public-archive-for-delving-bitcoin/87\" class=\"inline-onebox\">Public archive for Delving Bitcoin - Meta - Delving Bitcoin</a> , I’m using the <code>discourse-archive</code> tool to scrape the content here for archival.</p>\n<p>To test the archive, I’m also generating a mirror from the archive: <a href=\"https://mirror.b10c.me/bnoc-xyz/\">https://mirror.b10c.me/bnoc-xyz/</a></p>","post_number":1,"post_type":1,"posts_count":1,"updated_at":"2026-06-23T14:09:14.107Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":12,"readers_count":11,"score":32.0,"yours":false,"topic_id":144,"topic_slug":"archive-of-bnoc","topic_title":"Archive of BNOC","topic_html_title":"Archive of BNOC","category_id":2,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"Similar to https://delvingbitcoin.org/t/public-archive-for-delving-bitcoin/87 , I’m using the `discourse-archive` tool to scrape the content here for archival.\n\nTo test the archive, I’m also generating a mirror from the archive: [https://mirror.b10c.me/bnoc-xyz/](https://mirror.b10c.me/bnoc-xyz/)","actions_summary":[{"id":2,"count":2}],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Similar to <a href=\"https://delvingbitcoin.org/t/public-archive-for-delving-bitcoin/87\" class=\"inline-onebox\">Public archive for Delving Bitcoin - Meta - Delving Bitcoin</a> , I’m using the discourse-archive tool to scrape the content here for archival. \nTo test the archive, I’m also generating a mirror from the archive: <a href=\"https://mirror.b10c.me/bnoc-xyz/\">https://mirror.b10c.me/bnoc-xyz/</a>","truncated":true,"post_url":"/t/archive-of-bnoc/144/1","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null,"can_vote":false},{"id":492,"name":"Anthony Towns","username":"ajtowns","avatar_template":"/user_avatar/bnoc.xyz/ajtowns/{size}/64_2.png","created_at":"2026-06-23T01:27:19.908Z","cooked":"<p>Isn’t this already a good way of detecting if IPv6 is reachable? It means that the node will quickly start working on IPv6 if it becomes available, doesn’t rely on OS specific features or create additional code paths, and is fairly low cost.</p>","post_number":13,"post_type":1,"posts_count":14,"updated_at":"2026-06-23T01:27:19.908Z","reply_count":1,"reply_to_post_number":12,"quote_count":0,"incoming_link_count":0,"reads":13,"readers_count":12,"score":22.2,"yours":false,"topic_id":142,"topic_slug":"outbound-connection-success-rates-of-a-bitcoin-node","topic_title":"Outbound connection success rates of a Bitcoin node","topic_html_title":"Outbound connection success rates of a Bitcoin node","category_id":6,"display_username":"Anthony Towns","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"reply_to_user":{"id":3,"username":"mzumsande","name":"Martin Zumsande","avatar_template":"/user_avatar/bnoc.xyz/mzumsande/{size}/11_2.png"},"bookmarked":false,"raw":"Isn't this already a good way of detecting if IPv6 is reachable? It means that the node will quickly start working on IPv6 if it becomes available, doesn't rely on OS specific features or create additional code paths, and is fairly low cost.","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":16,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Isn’t this already a good way of detecting if IPv6 is reachable? It means that the node will quickly start working on IPv6 if it becomes available, doesn’t rely on OS specific features or create additional code paths, and is fairly low cost.","truncated":true,"post_url":"/t/outbound-connection-success-rates-of-a-bitcoin-node/142/13","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":491,"name":"Martin Zumsande","username":"mzumsande","avatar_template":"/user_avatar/bnoc.xyz/mzumsande/{size}/11_2.png","created_at":"2026-06-22T22:35:05.377Z","cooked":"<p>Many of the IPv6 connections are <a href=\"https://github.com/bitcoin/bitcoin/pull/27213\" rel=\"noopener nofollow ugc\">network-specific connections</a> that are attempted on average every 5 minutes (EXTRA_NETWORK_PEER_INTERVAL): The node views IPv6 as reachable and therefore tries in vain every 5 minutes to diversify its networks  by adding an additional IPv6 full outbound. I don’t think this is a huge problem because these attempts fail immediately and shouldn’t take up meaningful resources, but it would be nice if we could detect automatically if IPv6 is reachable.</p>","post_number":12,"post_type":1,"posts_count":14,"updated_at":"2026-06-22T22:35:27.070Z","reply_count":1,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":13,"readers_count":12,"score":12.2,"yours":false,"topic_id":142,"topic_slug":"outbound-connection-success-rates-of-a-bitcoin-node","topic_title":"Outbound connection success rates of a Bitcoin node","topic_html_title":"Outbound connection success rates of a Bitcoin node","category_id":6,"display_username":"Martin Zumsande","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"Many of the IPv6 connections are [network-specific connections](https://github.com/bitcoin/bitcoin/pull/27213) that are attempted on average every 5 minutes (EXTRA_NETWORK_PEER_INTERVAL): The node views IPv6 as reachable and therefore tries in vain every 5 minutes to diversify its networks  by adding an additional IPv6 full outbound. I don’t think this is a huge problem because these attempts fail immediately and shouldn’t take up meaningful resources, but it would be nice if we could detect automatically if IPv6 is reachable.","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":3,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Many of the IPv6 connections are <a href=\"https://github.com/bitcoin/bitcoin/pull/27213\" rel=\"noopener nofollow ugc\">network-specific connections</a> that are attempted on average every 5 minutes (EXTRA_NETWORK_PEER_INTERVAL): The node views IPv6 as reachable and therefore tries in vain every 5 minutes to diversify its networks  by adding an additional IPv6 full outbound. I don’t think&hellip;","truncated":true,"post_url":"/t/outbound-connection-success-rates-of-a-bitcoin-node/142/12","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":490,"name":"Eugene","username":"Crypt-iQ","avatar_template":"/user_avatar/bnoc.xyz/crypt-iq/{size}/177_2.png","created_at":"2026-06-22T18:00:09.292Z","cooked":"<p>Hi <a class=\"mention\" href=\"/u/b10c\">@b10c</a> I see you posted data on churn in outbound connections, but wondering if you also have data on how long outbound connections are lasting as well?</p>","post_number":11,"post_type":1,"posts_count":14,"updated_at":"2026-06-22T18:00:09.292Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":12,"readers_count":11,"score":2.0,"yours":false,"topic_id":142,"topic_slug":"outbound-connection-success-rates-of-a-bitcoin-node","topic_title":"Outbound connection success rates of a Bitcoin node","topic_html_title":"Outbound connection success rates of a Bitcoin node","category_id":6,"display_username":"Eugene","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"Hi @b10c I see you posted data on churn in outbound connections, but wondering if you also have data on how long outbound connections are lasting as well?","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":21,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Hi <a class=\"mention\" href=\"/u/b10c\">@b10c</a> I see you posted data on churn in outbound connections, but wondering if you also have data on how long outbound connections are lasting as well?","truncated":true,"post_url":"/t/outbound-connection-success-rates-of-a-bitcoin-node/142/11","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":489,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-06-22T16:48:57.130Z","cooked":"<h2><a name=\"p-489-connections-to-tor-exit-nodes-1\" class=\"anchor\" href=\"#p-489-connections-to-tor-exit-nodes-1\" aria-label=\"Heading link\"></a>connections to Tor exit nodes</h2>\n<p>When Bitcoin nodes use a Tor proxy to connect to clearnet peers (<code>node → proxy/tor exit node → clearnet peer</code>), the node might self-announce the proxy/Tor exit node address, as that’s what the peer thinks the node has.</p>\n<p>This is being changed in <a href=\"https://github.com/bitcoin/bitcoin/pull/35578\" class=\"inline-onebox\">net: don’t self advertise tor exit node ip addresses in outbound connections by stratospher · Pull Request #35578 · bitcoin/bitcoin · GitHub</a> by <a class=\"mention\" href=\"/u/stratospher\">@stratospher</a>.  For this, it’s interesting to know how many connections my node attempted (and succeeded in making) to Tor exit nodes. For this, I’m using the Tor exit node IPs since 2024-01 as archived on <a href=\"https://collector.torproject.org/archive/exit-lists/\" class=\"inline-onebox\">Index of /archive/exit-lists</a> .</p>\n<p>In mid 2026, my nodes each make between 7.5 to 12.5 connection attempts per day to Tor exit node IPs.</p>\n<p><div class=\"lightbox-wrapper\"><a class=\"lightbox\" href=\"https://bnoc.xyz/uploads/default/original/1X/d02eb5393c2b98cc62d22299c2ae7ef869050b68.jpeg\" data-download-href=\"https://bnoc.xyz/uploads/default/d02eb5393c2b98cc62d22299c2ae7ef869050b68\" title=\"Outbound connection attempts to Tor exit nodes per day (per node)\"><img src=\"https://bnoc.xyz/uploads/default/optimized/1X/d02eb5393c2b98cc62d22299c2ae7ef869050b68_2_690x369.jpeg\" alt=\"Outbound connection attempts to Tor exit nodes per day (per node)\" data-base62-sha1=\"tHFnSeJU7kTi2eUrI3kL8C4GaiQ\" width=\"690\" height=\"369\" srcset=\"https://bnoc.xyz/uploads/default/optimized/1X/d02eb5393c2b98cc62d22299c2ae7ef869050b68_2_690x369.jpeg, https://bnoc.xyz/uploads/default/optimized/1X/d02eb5393c2b98cc62d22299c2ae7ef869050b68_2_1035x553.jpeg 1.5x, https://bnoc.xyz/uploads/default/original/1X/d02eb5393c2b98cc62d22299c2ae7ef869050b68.jpeg 2x\" data-dominant-color=\"F1EFEF\"><div class=\"meta\"><svg class=\"fa d-icon d-icon-far-image svg-icon\" aria-hidden=\"true\"><use href=\"#far-image\"></use></svg><span class=\"filename\">Outbound connection attempts to Tor exit nodes per day (per node)</span><span class=\"informations\">1172×628 179 KB</span><svg class=\"fa d-icon d-icon-discourse-expand svg-icon\" aria-hidden=\"true\"><use href=\"#discourse-expand\"></use></svg></div></a></div></p>","post_number":10,"post_type":1,"posts_count":14,"updated_at":"2026-06-22T16:48:57.130Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":9,"reads":12,"readers_count":11,"score":57.0,"yours":false,"topic_id":142,"topic_slug":"outbound-connection-success-rates-of-a-bitcoin-node","topic_title":"Outbound connection success rates of a Bitcoin node","topic_html_title":"Outbound connection success rates of a Bitcoin node","category_id":6,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"## connections to Tor exit nodes\n\nWhen Bitcoin nodes use a Tor proxy to connect to clearnet peers (`node → proxy/tor exit node → clearnet peer`), the node might self-announce the proxy/Tor exit node address, as that’s what the peer thinks the node has.\n\nThis is being changed in https://github.com/bitcoin/bitcoin/pull/35578 by @stratospher.  For this, it’s interesting to know how many connections my node attempted (and succeeded in making) to Tor exit nodes. For this, I’m using the Tor exit node IPs since 2024-01 as archived on https://collector.torproject.org/archive/exit-lists/ . \n\nIn mid 2026, my nodes each make between 7.5 to 12.5 connection attempts per day to Tor exit node IPs.\n\n![Outbound connection attempts to Tor exit nodes per day (per node)|690x369](upload://tHFnSeJU7kTi2eUrI3kL8C4GaiQ.jpeg)","actions_summary":[{"id":2,"count":1}],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"<a name=\"p-489-connections-to-tor-exit-nodes-1\" class=\"anchor\" href=\"#p-489-connections-to-tor-exit-nodes-1\" aria-label=\"Heading link\"></a>connections to Tor exit nodes\nWhen Bitcoin nodes use a Tor proxy to connect to clearnet peers (node → proxy/tor exit node → clearnet peer), the node might self-announce the proxy/Tor exit node address, as that’s what the peer thinks the node has. \nThis is being changed in <a href=\"https://github.com/bitcoin/bitcoin/pull/35578\" class=\"inline-onebox\">net: don’t self advertise t&hellip;</a>","truncated":true,"post_url":"/t/outbound-connection-success-rates-of-a-bitcoin-node/142/10","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":488,"name":"stratospher","username":"stratospher","avatar_template":"/user_avatar/bnoc.xyz/stratospher/{size}/134_2.png","created_at":"2026-06-22T14:19:15.181Z","cooked":"<p>slightly related to GETADDR response size but not the same issue. was looking for GETADDR responses which were &lt;1000 addresses and came across a cluster which sent 850 - 900 addresses as GETADDR response instead of the expected 1000 addresses.</p>\n<ul>\n<li>they were all <code>/Satoshi:27.1.0/</code> in 212.132.x.x (<a href=\"http://bitnod.es/node.php?212.132.103.238\">212.132.103.238</a>, <a href=\"http://bitnod.es/node.php?212.132.126.170\">212.132.126.170</a>, <a href=\"http://bitnod.es/node.php?212.132.107.187\">212.132.107.187</a>,  <a href=\"http://bitnod.es/node.php?212.132.112.45\">212.132.112.45</a> etc..) and <a href=\"http://bitnod.es/node.php?85.215.183.240\">85.215.183.240</a></li>\n</ul>\n<p>weirdest thing about it is that it is still online and all their chain tip is stuck in 2010!</p>","post_number":5,"post_type":1,"posts_count":10,"updated_at":"2026-06-25T11:17:40.626Z","reply_count":1,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":15,"readers_count":14,"score":22.4,"yours":false,"topic_id":121,"topic_slug":"small-getaddr-responses-from-897-nodes-satoshi-27-0-0-on-as63949","topic_title":"Small getaddr responses from 897 nodes (/Satoshi:27.0.0/ on AS63949)","topic_html_title":"Small getaddr responses from 897 nodes (/Satoshi:27.0.0/ on AS63949)","category_id":6,"display_username":"stratospher","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":4,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"slightly related to GETADDR response size but not the same issue. was looking for GETADDR responses which were <1000 addresses and came across a cluster which sent 850 - 900 addresses as GETADDR response instead of the expected 1000 addresses.\n\n- they were all `/Satoshi:27.1.0/` in 212.132.x.x ([212.132.103.238](http://bitnod.es/node.php?212.132.103.238), [212.132.126.170](http://bitnod.es/node.php?212.132.126.170), [212.132.107.187](http://bitnod.es/node.php?212.132.107.187),  [212.132.112.45](http://bitnod.es/node.php?212.132.112.45) etc..) and [85.215.183.240](http://bitnod.es/node.php?85.215.183.240)\n\nweirdest thing about it is that it is still online and all their chain tip is stuck in 2010!","actions_summary":[{"id":2,"count":2}],"moderator":false,"admin":false,"staff":false,"user_id":43,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"slightly related to GETADDR response size but not the same issue. was looking for GETADDR responses which were &lt;1000 addresses and came across a cluster which sent 850 - 900 addresses as GETADDR response instead of the expected 1000 addresses. \n\nthey were all /Satoshi:27.1.0/ in 212.132.x.x (<a href=\"http://bitnod.es/node.php?212.132.103.238\">212.132&hellip;</a>","truncated":true,"post_url":"/t/small-getaddr-responses-from-897-nodes-satoshi-27-0-0-on-as63949/121/5","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":487,"name":"Sudocarlos","username":"sudocarlos","avatar_template":"/user_avatar/bnoc.xyz/sudocarlos/{size}/176_2.png","created_at":"2026-06-20T17:05:02.924Z","cooked":"<p>I’m curious to know if ASmap is behaving as intended and whether certain AS are more likely to encounter connection issues. There are probably more interesting considerations, but I’m not very creative.</p>","post_number":9,"post_type":1,"posts_count":14,"updated_at":"2026-06-20T17:05:02.924Z","reply_count":0,"reply_to_post_number":8,"quote_count":0,"incoming_link_count":0,"reads":13,"readers_count":12,"score":2.2,"yours":false,"topic_id":142,"topic_slug":"outbound-connection-success-rates-of-a-bitcoin-node","topic_title":"Outbound connection success rates of a Bitcoin node","topic_html_title":"Outbound connection success rates of a Bitcoin node","category_id":6,"display_username":"Sudocarlos","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"reply_to_user":{"id":2,"username":"b10c","name":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png"},"bookmarked":false,"raw":"I’m curious to know if ASmap is behaving as intended and whether certain AS are more likely to encounter connection issues. There are probably more interesting considerations, but I’m not very creative.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":63,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"I’m curious to know if ASmap is behaving as intended and whether certain AS are more likely to encounter connection issues. There are probably more interesting considerations, but I’m not very creative.","truncated":true,"post_url":"/t/outbound-connection-success-rates-of-a-bitcoin-node/142/9","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":486,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-06-20T14:33:01.481Z","cooked":"<p>I haven’t used any ASmap information yet for this. Anything you are curious about?</p>\n<p>I’ve seen a lot of connection attempts to <a href=\"https://ipinfo.io/AS56047\">AS56047</a> (China Mobile Communications Corporation) on different IPv4 subnets. This might be interesting to look into further. Having AS information would allow to find other Bitprojects-like entities easier in this data.</p>","post_number":8,"post_type":1,"posts_count":14,"updated_at":"2026-06-20T14:33:01.481Z","reply_count":1,"reply_to_post_number":7,"quote_count":0,"incoming_link_count":0,"reads":13,"readers_count":12,"score":7.2,"yours":false,"topic_id":142,"topic_slug":"outbound-connection-success-rates-of-a-bitcoin-node","topic_title":"Outbound connection success rates of a Bitcoin node","topic_html_title":"Outbound connection success rates of a Bitcoin node","category_id":6,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"reply_to_user":{"id":63,"username":"sudocarlos","name":"Sudocarlos","avatar_template":"/user_avatar/bnoc.xyz/sudocarlos/{size}/176_2.png"},"bookmarked":false,"raw":"I haven’t used any ASmap information yet for this. Anything you are curious about?\n\nI’ve seen a lot of connection attempts to [AS56047](https://ipinfo.io/AS56047) (China Mobile Communications Corporation) on different IPv4 subnets. This might be interesting to look into further. Having AS information would allow to find other Bitprojects-like entities easier in this data.","actions_summary":[],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"I haven’t used any ASmap information yet for this. Anything you are curious about? \nI’ve seen a lot of connection attempts to <a href=\"https://ipinfo.io/AS56047\">AS56047</a> (China Mobile Communications Corporation) on different IPv4 subnets. This might be interesting to look into further. Having AS information would allow to find other B&hellip;","truncated":true,"post_url":"/t/outbound-connection-success-rates-of-a-bitcoin-node/142/8","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":485,"name":"Sudocarlos","username":"sudocarlos","avatar_template":"/user_avatar/bnoc.xyz/sudocarlos/{size}/176_2.png","created_at":"2026-06-20T14:17:11.351Z","cooked":"<p>Are you considering any analysis based on ASmap?</p>","post_number":7,"post_type":1,"posts_count":14,"updated_at":"2026-06-20T14:17:11.351Z","reply_count":1,"reply_to_post_number":2,"quote_count":0,"incoming_link_count":0,"reads":13,"readers_count":12,"score":7.2,"yours":false,"topic_id":142,"topic_slug":"outbound-connection-success-rates-of-a-bitcoin-node","topic_title":"Outbound connection success rates of a Bitcoin node","topic_html_title":"Outbound connection success rates of a Bitcoin node","category_id":6,"display_username":"Sudocarlos","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"reply_to_user":{"id":2,"username":"b10c","name":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png"},"bookmarked":false,"raw":"Are you considering any analysis based on ASmap?","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":63,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Are you considering any analysis based on ASmap?","truncated":true,"post_url":"/t/outbound-connection-success-rates-of-a-bitcoin-node/142/7","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":483,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-06-20T08:16:54.638Z","cooked":"<p>Cool! Some feedback: A possible UX improvement could be to move parts of the ⓘ texts below the title. Currently, these charts feel optimized for recurring visitors who know what to look for and know what each chart shows (and if that’s the goal, then it’s probably fine). However, people who want to explore and learn about ASMap might have a harder time understanding the charts.</p>\n<p><div class=\"lightbox-wrapper\"><a class=\"lightbox\" href=\"https://bnoc.xyz/uploads/default/original/1X/ca1f5f9c5f35bec5d8eef364edc5c839d96353ed.png\" data-download-href=\"https://bnoc.xyz/uploads/default/ca1f5f9c5f35bec5d8eef364edc5c839d96353ed\" title=\"image\"><img src=\"https://bnoc.xyz/uploads/default/optimized/1X/ca1f5f9c5f35bec5d8eef364edc5c839d96353ed_2_690x282.png\" alt=\"image\" data-base62-sha1=\"sQ3FjE3zLJooF0BXLRIGASHjMjX\" width=\"690\" height=\"282\" srcset=\"https://bnoc.xyz/uploads/default/optimized/1X/ca1f5f9c5f35bec5d8eef364edc5c839d96353ed_2_690x282.png, https://bnoc.xyz/uploads/default/optimized/1X/ca1f5f9c5f35bec5d8eef364edc5c839d96353ed_2_1035x423.png 1.5x, https://bnoc.xyz/uploads/default/optimized/1X/ca1f5f9c5f35bec5d8eef364edc5c839d96353ed_2_1380x564.png 2x\" data-dominant-color=\"F7F7F9\"><div class=\"meta\"><svg class=\"fa d-icon d-icon-far-image svg-icon\" aria-hidden=\"true\"><use href=\"#far-image\"></use></svg><span class=\"filename\">image</span><span class=\"informations\">2382×974 314 KB</span><svg class=\"fa d-icon d-icon-discourse-expand svg-icon\" aria-hidden=\"true\"><use href=\"#discourse-expand\"></use></svg></div></a></div></p>\n<p>Having a one-line description of what the chart shows and then more information below might better for “new“ visitors. Maybe something like this:</p>\n<p><div class=\"lightbox-wrapper\"><a class=\"lightbox\" href=\"https://bnoc.xyz/uploads/default/original/1X/fdaab8ac88bb415127c04b64f90d5e67fe6e31d7.png\" data-download-href=\"https://bnoc.xyz/uploads/default/fdaab8ac88bb415127c04b64f90d5e67fe6e31d7\" title=\"image\"><img src=\"https://bnoc.xyz/uploads/default/optimized/1X/fdaab8ac88bb415127c04b64f90d5e67fe6e31d7_2_690x308.png\" alt=\"image\" data-base62-sha1=\"Ac2zgQzAbJNFS4mo1hX0XLOOuov\" width=\"690\" height=\"308\" srcset=\"https://bnoc.xyz/uploads/default/optimized/1X/fdaab8ac88bb415127c04b64f90d5e67fe6e31d7_2_690x308.png, https://bnoc.xyz/uploads/default/optimized/1X/fdaab8ac88bb415127c04b64f90d5e67fe6e31d7_2_1035x462.png 1.5x, https://bnoc.xyz/uploads/default/optimized/1X/fdaab8ac88bb415127c04b64f90d5e67fe6e31d7_2_1380x616.png 2x\" data-dominant-color=\"FBFCFC\"><div class=\"meta\"><svg class=\"fa d-icon d-icon-far-image svg-icon\" aria-hidden=\"true\"><use href=\"#far-image\"></use></svg><span class=\"filename\">image</span><span class=\"informations\">1988×888 70.5 KB</span><svg class=\"fa d-icon d-icon-discourse-expand svg-icon\" aria-hidden=\"true\"><use href=\"#discourse-expand\"></use></svg></div></a></div></p>\n<p>Where the extra information is presented in a</p>\n<details>\n<summary>\nAbout the decay curve</summary>\n<p>Lorem ipsum</p>\n</details>\n<p>If it’s not too much text, it makes sense to always show it.</p>","post_number":4,"post_type":1,"posts_count":5,"updated_at":"2026-06-20T08:16:54.638Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":14,"readers_count":13,"score":32.6,"yours":false,"topic_id":140,"topic_slug":"asmap-dashboard-first-version-looking-for-feedback","topic_title":"ASmap dashboard: first version, looking for feedback","topic_html_title":"ASmap dashboard: first version, looking for feedback","category_id":6,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"Cool! Some feedback: A possible UX improvement could be to move parts of the ⓘ texts below the title. Currently, these charts feel optimized for recurring visitors who know what to look for and know what each chart shows (and if that’s the goal, then it’s probably fine). However, people who want to explore and learn about ASMap might have a harder time understanding the charts. \n\n![image|690x282](upload://sQ3FjE3zLJooF0BXLRIGASHjMjX.png)\n\nHaving a one-line description of what the chart shows and then more information below might better for “new“ visitors. Maybe something like this:\n\n![image|690x308](upload://Ac2zgQzAbJNFS4mo1hX0XLOOuov.png)\n\nWhere the extra information is presented in a \n\n[details=\"About the decay curve\"]\nLorem ipsum\n\n[/details]\n\nIf it’s not too much text, it makes sense to always show it.","actions_summary":[{"id":2,"count":2}],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Cool! Some feedback: A possible UX improvement could be to move parts of the ⓘ texts below the title. Currently, these charts feel optimized for recurring visitors who know what to look for and know what each chart shows (and if that’s the goal, then it’s probably fine). However, people who want to &hellip;","truncated":true,"post_url":"/t/asmap-dashboard-first-version-looking-for-feedback/140/4","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":482,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-06-19T15:32:34.019Z","cooked":"<aside class=\"quote no-group\" data-username=\"b10c\" data-post=\"4\" data-topic=\"45\">\n<div class=\"title\">\n<div class=\"quote-controls\"></div>\n<img alt=\"\" width=\"24\" height=\"24\" src=\"https://bnoc.xyz/user_avatar/bnoc.xyz/b10c/48/4_2.png\" class=\"avatar\"> b10c:</div>\n<blockquote>\n<p>edit: this post mentioned 23.100.246.0/24, but that’s not bitprojects! It should have been 123.100.246.0/24!</p>\n</blockquote>\n</aside>\n<p>For completeness, these are the 12x /24 IPv4 subnets that were owned by bitprojects until late March 2026:</p>\n<ul>\n<li>45.40.98.0/24</li>\n<li>103.47.56.0/24</li>\n<li>173.46.87.0/24</li>\n<li>206.206.109.0/24</li>\n<li>189.106.27.0/24</li>\n<li>174.140.231.0/24</li>\n<li>84.174.95.0/24</li>\n<li>216.107.135.0/24</li>\n<li>66.163.223.0/24</li>\n<li>103.246.186.0/24</li>\n<li>123.100.246.0/24</li>\n<li>203.11.72.0/24</li>\n</ul>","post_number":11,"post_type":1,"posts_count":11,"updated_at":"2026-07-03T15:07:09.737Z","reply_count":0,"reply_to_post_number":4,"quote_count":1,"incoming_link_count":10,"reads":15,"readers_count":14,"score":52.8,"yours":false,"topic_id":45,"topic_slug":"increase-in-the-number-of-reachable-ipv4-nodes-bitprojects-io","topic_title":"Increase in the number of reachable IPv4 nodes (bitprojects.io)","topic_html_title":"Increase in the number of reachable IPv4 nodes (bitprojects.io)","category_id":6,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":2,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"[quote=\"b10c, post:4, topic:45\"]\nedit: this post mentioned 23.100.246.0/24, but that’s not bitprojects! It should have been 123.100.246.0/24!\n\n[/quote]\n\nFor completeness, these are the 12x /24 IPv4 subnets that were owned by bitprojects until late March 2026:\n\n* 45.40.98.0/24\n* 103.47.56.0/24\n* 173.46.87.0/24\n* 206.206.109.0/24\n* 189.106.27.0/24\n* 174.140.231.0/24\n* 84.174.95.0/24\n* 216.107.135.0/24\n* 66.163.223.0/24\n* 103.246.186.0/24\n* 123.100.246.0/24\n* 203.11.72.0/24","actions_summary":[{"id":2,"count":2}],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"For completeness, these are the 12x /24 IPv4 subnets that were owned by bitprojects until late March 2026: \n\n45.40.98.0/24\n103.47.56.0/24\n173.46.87.0/24\n206.206.109.0/24\n189.106.27.0/24\n174.140.231.0/24\n84.174.95.0/24\n216.107.135.0/24\n66.163.223.0/24\n103.246.186.0/24\n123.100.246.0/24\n203.11.72.0/24\n&hellip;","truncated":true,"post_url":"/t/increase-in-the-number-of-reachable-ipv4-nodes-bitprojects-io/45/11","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":481,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-06-18T15:49:02.593Z","cooked":"<h2><a name=\"p-481-connections-with-v2-transport-1\" class=\"anchor\" href=\"#p-481-connections-with-v2-transport-1\" aria-label=\"Heading link\"></a>connections with v2 transport</h2>\n<p>Bitcoin Core v26.0 (released November 2023) introduced experimental support for BIP324 v2 transport, but it was off by default and had to be enabled manually using the <code>-v2transport</code> option. It was enabled by default in Bitcoin Core v27.0, which was released in April 2024. In June 2026, more than 80% of the outbound connection attempts my nodes make are to v2 nodes.</p>\n<p><div class=\"lightbox-wrapper\"><a class=\"lightbox\" href=\"https://bnoc.xyz/uploads/default/original/1X/c3c3ed56dcb73ae854d2baa445058c0bbf562bcc.png\" data-download-href=\"https://bnoc.xyz/uploads/default/c3c3ed56dcb73ae854d2baa445058c0bbf562bcc\" title=\"image\"><img src=\"https://bnoc.xyz/uploads/default/optimized/1X/c3c3ed56dcb73ae854d2baa445058c0bbf562bcc_2_690x366.png\" alt=\"image\" data-base62-sha1=\"rVOStryWe1lxJoqLUyuQT4z77XK\" width=\"690\" height=\"366\" srcset=\"https://bnoc.xyz/uploads/default/optimized/1X/c3c3ed56dcb73ae854d2baa445058c0bbf562bcc_2_690x366.png, https://bnoc.xyz/uploads/default/optimized/1X/c3c3ed56dcb73ae854d2baa445058c0bbf562bcc_2_1035x549.png 1.5x, https://bnoc.xyz/uploads/default/original/1X/c3c3ed56dcb73ae854d2baa445058c0bbf562bcc.png 2x\" data-dominant-color=\"F6F3F5\"><div class=\"meta\"><svg class=\"fa d-icon d-icon-far-image svg-icon\" aria-hidden=\"true\"><use href=\"#far-image\"></use></svg><span class=\"filename\">image</span><span class=\"informations\">1182×628 119 KB</span><svg class=\"fa d-icon d-icon-discourse-expand svg-icon\" aria-hidden=\"true\"><use href=\"#discourse-expand\"></use></svg></div></a></div></p>\n<p>It can happen, that we try to make a v2 connection to a node which does not support v2 transport. For example, when we store an address with the service flag `NODE_P2P_V2` set in our address manager, because we received it this way through address gossip. We’ll attempt a v2 connection, but downgrade to v1 if we can connect, but can not establish a v2 connection.</p>\n<p>My nodes downgrade from v2 → v1 transport for about 30 to 40 connections per day. Depending on node, they have between 200 and 400 successful connection attempts per day. This means, we have a v2 → downgrade rate somewhere between 15% and 20%. Most of these seem to be feeler connections. This is expected, as we’re using information from the new table for feelers. In the tried table, we’ve updated potential service flag mismatches after a first connection.</p>\n<p><div class=\"lightbox-wrapper\"><a class=\"lightbox\" href=\"https://bnoc.xyz/uploads/default/original/1X/34b83bcbb791d874efbc970637c3955f6c9ab423.jpeg\" data-download-href=\"https://bnoc.xyz/uploads/default/34b83bcbb791d874efbc970637c3955f6c9ab423\" title=\"image\"><img src=\"https://bnoc.xyz/uploads/default/optimized/1X/34b83bcbb791d874efbc970637c3955f6c9ab423_2_690x374.jpeg\" alt=\"image\" data-base62-sha1=\"7wnxUYZqZZ9OM6hVQkutfg1tENZ\" width=\"690\" height=\"374\" srcset=\"https://bnoc.xyz/uploads/default/optimized/1X/34b83bcbb791d874efbc970637c3955f6c9ab423_2_690x374.jpeg, https://bnoc.xyz/uploads/default/optimized/1X/34b83bcbb791d874efbc970637c3955f6c9ab423_2_1035x561.jpeg 1.5x, https://bnoc.xyz/uploads/default/original/1X/34b83bcbb791d874efbc970637c3955f6c9ab423.jpeg 2x\" data-dominant-color=\"F5F2F3\"><div class=\"meta\"><svg class=\"fa d-icon d-icon-far-image svg-icon\" aria-hidden=\"true\"><use href=\"#far-image\"></use></svg><span class=\"filename\">image</span><span class=\"informations\">1158×628 148 KB</span><svg class=\"fa d-icon d-icon-discourse-expand svg-icon\" aria-hidden=\"true\"><use href=\"#discourse-expand\"></use></svg></div></a></div></p>","post_number":6,"post_type":1,"posts_count":14,"updated_at":"2026-06-20T14:02:00.961Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":13,"readers_count":12,"score":2.4,"yours":false,"topic_id":142,"topic_slug":"outbound-connection-success-rates-of-a-bitcoin-node","topic_title":"Outbound connection success rates of a Bitcoin node","topic_html_title":"Outbound connection success rates of a Bitcoin node","category_id":6,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":2,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"## connections with v2 transport\n\nBitcoin Core v26.0 (released November 2023) introduced experimental support for BIP324 v2 transport, but it was off by default and had to be enabled manually using the `-v2transport` option. It was enabled by default in Bitcoin Core v27.0, which was released in April 2024. In June 2026, more than 80% of the outbound connection attempts my nodes make are to v2 nodes.\n\n![image|690x366](upload://rVOStryWe1lxJoqLUyuQT4z77XK.png)\n\nIt can happen, that we try to make a v2 connection to a node which does not support v2 transport. For example, when we store an address with the service flag \\`NODE_P2P_V2\\` set in our address manager, because we received it this way through address gossip. We’ll attempt a v2 connection, but downgrade to v1 if we can connect, but can not establish a v2 connection.\n\nMy nodes downgrade from v2 → v1 transport for about 30 to 40 connections per day. Depending on node, they have between 200 and 400 successful connection attempts per day. This means, we have a v2 → downgrade rate somewhere between 15% and 20%. Most of these seem to be feeler connections. This is expected, as we’re using information from the new table for feelers. In the tried table, we’ve updated potential service flag mismatches after a first connection.\n\n![image|690x374](upload://7wnxUYZqZZ9OM6hVQkutfg1tENZ.jpeg)","actions_summary":[],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"<a name=\"p-481-connections-with-v2-transport-1\" class=\"anchor\" href=\"#p-481-connections-with-v2-transport-1\" aria-label=\"Heading link\"></a>connections with v2 transport\nBitcoin Core v26.0 (released November 2023) introduced experimental support for BIP324 v2 transport, but it was off by default and had to be enabled manually using the -v2transport option. It was enabled by default in Bitcoin Core v27.0, which was released in April 2024&hellip;","truncated":true,"post_url":"/t/outbound-connection-success-rates-of-a-bitcoin-node/142/6","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":480,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-06-18T15:47:48.454Z","cooked":"<p>For the simulation, it’s also important to know how frequently connections to Bitprojects ( <a href=\"https://bnoc.xyz/t/many-connections-to-bitproject-io-nodes/40/19\" class=\"inline-onebox\">Many connections to bitproject.io nodes? - #19 by b10c</a> ) were attempted and how often they succeeded. If, for example, all attempted connections to Bitprojects succeeded, then we can assume that once we picked a Bitprojects address from our address manager, we also made a connection to it.</p>\n<p>In the final months before it was shut down, Bitprojects was using 12x /24 IPv4 ranges with each of these 3072 IPs having some kind of reachable Bitcoin node behind it. My nodes first started making connections to it in mid July 2024. This grew to about 0.75 outbound connections per hour per node in April 2025. In October 2025, this started to increase and by January 2026, some of my nodes were making 2 outbound connections per hour to Bitprojects IPs. But how many of these connections were successful?</p>\n<p><div class=\"lightbox-wrapper\"><a class=\"lightbox\" href=\"https://bnoc.xyz/uploads/default/original/1X/a90b89cbba2fbf8aa5524aa90435fb655195f189.png\" data-download-href=\"https://bnoc.xyz/uploads/default/a90b89cbba2fbf8aa5524aa90435fb655195f189\" title=\"Outbound connection attempts to Bitporjects per hour (per node)\"><img src=\"https://bnoc.xyz/uploads/default/optimized/1X/a90b89cbba2fbf8aa5524aa90435fb655195f189_2_690x372.png\" alt=\"Outbound connection attempts to Bitporjects per hour (per node)\" data-base62-sha1=\"o7rpC36MjrbnsARy9Hxe47qmwFb\" width=\"690\" height=\"372\" srcset=\"https://bnoc.xyz/uploads/default/optimized/1X/a90b89cbba2fbf8aa5524aa90435fb655195f189_2_690x372.png, https://bnoc.xyz/uploads/default/optimized/1X/a90b89cbba2fbf8aa5524aa90435fb655195f189_2_1035x558.png 1.5x, https://bnoc.xyz/uploads/default/original/1X/a90b89cbba2fbf8aa5524aa90435fb655195f189.png 2x\" data-dominant-color=\"F8F6F7\"><div class=\"meta\"><svg class=\"fa d-icon d-icon-far-image svg-icon\" aria-hidden=\"true\"><use href=\"#far-image\"></use></svg><span class=\"filename\">Outbound connection attempts to Bitporjects per hour (per node)</span><span class=\"informations\">1163×628 132 KB</span><svg class=\"fa d-icon d-icon-discourse-expand svg-icon\" aria-hidden=\"true\"><use href=\"#discourse-expand\"></use></svg></div></a></div></p>\n<p>When Bitprojects initially started in mid 2024, connectivity to it wasn’t good. Until early 2025, usually less than half of the connections my nodes attempted to Bitprojects succeeded. This changed in early 2025. Then, nearly all connections succeeded. There still was some downtime here and there, but for many of my nodes, there were multiple weeks with high success rates. Around October 2025, connectivity dropped nearly completely, which is likely related to the clock misconfiguration Antoine discusses in <a href=\"https://antoinep.com/posts/misbehaving_nodes/\" class=\"inline-onebox\">Antoine Poinsot - Misbehaving nodes investigation</a> and the Bitprojects maintainer pausing and then re-enabling the nodes. From then on, connectivity remained very high until the nodes were stopped at the end of March 2026.</p>\n<p><div class=\"lightbox-wrapper\"><a class=\"lightbox\" href=\"https://bnoc.xyz/uploads/default/original/1X/bfc2d9a79e6ed10c9cb89cca2a7d7a493e4dc6a4.png\" data-download-href=\"https://bnoc.xyz/uploads/default/bfc2d9a79e6ed10c9cb89cca2a7d7a493e4dc6a4\" title=\"Success rate of connections to Bitprojects IPs\"><img src=\"https://bnoc.xyz/uploads/default/optimized/1X/bfc2d9a79e6ed10c9cb89cca2a7d7a493e4dc6a4_2_690x276.png\" alt=\"Success rate of connections to Bitprojects IPs\" data-base62-sha1=\"rmoF0RfoJ3Sifn1mBToT4shNOT2\" width=\"690\" height=\"276\" srcset=\"https://bnoc.xyz/uploads/default/optimized/1X/bfc2d9a79e6ed10c9cb89cca2a7d7a493e4dc6a4_2_690x276.png, https://bnoc.xyz/uploads/default/optimized/1X/bfc2d9a79e6ed10c9cb89cca2a7d7a493e4dc6a4_2_1035x414.png 1.5x, https://bnoc.xyz/uploads/default/original/1X/bfc2d9a79e6ed10c9cb89cca2a7d7a493e4dc6a4.png 2x\" data-dominant-color=\"F5F3F4\"><div class=\"meta\"><svg class=\"fa d-icon d-icon-far-image svg-icon\" aria-hidden=\"true\"><use href=\"#far-image\"></use></svg><span class=\"filename\">Success rate of connections to Bitprojects IPs</span><span class=\"informations\">1182×474 125 KB</span><svg class=\"fa d-icon d-icon-discourse-expand svg-icon\" aria-hidden=\"true\"><use href=\"#discourse-expand\"></use></svg></div></a></div></p>\n<p>While Bitprojects used 12x /24 IPv4 subnets at the end, they started with the first /24 in mind July 2024. In October, November, and December 2024, they added three more /24’s. In October 2025, they added eight more /24’s.</p>\n<p><div class=\"lightbox-wrapper\"><a class=\"lightbox\" href=\"https://bnoc.xyz/uploads/default/original/1X/4c82b9a33954a5fa482244360922ec7c8af63524.png\" data-download-href=\"https://bnoc.xyz/uploads/default/4c82b9a33954a5fa482244360922ec7c8af63524\" title=\"image\"><img src=\"https://bnoc.xyz/uploads/default/optimized/1X/4c82b9a33954a5fa482244360922ec7c8af63524_2_690x280.png\" alt=\"image\" data-base62-sha1=\"aUQmDp3Sbx7UNPxgoXlEfRwRYjy\" width=\"690\" height=\"280\" srcset=\"https://bnoc.xyz/uploads/default/optimized/1X/4c82b9a33954a5fa482244360922ec7c8af63524_2_690x280.png, https://bnoc.xyz/uploads/default/optimized/1X/4c82b9a33954a5fa482244360922ec7c8af63524_2_1035x420.png 1.5x, https://bnoc.xyz/uploads/default/original/1X/4c82b9a33954a5fa482244360922ec7c8af63524.png 2x\" data-dominant-color=\"F5F4F4\"><div class=\"meta\"><svg class=\"fa d-icon d-icon-far-image svg-icon\" aria-hidden=\"true\"><use href=\"#far-image\"></use></svg><span class=\"filename\">image</span><span class=\"informations\">1168×474 112 KB</span><svg class=\"fa d-icon d-icon-discourse-expand svg-icon\" aria-hidden=\"true\"><use href=\"#discourse-expand\"></use></svg></div></a></div></p>","post_number":5,"post_type":1,"posts_count":14,"updated_at":"2026-06-20T08:35:41.258Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":9,"reads":14,"readers_count":13,"score":42.6,"yours":false,"topic_id":142,"topic_slug":"outbound-connection-success-rates-of-a-bitcoin-node","topic_title":"Outbound connection success rates of a Bitcoin node","topic_html_title":"Outbound connection success rates of a Bitcoin node","category_id":6,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":5,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"For the simulation, it’s also important to know how frequently connections to Bitprojects ( https://bnoc.xyz/t/many-connections-to-bitproject-io-nodes/40/19 ) were attempted and how often they succeeded. If, for example, all attempted connections to Bitprojects succeeded, then we can assume that once we picked a Bitprojects address from our address manager, we also made a connection to it.\n\nIn the final months before it was shut down, Bitprojects was using 12x /24 IPv4 ranges with each of these 3072 IPs having some kind of reachable Bitcoin node behind it. My nodes first started making connections to it in mid July 2024. This grew to about 0.75 outbound connections per hour per node in April 2025. In October 2025, this started to increase and by January 2026, some of my nodes were making 2 outbound connections per hour to Bitprojects IPs. But how many of these connections were successful?\n\n![Outbound connection attempts to Bitporjects per hour (per node)|690x372](upload://o7rpC36MjrbnsARy9Hxe47qmwFb.png)\n\nWhen Bitprojects initially started in mid 2024, connectivity to it wasn’t good. Until early 2025, usually less than half of the connections my nodes attempted to Bitprojects succeeded. This changed in early 2025. Then, nearly all connections succeeded. There still was some downtime here and there, but for many of my nodes, there were multiple weeks with high success rates. Around October 2025, connectivity dropped nearly completely, which is likely related to the clock misconfiguration Antoine discusses in https://antoinep.com/posts/misbehaving_nodes/ and the Bitprojects maintainer pausing and then re-enabling the nodes. From then on, connectivity remained very high until the nodes were stopped at the end of March 2026.\n\n![Success rate of connections to Bitprojects IPs|690x276](upload://rmoF0RfoJ3Sifn1mBToT4shNOT2.png)\n\nWhile Bitprojects used 12x /24 IPv4 subnets at the end, they started with the first /24 in mind July 2024. In October, November, and December 2024, they added three more /24’s. In October 2025, they added eight more /24’s.\n\n![image|690x280](upload://aUQmDp3Sbx7UNPxgoXlEfRwRYjy.png)","actions_summary":[{"id":2,"count":1}],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"For the simulation, it’s also important to know how frequently connections to Bitprojects ( <a href=\"https://bnoc.xyz/t/many-connections-to-bitproject-io-nodes/40/19\" class=\"inline-onebox\">Many connections to bitproject.io nodes? - #19 by b10c</a> ) were attempted and how often they succeeded. If, for example, all attempted connections to Bitprojects succeeded, then we can assume that once we picke&hellip;","truncated":true,"post_url":"/t/outbound-connection-success-rates-of-a-bitcoin-node/142/5","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":479,"name":"b10c","username":"b10c","avatar_template":"/user_avatar/bnoc.xyz/b10c/{size}/4_2.png","created_at":"2026-06-18T15:47:36.319Z","cooked":"<p>For the <a href=\"https://github.com/bitcoin/bitcoin/issues/34019#issuecomment-4422039561\">simulation</a>, we are primarily looking for a realistic success rate of IPv4 and IPv6 connections. This allows us to simulate a node picking an address, “attempting” a connection to it, and then either succeeding or failing. When we fail, we “attempt“ another connection. Additionally, we want a success rate that ignores feelers, as feelers are only made to connections from the addrman new table (addresses we’ve never tried before). These are expected to be worse than connections to the tried table (addresses we’ve tried before).</p>\n<aside class=\"onebox githubblob\" data-onebox-src=\"https://github.com/bitcoin/bitcoin/blob/8598ec220450b05eff03fc1d1c81f51269cca247/src/net.cpp#L2863-L2864\">\n  <header class=\"source\">\n\n      <a href=\"https://github.com/bitcoin/bitcoin/blob/8598ec220450b05eff03fc1d1c81f51269cca247/src/net.cpp#L2863-L2864\" target=\"_blank\" rel=\"noopener\">github.com/bitcoin/bitcoin</a>\n  </header>\n\n  <article class=\"onebox-body\">\n    <h4><a href=\"https://github.com/bitcoin/bitcoin/blob/8598ec220450b05eff03fc1d1c81f51269cca247/src/net.cpp#L2863-L2864\" target=\"_blank\" rel=\"noopener\">src/net.cpp</a></h4>\n\n<div class=\"git-blob-info\">\n  <a href=\"https://github.com/bitcoin/bitcoin/blob/8598ec220450b05eff03fc1d1c81f51269cca247/src/net.cpp#L2863-L2864\" rel=\"noopener\"><code>8598ec220</code></a>\n</div>\n\n\n\n    <pre class=\"onebox\"><code class=\"lang-cpp\">\n      <ol class=\"start lines\" start=\"2863\" style=\"counter-reset: li-counter 2862 ;\">\n          <li>// Select a new table address for our feeler instead.</li>\n          <li>std::tie(addr, addr_last_try) = addrman.get().Select(true, reachable_nets);</li>\n      </ol>\n    </code></pre>\n\n\n\n  </article>\n\n  <div class=\"onebox-metadata\">\n    \n    \n  </div>\n\n  <div style=\"clear: both\"></div>\n</aside>\n\n<p>For IPv4, we have this data from node Alice, which generally seems to perform very similar to the other nodes:</p>\n<aside class=\"quote no-group\" data-username=\"b10c\" data-post=\"3\" data-topic=\"142\">\n<div class=\"title\">\n<div class=\"quote-controls\"></div>\n<img alt=\"\" width=\"24\" height=\"24\" src=\"https://bnoc.xyz/user_avatar/bnoc.xyz/b10c/48/4_2.png\" class=\"avatar\"> b10c:</div>\n<blockquote>\n<h3>By network and connection type</h3>\n<p>Looking at, for example, the success rate of alice’s IPv4 connections, shows that both block-relay-only and outbound-full-relay connections share the same ~25% percent success rate.</p>\n</blockquote>\n</aside>\n<p>We can probably get close to reality assuming a 25% connection attempt success rate for IPv4.</p>\n<p>However, we don’t have the same data for IPv6 yet. Node jade is not running with <a href=\"https://github.com/bitcoin/bitcoin/commit/67696b207f370e902c8d5fb765e4ff10f6c9e1b4\" class=\"inline-onebox\">net: extend log message to include attempted connection type · bitcoin/bitcoin@67696b2 · GitHub</a> and I don’t have historical data on it yet. Given that:</p>\n<aside class=\"quote no-group quote-modified\" data-username=\"b10c\" data-post=\"3\" data-topic=\"142\">\n<div class=\"title\">\n<div class=\"quote-controls\"></div>\n<img alt=\"\" width=\"24\" height=\"24\" src=\"https://bnoc.xyz/user_avatar/bnoc.xyz/b10c/48/4_2.png\" class=\"avatar\"> b10c:</div>\n<blockquote>\n<p>Only <code>jade</code> makes connections to IPv6. There, we have connection success rate just above 20%.</p>\n</blockquote>\n</aside>\n<p>matches the numbers for IPv4:</p>\n<aside class=\"quote no-group\" data-username=\"b10c\" data-post=\"3\" data-topic=\"142\">\n<div class=\"title\">\n<div class=\"quote-controls\"></div>\n<img alt=\"\" width=\"24\" height=\"24\" src=\"https://bnoc.xyz/user_avatar/bnoc.xyz/b10c/48/4_2.png\" class=\"avatar\"> b10c:</div>\n<blockquote>\n<p>All nodes can make connections via IPv4. Between 2025-01 and 2025-03-31, the nodes averaged at about a 20% (or slightly more) connection success rate.</p>\n</blockquote>\n</aside>\n<p>we could assume a 25% success rate for IPv6 non-feeler connections too.</p>","post_number":4,"post_type":1,"posts_count":14,"updated_at":"2026-06-18T17:52:54.118Z","reply_count":0,"reply_to_post_number":null,"quote_count":1,"incoming_link_count":10,"reads":15,"readers_count":14,"score":52.8,"yours":false,"topic_id":142,"topic_slug":"outbound-connection-success-rates-of-a-bitcoin-node","topic_title":"Outbound connection success rates of a Bitcoin node","topic_html_title":"Outbound connection success rates of a Bitcoin node","category_id":6,"display_username":"b10c","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":5,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"For the [simulation](https://github.com/bitcoin/bitcoin/issues/34019#issuecomment-4422039561), we are primarily looking for a realistic success rate of IPv4 and IPv6 connections. This allows us to simulate a node picking an address, “attempting” a connection to it, and then either succeeding or failing. When we fail, we “attempt“ another connection. Additionally, we want a success rate that ignores feelers, as feelers are only made to connections from the addrman new table (addresses we’ve never tried before). These are expected to be worse than connections to the tried table (addresses we’ve tried before).\n\nhttps://github.com/bitcoin/bitcoin/blob/8598ec220450b05eff03fc1d1c81f51269cca247/src/net.cpp#L2863-L2864\n\nFor IPv4, we have this data from node Alice, which generally seems to perform very similar to the other nodes:\n\n[quote=\"b10c, post:3, topic:142\"]\n### By network and connection type\n\nLooking at, for example, the success rate of alice’s IPv4 connections, shows that both block-relay-only and outbound-full-relay connections share the same \\~25% percent success rate.\n\n[/quote]\n\nWe can probably get close to reality assuming a 25% connection attempt success rate for IPv4.\n\nHowever, we don’t have the same data for IPv6 yet. Node jade is not running with https://github.com/bitcoin/bitcoin/commit/67696b207f370e902c8d5fb765e4ff10f6c9e1b4 and I don’t have historical data on it yet. Given that:\n\n[quote=\"b10c, post:3, topic:142\"]\nOnly `jade` makes connections to IPv6. There, we have connection success rate just above 20%.\n\n[/quote]\n\nmatches the numbers for IPv4:\n\n[quote=\"b10c, post:3, topic:142\"]\nAll nodes can make connections via IPv4. Between 2025-01 and 2025-03-31, the nodes averaged at about a 20% (or slightly more) connection success rate.\n\n[/quote]\n\nwe could assume a 25% success rate for IPv6 non-feeler connections too.","actions_summary":[],"moderator":true,"admin":false,"staff":true,"user_id":2,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"For the <a href=\"https://github.com/bitcoin/bitcoin/issues/34019#issuecomment-4422039561\">simulation</a>, we are primarily looking for a realistic success rate of IPv4 and IPv6 connections. This allows us to simulate a node picking an address, “attempting” a connection to it, and then either succeeding or failing. When we fail, we “attempt“ another connection. Additionally, we want a&hellip;","truncated":true,"post_url":"/t/outbound-connection-success-rates-of-a-bitcoin-node/142/4","can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null}]}