deploy: 032ddc5

Author: adamjonas

bitcoin-core-dev-tech/2025-10/asmap/index.html

@@ -6,7 +6,7 @@ Peerman and CConnman are currently interacting quite a bit, because we provide c
 code and logic that is specific to bitcoin p2p code low-level sockets stuff. Sockets and P2P code is intermixed The newly proposed SockMan class idea is to isolate the sockets logic inside CConnman, and give it a nice interface. CConnman is too big and too hard to reason about.</description></item><item><title>net - net_processing split</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/net-net_processing-split/</link><pubDate>Thu, 23 Oct 2025 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/net-net_processing-split/</guid><description>Net Processing Refactor Discussion (transcript #1)
 Overview This discussion covers two refactoring proposals for Bitcoin Core&amp;rsquo;s peer-to-peer networking layer:
 Sockman refactor: Isolating socket management from peer connection logic CNode-to-Peer refactor: Separating peer state management from connection management Part 1: The Sockman Refactor Current Architecture Issues CConnman contains mixed responsibilities:
-Bitcoin P2P network-specific logic Low-level socket operations Callback interfaces to PeerMan &amp;ldquo;Kitchen sink&amp;rdquo; of accumulated code Problem: Socket management and network logic are tightly coupled, making the code difficult to test, reason about, and reuse.</description></item><item><title>Subject matter experts and working groups</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/smes-and-wgs/</link><pubDate>Thu, 23 Oct 2025 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/smes-and-wgs/</guid><description>What is maintenance? Different from just merge access and not just done by maintainers. It takes a village GitHub admin and moderation Continuous integration Releases and release process, backports, translations, GUIX, website (checkout the release-notes file) Security, disclosures, advisories Perceived “tech leads” in different areas of the codebase How are maintainers added? Avoid public nominations or popularity contests Anonymous nominations Maintainers review list and nominate on IRC Public IRC discussion Frequent contributors Not much wrt permissions.</description></item><item><title>ASMap</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/asmap/</link><pubDate>Wed, 22 Oct 2025 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/asmap/</guid><description>Kartograf - is a tool that gets data from resources and builds the map (it’s a deterministic process and depends on RPKI) Asmap-data is a repository where the maps are stored (we usually do collaborative launches) - a timestamp is specified to do the launch. It’s required everyone to start at the same exact time. People post the results (hash) and we check if the hashes have matched. We expected 5 people (at least) attending and we expect a majority of people with same results.</description></item><item><title>CMake</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/cmake/</link><pubDate>Wed, 22 Oct 2025 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/cmake/</guid><description>Overview This presentation discusses CMake fundamentals and its future direction, brought into the context of Bitcoin Core. The speaker notes not to expect too many best practices, as these have been discussed before. Best practices for Bitcoin are not best practices for many other projects.
+Bitcoin P2P network-specific logic Low-level socket operations Callback interfaces to PeerMan &amp;ldquo;Kitchen sink&amp;rdquo; of accumulated code Problem: Socket management and network logic are tightly coupled, making the code difficult to test, reason about, and reuse.</description></item><item><title>Subject matter experts and working groups</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/smes-and-wgs/</link><pubDate>Thu, 23 Oct 2025 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/smes-and-wgs/</guid><description>What is maintenance? Different from just merge access and not just done by maintainers. It takes a village GitHub admin and moderation Continuous integration Releases and release process, backports, translations, GUIX, website (checkout the release-notes file) Security, disclosures, advisories Perceived “tech leads” in different areas of the codebase How are maintainers added? Avoid public nominations or popularity contests Anonymous nominations Maintainers review list and nominate on IRC Public IRC discussion Frequent contributors Not much wrt permissions.</description></item><item><title>ASMap</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/asmap/</link><pubDate>Wed, 22 Oct 2025 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/asmap/</guid><description>Kartograf - is a tool that gets data from resources and builds the map (it’s a deterministic process and depends on RPKI repositories, RIR IRR DBs and BGP announcements from Routeviews as inputs). RPKI data is fetched using rpki-client. Asmap-data is a repository where the maps are stored (we usually do collaborative launches) - a timestamp is specified to do the launch. It’s required everyone to start at the same exact time.</description></item><item><title>CMake</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/cmake/</link><pubDate>Wed, 22 Oct 2025 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/cmake/</guid><description>Overview This presentation discusses CMake fundamentals and its future direction, brought into the context of Bitcoin Core. The speaker notes not to expect too many best practices, as these have been discussed before. Best practices for Bitcoin are not best practices for many other projects.
 The goal is to explain what CMake is and what direction it should go in the future, to help understand the full scope of what it can be used for and to show some things that can change, because best practices evolve over time.</description></item><item><title>Package Relay</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/package-relay/</link><pubDate>Wed, 22 Oct 2025 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/package-relay/</guid><description>Tracking issue: we have come very far
 Idea was that after cluster mempool, you would be able to do arbitrary packages
 There are branches to do arbitrary package validation, but imperfect

bitcoin-core-dev-tech/2025-10/index.xml

@@ -1,2 +1,2 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>asmap on ₿itcoin Transcripts</title><link>https://btctranscripts.com/tags/asmap/</link><description>Recent content in asmap on ₿itcoin Transcripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Wed, 22 Oct 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://btctranscripts.com/tags/asmap/index.xml" rel="self" type="application/rss+xml"/><item><title>ASMap</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/asmap/</link><pubDate>Wed, 22 Oct 2025 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/asmap/</guid><description>Kartograf - is a tool that gets data from resources and builds the map (it’s a deterministic process and depends on RPKI) Asmap-data is a repository where the maps are stored (we usually do collaborative launches) - a timestamp is specified to do the launch. It’s required everyone to start at the same exact time. People post the results (hash) and we check if the hashes have matched. We expected 5 people (at least) attending and we expect a majority of people with same results.</description></item><item><title>PR Review Club</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2025-02/asmap/</link><pubDate>Fri, 28 Feb 2025 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2025-02/asmap/</guid><description>Scribe 1: PR 23792: is the only PR that&amp;rsquo;s left for ASMAP (needs cmake changes first) - hope to get this into v30.0
+<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>asmap on ₿itcoin Transcripts</title><link>https://btctranscripts.com/tags/asmap/</link><description>Recent content in asmap on ₿itcoin Transcripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Wed, 22 Oct 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://btctranscripts.com/tags/asmap/index.xml" rel="self" type="application/rss+xml"/><item><title>ASMap</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/asmap/</link><pubDate>Wed, 22 Oct 2025 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/asmap/</guid><description>Kartograf - is a tool that gets data from resources and builds the map (it’s a deterministic process and depends on RPKI repositories, RIR IRR DBs and BGP announcements from Routeviews as inputs). RPKI data is fetched using rpki-client. Asmap-data is a repository where the maps are stored (we usually do collaborative launches) - a timestamp is specified to do the launch. It’s required everyone to start at the same exact time.</description></item><item><title>PR Review Club</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2025-02/asmap/</link><pubDate>Fri, 28 Feb 2025 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2025-02/asmap/</guid><description>Scribe 1: PR 23792: is the only PR that&amp;rsquo;s left for ASMAP (needs cmake changes first) - hope to get this into v30.0
 How does ASMAP ends up in a Asmap file? Kartograph tool, based on rpki-client-nix () use tool from bitcoin Core encode and compress it multiple people will run the Kartograph tool How often should you refresh it? using an old one should be better than /16 but using a fresh asmap is better quality drops off slowly, probably five years or so.</description></item></channel></rss>

index.json

@@ -13,7 +13,7 @@ Peerman and CConnman are currently interacting quite a bit, because we provide c
 code and logic that is specific to bitcoin p2p code low-level sockets stuff. Sockets and P2P code is intermixed The newly proposed SockMan class idea is to isolate the sockets logic inside CConnman, and give it a nice interface. CConnman is too big and too hard to reason about.</description></item><item><title>net - net_processing split</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/net-net_processing-split/</link><pubDate>Thu, 23 Oct 2025 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/net-net_processing-split/</guid><description>Net Processing Refactor Discussion (transcript #1)
 Overview This discussion covers two refactoring proposals for Bitcoin Core&amp;rsquo;s peer-to-peer networking layer:
 Sockman refactor: Isolating socket management from peer connection logic CNode-to-Peer refactor: Separating peer state management from connection management Part 1: The Sockman Refactor Current Architecture Issues CConnman contains mixed responsibilities:
-Bitcoin P2P network-specific logic Low-level socket operations Callback interfaces to PeerMan &amp;ldquo;Kitchen sink&amp;rdquo; of accumulated code Problem: Socket management and network logic are tightly coupled, making the code difficult to test, reason about, and reuse.</description></item><item><title>Subject matter experts and working groups</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/smes-and-wgs/</link><pubDate>Thu, 23 Oct 2025 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/smes-and-wgs/</guid><description>What is maintenance? Different from just merge access and not just done by maintainers. It takes a village GitHub admin and moderation Continuous integration Releases and release process, backports, translations, GUIX, website (checkout the release-notes file) Security, disclosures, advisories Perceived “tech leads” in different areas of the codebase How are maintainers added? Avoid public nominations or popularity contests Anonymous nominations Maintainers review list and nominate on IRC Public IRC discussion Frequent contributors Not much wrt permissions.</description></item><item><title>ASMap</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/asmap/</link><pubDate>Wed, 22 Oct 2025 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/asmap/</guid><description>Kartograf - is a tool that gets data from resources and builds the map (it’s a deterministic process and depends on RPKI) Asmap-data is a repository where the maps are stored (we usually do collaborative launches) - a timestamp is specified to do the launch. It’s required everyone to start at the same exact time. People post the results (hash) and we check if the hashes have matched. We expected 5 people (at least) attending and we expect a majority of people with same results.</description></item><item><title>CMake</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/cmake/</link><pubDate>Wed, 22 Oct 2025 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/cmake/</guid><description>Overview This presentation discusses CMake fundamentals and its future direction, brought into the context of Bitcoin Core. The speaker notes not to expect too many best practices, as these have been discussed before. Best practices for Bitcoin are not best practices for many other projects.
+Bitcoin P2P network-specific logic Low-level socket operations Callback interfaces to PeerMan &amp;ldquo;Kitchen sink&amp;rdquo; of accumulated code Problem: Socket management and network logic are tightly coupled, making the code difficult to test, reason about, and reuse.</description></item><item><title>Subject matter experts and working groups</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/smes-and-wgs/</link><pubDate>Thu, 23 Oct 2025 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/smes-and-wgs/</guid><description>What is maintenance? Different from just merge access and not just done by maintainers. It takes a village GitHub admin and moderation Continuous integration Releases and release process, backports, translations, GUIX, website (checkout the release-notes file) Security, disclosures, advisories Perceived “tech leads” in different areas of the codebase How are maintainers added? Avoid public nominations or popularity contests Anonymous nominations Maintainers review list and nominate on IRC Public IRC discussion Frequent contributors Not much wrt permissions.</description></item><item><title>ASMap</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/asmap/</link><pubDate>Wed, 22 Oct 2025 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/asmap/</guid><description>Kartograf - is a tool that gets data from resources and builds the map (it’s a deterministic process and depends on RPKI repositories, RIR IRR DBs and BGP announcements from Routeviews as inputs). RPKI data is fetched using rpki-client. Asmap-data is a repository where the maps are stored (we usually do collaborative launches) - a timestamp is specified to do the launch. It’s required everyone to start at the same exact time.</description></item><item><title>CMake</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/cmake/</link><pubDate>Wed, 22 Oct 2025 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/cmake/</guid><description>Overview This presentation discusses CMake fundamentals and its future direction, brought into the context of Bitcoin Core. The speaker notes not to expect too many best practices, as these have been discussed before. Best practices for Bitcoin are not best practices for many other projects.
 The goal is to explain what CMake is and what direction it should go in the future, to help understand the full scope of what it can be used for and to show some things that can change, because best practices evolve over time.</description></item><item><title>Package Relay</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/package-relay/</link><pubDate>Wed, 22 Oct 2025 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/package-relay/</guid><description>Tracking issue: we have come very far
 Idea was that after cluster mempool, you would be able to do arbitrary packages
 There are branches to do arbitrary package validation, but imperfect