<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="//bitdevsamsterdam.org/feed.xml" rel="self" type="application/atom+xml" /><link href="//bitdevsamsterdam.org/" rel="alternate" type="text/html" /><updated>2026-03-31T07:49:07+00:00</updated><id>//bitdevsamsterdam.org/feed.xml</id><title type="html">BitDevs Amsterdam</title><subtitle>BitDevs is a community for those interested in discussing and participating in the research and development of Bitcoin and related protocols.</subtitle><entry><title type="html">BitDevs Rotterdam, June 4, 2026</title><link href="//bitdevsamsterdam.org/2026-06-04-june-bitdevs-rotterdam" rel="alternate" type="text/html" title="BitDevs Rotterdam, June 4, 2026" /><published>2026-06-04T00:00:00+00:00</published><updated>2026-06-04T00:00:00+00:00</updated><id>//bitdevsamsterdam.org/june-bitdevs-rotterdam</id><content type="html" xml:base="//bitdevsamsterdam.org/2026-06-04-june-bitdevs-rotterdam"><![CDATA[<h2 id="bitdevs-rotterdam-meeting-029">BitDevs Rotterdam meeting 029!</h2>

<p>It’s time for another BitDevs! A big thanks to <a href="https://www.blockrise.com/nl">Blockrise</a> for sponsoring us with the meeting space. Drinks will be provided, so please ensure you have some dinner beforehand or bring it along to the seminar.</p>

<h3 id="thursday-june-4th-2026--7pm">Thursday, June 4th, 2026 @ 7PM</h3>

<p>Doors open at 6:30PM and we will try to start promptly at 7PM. As a reminder, the ground rules of BitDevs are as follows:</p>

<ol>
  <li>No photos, videos, or recordings.</li>
  <li><a href="https://en.wikipedia.org/wiki/Chatham_House_Rule">Chatham House Rule</a>: you may
reiterate the contents of the meeting <em>without</em> attribution.</li>
</ol>

<p>These rules exist so that BitDevs participants can speak freely within the event.</p>

<h3 id="agenda">Agenda</h3>

<p>TBA</p>]]></content><author><name></name></author><summary type="html"><![CDATA[BitDevs Rotterdam meeting 029!]]></summary></entry><entry><title type="html">BitDevs Amsterdam, May 7th, 2026</title><link href="//bitdevsamsterdam.org/2026-05-07-may-bitdevs-amsterdam" rel="alternate" type="text/html" title="BitDevs Amsterdam, May 7th, 2026" /><published>2026-05-07T00:00:00+00:00</published><updated>2026-05-07T00:00:00+00:00</updated><id>//bitdevsamsterdam.org/may-bitdevs-amsterdam</id><content type="html" xml:base="//bitdevsamsterdam.org/2026-05-07-may-bitdevs-amsterdam"><![CDATA[<h2 id="bitdevs-amsterdam-meeting-028">BitDevs Amsterdam meeting 028!</h2>

<p>It’s time for another BitDevs! A big thanks to <a href="https://www.bitonic.nl">Bitonic</a> for sponsoring us with the meeting space. Drinks will be provided, so please ensure you have some dinner beforehand or bring it along to the seminar.</p>

<h3 id="thursday-may-7th-2026--7pm">Thursday, May 7th, 2026 @ 7PM</h3>

<p>Doors open at 6:30PM and we will try to start promptly at 7PM. As a reminder, the ground rules of BitDevs are as follows:</p>

<ol>
  <li>No photos, videos, or recordings.</li>
  <li><a href="https://en.wikipedia.org/wiki/Chatham_House_Rule">Chatham House Rule</a>: you may
reiterate the contents of the meeting <em>without</em> attribution.</li>
</ol>

<p>These rules exist so that BitDevs participants can speak freely within the event.</p>

<h3 id="agenda">Agenda</h3>

<p>TBA</p>]]></content><author><name></name></author><summary type="html"><![CDATA[BitDevs Amsterdam meeting 028!]]></summary></entry><entry><title type="html">BitDevs Rotterdam, April 2, 2026</title><link href="//bitdevsamsterdam.org/2026-04-02-april-bitdevs-rotterdam" rel="alternate" type="text/html" title="BitDevs Rotterdam, April 2, 2026" /><published>2026-04-02T00:00:00+00:00</published><updated>2026-04-02T00:00:00+00:00</updated><id>//bitdevsamsterdam.org/april-bitdevs-rotterdam</id><content type="html" xml:base="//bitdevsamsterdam.org/2026-04-02-april-bitdevs-rotterdam"><![CDATA[<h2 id="bitdevs-rotterdam-meeting-027">BitDevs Rotterdam meeting 027!</h2>

<p>It’s time for another BitDevs! A big thanks to <a href="https://www.blockrise.com/nl">Blockrise</a> for sponsoring us with the meeting space. Drinks will be provided, so please ensure you have some dinner beforehand or bring it along to the seminar.</p>

<h3 id="thursday-april-2nd-2026--7pm">Thursday, April 2nd, 2026 @ 7PM</h3>

<p>Doors open at 6:30PM and we will try to start promptly at 7PM. As a reminder, the ground rules of BitDevs are as follows:</p>

<ol>
  <li>No photos, videos, or recordings.</li>
  <li><a href="https://en.wikipedia.org/wiki/Chatham_House_Rule">Chatham House Rule</a>: you may
reiterate the contents of the meeting <em>without</em> attribution.</li>
</ol>

<p>These rules exist so that BitDevs participants can speak freely within the event.</p>

<h3 id="agenda">Agenda</h3>

<ul>
  <li><strong>Disposing of dust attack UTXOs</strong>: A proposed method for wallet users to dispose of “dust attack” UTXOs, small amounts sent by adversaries to reveal wallet ownership patterns, by creating transactions that use the entire amount for fees with an OP_RETURN output.
    <ul>
      <li><a href="https://delvingbitcoin.org/t/disposing-of-dust-attack-utxos/2215">https://delvingbitcoin.org/t/disposing-of-dust-attack-utxos/2215</a></li>
    </ul>
  </li>
  <li><strong>BIP 54 (Consensus Cleanup) active on Bitcoin Inquisition</strong>: BIP 54 is now active on Bitcoin Inquisition, a specialized Bitcoin Core fork used for testing proposed protocol changes. It includes fixes for known consensus bugs such as Timewarp/Murch-Zawy timestamp attacks, long block validation times from excessive legacy signature operations, the 64-byte transaction Merkle tree weakness, and coinbase transaction duplication.
    <ul>
      <li><a href="https://groups.google.com/g/bitcoindev/c/wOVjJoLDWfA">https://groups.google.com/g/bitcoindev/c/wOVjJoLDWfA</a></li>
    </ul>
  </li>
  <li><strong>Hourglass V2 update</strong>: An update on the Hourglass protocol (V2), a proposed soft fork designed to mitigate the economic damage from potential quantum attacks on lost Bitcoin. It would restrict how quickly vulnerable P2PK funds can be spent to prevent a mass market liquidation event if a quantum adversary gains the ability to derive private keys from exposed public keys.
    <ul>
      <li><a href="https://groups.google.com/g/bitcoindev/c/0E1UyyQIUA0">https://groups.google.com/g/bitcoindev/c/0E1UyyQIUA0</a></li>
    </ul>
  </li>
  <li><strong>BIP 360: Pay to Merkle Root (P2MR)</strong>: A new BIP specifying “Pay to Merkle Root,” a transaction output format designed to enhance Bitcoin’s scripting capabilities. The proposal was merged in February 2026 as a Draft specification.
    <ul>
      <li><a href="https://github.com/bitcoin/bips/pull/1670">https://github.com/bitcoin/bips/pull/1670</a></li>
    </ul>
  </li>
  <li><strong>BIP 392: Silent Payment Output Script Descriptors</strong>: Introduces a new output descriptor format for Silent Payments (BIP352), proposing <code class="language-plaintext highlighter-rouge">sp()</code> script expressions with <code class="language-plaintext highlighter-rouge">spscan</code> and <code class="language-plaintext highlighter-rouge">spspend</code> key expressions, allowing wallets to represent and manage silent payment keys using a standardized descriptor format.
    <ul>
      <li><a href="https://github.com/bitcoin/bips/pull/2047">https://github.com/bitcoin/bips/pull/2047</a></li>
    </ul>
  </li>
  <li><strong>Two-block reorg at height 941880</strong>: A mining event where Foundry mined two consecutive blocks, causing a reorganization that displaced blocks from AntPool and ViaBTC. Analysis suggests network latency and block propagation timing as contributing factors.
    <ul>
      <li><a href="https://bnoc.xyz/t/two-block-reorg-at-height-941880/97">https://bnoc.xyz/t/two-block-reorg-at-height-941880/97</a></li>
    </ul>
  </li>
  <li><strong>Fuzzor: continuous fuzzing infrastructure</strong>: Experimental continuous fuzzing infrastructure primarily designed to test Bitcoin Core, supporting multiple fuzzing engines (AFL++, libFuzzer, honggfuzz) with automated bug detection, crash deduplication, and coverage analysis.
    <ul>
      <li><a href="https://github.com/dergoegge/fuzzor">https://github.com/dergoegge/fuzzor</a></li>
    </ul>
  </li>
  <li><strong>Want to submit a discussion topic?</strong> Open an issue or PR at <a href="https://github.com/bitdevsamsterdam/bitdevsamsterdam.github.io">https://github.com/bitdevsamsterdam/bitdevsamsterdam.github.io</a></li>
</ul>]]></content><author><name></name></author><summary type="html"><![CDATA[BitDevs Rotterdam meeting 027!]]></summary></entry><entry><title type="html">BitDevs Amsterdam, March 5th, 2026</title><link href="//bitdevsamsterdam.org/2026-03-05-march-bitdevs-amsterdam" rel="alternate" type="text/html" title="BitDevs Amsterdam, March 5th, 2026" /><published>2026-03-05T00:00:00+00:00</published><updated>2026-03-05T00:00:00+00:00</updated><id>//bitdevsamsterdam.org/march-bitdevs-amsterdam</id><content type="html" xml:base="//bitdevsamsterdam.org/2026-03-05-march-bitdevs-amsterdam"><![CDATA[<h2 id="bitdevs-amsterdam-meeting-026">BitDevs Amsterdam meeting 026!</h2>

<p>It’s time for another BitDevs! A big thanks to <a href="https://www.bitonic.nl">Bitonic</a> for sponsoring us with the meeting space. Drinks will be provided, so please ensure you have some dinner beforehand or bring it along to the seminar.</p>

<h3 id="thursday-march-5th-2026--7pm">Thursday, March 5th, 2026 @ 7PM</h3>

<p>Doors open at 6:30PM and we will try to start promptly at 7PM. As a reminder, the ground rules of BitDevs are as follows:</p>

<ol>
  <li>No photos, videos, or recordings.</li>
  <li><a href="https://en.wikipedia.org/wiki/Chatham_House_Rule">Chatham House Rule</a>: you may
reiterate the contents of the meeting <em>without</em> attribution.</li>
</ol>

<p>These rules exist so that BitDevs participants can speak freely within the event.</p>

<h3 id="agenda">Agenda</h3>

<ul>
  <li><strong>hArk (hash-lock-Ark)</strong>: A major Ark protocol evolution that eliminates synchronous interactivity during rounds. Instead of requiring all participants to be online simultaneously to sign transactions, the server generates unique secrets for each VTXO, allowing participants to claim their funds asynchronously.
    <ul>
      <li><a href="https://x.com/2ndbtc/status/2015401100355002626">https://x.com/2ndbtc/status/2015401100355002626</a></li>
    </ul>
  </li>
  <li><strong>ZK Statechains</strong>: Replaces traditional statechain ledgers with zero-knowledge proofs to validate ownership transfers of Bitcoin UTXOs while maintaining privacy, combining statechain exit mechanics with a “ZK Ledger” that proves key changes and timelock decrements.
    <ul>
      <li><a href="https://delvingbitcoin.org/t/zk-statechains-without-states/2166">https://delvingbitcoin.org/t/zk-statechains-without-states/2166</a></li>
    </ul>
  </li>
  <li><strong>Taproot Quantum Spend Paths</strong>: Proposes a quantum-safe version of Taproot that allows Bitcoin addresses to have multiple spending paths (both quantum-resistant and quantum-vulnerable), letting users continue benefiting from smaller, efficient signatures until quantum computers become a genuine threat.
    <ul>
      <li><a href="https://www.bitmex.com/blog/Taproot-Quantum-Spend-Paths">https://www.bitmex.com/blog/Taproot-Quantum-Spend-Paths</a></li>
    </ul>
  </li>
  <li><strong>Lightning Network surpassed $1B in monthly volume</strong>
    <ul>
      <li><a href="https://x.com/SDWouters/status/2024507942708351443">https://x.com/SDWouters/status/2024507942708351443</a></li>
      <li><a href="https://river.com/content/bitcoin-adoption-2026">River: Bitcoin Adoption 2026</a> — Bitcoin adoption is accelerating across institutional, business, and individual segments, with the Lightning Network reaching $1 billion in monthly volume and 194 public companies now holding bitcoin on their balance sheets.</li>
    </ul>
  </li>
  <li><strong>L402 Apps</strong>: A directory and marketplace for Lightning Network-powered applications and APIs that enable micropayments in Bitcoin. Discover apps that accept L402 payments and call verified Lightning-paywalled API endpoints priced in satoshis.
    <ul>
      <li><a href="https://www.l402apps.com/">https://www.l402apps.com/</a></li>
    </ul>
  </li>
  <li><strong>BIP352 update</strong>: Proposes adding a limit specifying that the number of taproot outputs in a transaction must fit within an unsigned 32-bit integer for silent payments scanning, improving clarity for implementations choosing compatible data types.
    <ul>
      <li><a href="https://github.com/bitcoin/bips/pull/2055">https://github.com/bitcoin/bips/pull/2055</a></li>
    </ul>
  </li>
  <li><strong>sedited added to trusted-keys</strong>: Adds sedited to Bitcoin Core’s trusted-keys file, granting cryptographic signing authority for the release process.
    <ul>
      <li><a href="https://github.com/bitcoin/bitcoin/pull/34236">https://github.com/bitcoin/bitcoin/pull/34236</a></li>
    </ul>
  </li>
  <li><strong>Incremental mutation testing in Bitcoin Core</strong>: Applies mutation testing selectively and progressively by focusing only on code changes since the last analysis, dramatically reducing execution time while maintaining the ability to assess whether tests effectively detect introduced bugs.
    <ul>
      <li><a href="https://delvingbitcoin.org/t/incremental-mutation-testing-in-the-bitcoin-core/2197">https://delvingbitcoin.org/t/incremental-mutation-testing-in-the-bitcoin-core/2197</a></li>
    </ul>
  </li>
  <li><strong>Binohash: Transaction Introspection Without Softforks</strong>: A collision-resistant hash function for Bitcoin Script that enables limited transaction introspection without consensus changes.
    <ul>
      <li>[https://robinlinus.com/binohash.pdf][https://robinlinus.com/binohash.pdf]</li>
    </ul>
  </li>
</ul>]]></content><author><name></name></author><summary type="html"><![CDATA[BitDevs Amsterdam meeting 026!]]></summary></entry><entry><title type="html">BitDevs Rotterdam, February 5, 2026</title><link href="//bitdevsamsterdam.org/2026-02-05-february-bitdevs-rotterdam" rel="alternate" type="text/html" title="BitDevs Rotterdam, February 5, 2026" /><published>2026-02-05T00:00:00+00:00</published><updated>2026-02-05T00:00:00+00:00</updated><id>//bitdevsamsterdam.org/february-bitdevs-rotterdam</id><content type="html" xml:base="//bitdevsamsterdam.org/2026-02-05-february-bitdevs-rotterdam"><![CDATA[<h2 id="bitdevs-rotterdam-meeting-025">BitDevs Rotterdam meeting 025!</h2>

<p>It’s time for another BitDevs! A big thanks to <a href="https://www.blockrise.com/nl">Blockrise</a> for sponsoring us with the meeting space. Drinks will be provided, so please ensure you have some dinner beforehand or bring it along to the seminar.</p>

<h3 id="thursday-february-5th-2026--7pm">Thursday, February 5th, 2026 @ 7PM</h3>

<p>Doors open at 6:30PM and we will try to start promptly at 7PM. As a reminder, the ground rules of BitDevs are as follows:</p>

<ol>
  <li>No photos, videos, or recordings.</li>
  <li><a href="https://en.wikipedia.org/wiki/Chatham_House_Rule">Chatham House Rule</a>: you may
reiterate the contents of the meeting <em>without</em> attribution.</li>
</ol>

<p>These rules exist so that BitDevs participants can speak freely within the event.</p>

<h3 id="agenda">Agenda</h3>

<h4 id="part-i-bip54-consensus-cleanup-revival">Part I: BIP54 (Consensus Cleanup Revival)</h4>

<ul>
  <li>BIP: <a href="https://bips.dev/54/">bips.dev/54</a></li>
  <li>Bitcoin Inquisition PR: <a href="https://github.com/bitcoin-inquisition/bitcoin/pull/99">bitcoin-inquisition/bitcoin#99</a></li>
  <li>Ongoing discussion
    <ul>
      <li>Modifying BIP54 timestamp restriction to support a future “ntime soft fork”
        <ul>
          <li><a href="https://groups.google.com/g/bitcoindev/c/L4Eu9bA5iBw/m/jo9RzS-HAQAJ">Bitcoin-Dev list</a></li>
          <li><a href="https://delvingbitcoin.org/t/modifying-bip54-to-support-future-ntime-soft-fork/2163">delvingbitcoin.org</a></li>
        </ul>
      </li>
    </ul>
  </li>
</ul>

<h4 id="part-ii-bitcoin-open-source-vs-llm-coding">Part II: Bitcoin Open Source vs LLM coding</h4>

<p>Open discussion around bitcoin open source development and the challenges that
wide adoption of LLM/agentic coding presents. Main discussion will be around development flow, reviews, repository policies and security.</p>]]></content><author><name></name></author><summary type="html"><![CDATA[BitDevs Rotterdam meeting 025!]]></summary></entry><entry><title type="html">BitDevs Rotterdam, January 8, 2026 (❄️ cancelled)</title><link href="//bitdevsamsterdam.org/2026-01-08-january-bitdevs-rotterdam" rel="alternate" type="text/html" title="BitDevs Rotterdam, January 8, 2026 (❄️ cancelled)" /><published>2026-01-08T00:00:00+00:00</published><updated>2026-01-08T00:00:00+00:00</updated><id>//bitdevsamsterdam.org/january-bitdevs-rotterdam</id><content type="html" xml:base="//bitdevsamsterdam.org/2026-01-08-january-bitdevs-rotterdam"><![CDATA[<h2 id="bitdevs-rotterdam-meeting-025">BitDevs Rotterdam meeting 025!</h2>

<p>❄️❄️❄️ Sadly this months’s Rotterdam meetup has been cancelled due to snow.</p>

<p>We’ll announce the next meetup and location soon(tm).</p>]]></content><author><name></name></author><summary type="html"><![CDATA[BitDevs Rotterdam meeting 025!]]></summary></entry><entry><title type="html">BitDevs Amsterdam, December 4th, 2025</title><link href="//bitdevsamsterdam.org/2025-12-04-december-bitdevs-amsterdam" rel="alternate" type="text/html" title="BitDevs Amsterdam, December 4th, 2025" /><published>2025-12-04T00:00:00+00:00</published><updated>2025-12-04T00:00:00+00:00</updated><id>//bitdevsamsterdam.org/december-bitdevs-amsterdam</id><content type="html" xml:base="//bitdevsamsterdam.org/2025-12-04-december-bitdevs-amsterdam"><![CDATA[<h2 id="bitdevs-amsterdam-meeting-024">BitDevs Amsterdam meeting 024!</h2>

<p>It’s time for another BitDevs! A big thanks to <a href="https://www.bitonic.nl">Bitonic</a> for sponsoring us with the meeting space. Drinks will be provided, so please ensure you have some dinner beforehand or bring it along to the seminar.</p>

<h3 id="thursday-december-4th-2025--7pm">Thursday, December 4th, 2025 @ 7PM</h3>

<p>Doors open at 6:30PM and we will try to start promptly at 7PM. As a reminder, the ground rules of BitDevs are as follows:</p>

<ol>
  <li>No photos, videos, or recordings.</li>
  <li><a href="https://en.wikipedia.org/wiki/Chatham_House_Rule">Chatham House Rule</a>: you may
reiterate the contents of the meeting <em>without</em> attribution.</li>
</ol>

<p>These rules exist so that BitDevs participants can speak freely within the event.</p>

<h1 id="agenda">Agenda</h1>

<p>The mysterious Bitcoin Core developers met in October. Minutes of meeting were leaked!</p>

<p>We’ll cover these topics based on the collected notes:</p>

<ul>
  <li><a href="https://btctranscripts.com/bitcoin-core-dev-tech/2025-10">https://btctranscripts.com/bitcoin-core-dev-tech/2025-10</a></li>
</ul>

<h2 id="softforks">Softforks</h2>

<ul>
  <li><a href="https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/cisa">CISA FullAgg BIP</a></li>
</ul>

<h2 id="networking">Networking</h2>

<ul>
  <li><a href="https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/package-relay">Package Relay</a></li>
  <li><a href="https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/asmap">ASMap</a></li>
  <li><a href="https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/security-audit">Security Audit</a></li>
  <li><a href="https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/sockets-abstraction">Low Level Sockets Abstraction</a></li>
  <li><a href="https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/net-net_processing-split">net - net_processing split</a></li>
</ul>

<h2 id="plumbing">Plumbing</h2>

<ul>
  <li><a href="https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/cluster-mempool">Cluster Mempool</a></li>
  <li><a href="https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/multiprocess-mining-interface">Multiprocess and mining interface</a></li>
  <li><a href="https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/cmake">CMake</a></li>
  <li><a href="https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/batch-validation">Batch Validation</a></li>
  <li><a href="https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/libsha">libsha</a></li>
</ul>

<h2 id="privacy-and-security">Privacy and security</h2>

<ul>
  <li><a href="https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/private-broadcast">Private broadcast</a></li>
  <li><a href="https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/fingerprinting">Fingerprinting</a></li>
  <li><a href="https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/breaking-secp256k1">A secp256k1 break? (quantum)</a></li>
</ul>

<h2 id="test-developer-tools">Test, developer tools</h2>

<ul>
  <li><a href="https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/fuzzamoto">Fuzzamoto</a></li>
  <li><a href="https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/debugging">Debugging</a></li>
  <li><a href="https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/corecheck">CoreCheck</a></li>
</ul>

<h2 id="meta">Meta</h2>

<ul>
  <li><a href="https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/smes-and-wgs">Subject matter experts and working groups</a></li>
</ul>]]></content><author><name></name></author><summary type="html"><![CDATA[BitDevs Amsterdam meeting 024!]]></summary></entry><entry><title type="html">BitDevs Rotterdam, November 6, 2025</title><link href="//bitdevsamsterdam.org/2025-11-06-november-bitdevs-rotterdam" rel="alternate" type="text/html" title="BitDevs Rotterdam, November 6, 2025" /><published>2025-11-06T00:00:00+00:00</published><updated>2025-11-06T00:00:00+00:00</updated><id>//bitdevsamsterdam.org/november-bitdevs-rotterdam</id><content type="html" xml:base="//bitdevsamsterdam.org/2025-11-06-november-bitdevs-rotterdam"><![CDATA[<h2 id="bitdevs-rotterdam-meeting-023">BitDevs Rotterdam meeting 023!</h2>

<p>It’s time for another BitDevs! A big thanks to <a href="https://www.blockrise.com/nl">Blockrise</a> for sponsoring us with the meeting space. Drinks will be provided, so please ensure you have some dinner beforehand or bring it along to the seminar.</p>

<h3 id="thursday-november-6th-2025--7pm">Thursday, November 6th, 2025 @ 7PM</h3>

<p>Doors open at 6:30PM and we will try to start promptly at 7PM. As a reminder, the ground rules of BitDevs are as follows:</p>

<ol>
  <li>No photos, videos, or recordings.</li>
  <li><a href="https://en.wikipedia.org/wiki/Chatham_House_Rule">Chatham House Rule</a>: you may
reiterate the contents of the meeting <em>without</em> attribution.</li>
</ol>

<p>These rules exist so that BitDevs participants can speak freely within the event.</p>

<h1 id="agenda">Agenda</h1>

<p>This month’s agenda is inspired by the lightning++ conference in Berlin that took place earlier in October. Unfortunately individual videos corresponding to specific talks have not yet been uploaded, and also any recordings of the secondary stage are not uploaded. That means that reading material remains in text form.</p>

<ul>
  <li><strong>RGB on lightning</strong>: bringing RGB assets on the LN level by pulling the assets in the channel via the op_return field
    <ul>
      <li><a href="https://btcplusplus.dev/conf/berlin25/talks#b25_rgb">lightning++ Talk description</a></li>
      <li><a href="https://docs.rgb.info/rgb-over-lightning-network/lightning-network-compatibility">RGB LN docs</a></li>
    </ul>
  </li>
  <li><strong>Spark</strong>: a new solution to batching payments with interesting trust assumptions/guarantees
    <ul>
      <li><a href="https://docs.spark.money/learn/tldr">Spark docs TLDR</a></li>
      <li><a href="https://docs.spark.money/learn/technical-definitions">Spark docs Technical Definitions</a></li>
    </ul>
  </li>
  <li><strong>Gossip v2: path to minisketch</strong>: Current state of lightning gossip and how minisketch can improve it
    <ul>
      <li><a href="https://github.com/jharveyb/gossip_observer">Gossip Observer repository</a></li>
      <li><a href="https://bitcoinops.org/en/topics/minisketch/">Bitcoin Ops: Minisketch</a></li>
    </ul>
  </li>
  <li><strong>Lightning’s “toxic” waste problem</strong>: In the long term of running a lightning node you have to consider  your own storage as an attack vector on privacy – you keep track of everything you ever sent/received or forwarded
    <ul>
      <li><a href="https://btcplusplus.dev/conf/berlin25/talks#b25_waste">lightning++ Talk description</a></li>
      <li><a href="https://github.com/lightningnetwork/lnd/issues/9963">Related LND issue</a></li>
      <li><a href="https://github.com/lightningnetwork/lnd/blob/017299fe6f3aec3d8c7ece84c383a47da59862f0/docs/forwarding_history_privacy.md">Pull Request doc explaining this in-depth</a></li>
    </ul>
  </li>
  <li><strong>State of Lightning Privacy</strong>: One of the strongest aspects of lightning is the privacy model. How well does it hold and how hard is it for an attacker to gain any information related to identifying the actors within the system.
    <ul>
      <li><a href="https://arxiv.org/abs/2006.12143">arxiv: Research Paper</a></li>
      <li><a href="https://stacker.news/items/1012159">Stackernews post with older video</a></li>
    </ul>
  </li>
</ul>]]></content><author><name></name></author><summary type="html"><![CDATA[BitDevs Rotterdam meeting 023!]]></summary></entry><entry><title type="html">BitDevs Amsterdam, October 2nd, 2025</title><link href="//bitdevsamsterdam.org/2025-10-02-october-bitdevs-amsterdam" rel="alternate" type="text/html" title="BitDevs Amsterdam, October 2nd, 2025" /><published>2025-10-02T00:00:00+00:00</published><updated>2025-10-02T00:00:00+00:00</updated><id>//bitdevsamsterdam.org/october-bitdevs-amsterdam</id><content type="html" xml:base="//bitdevsamsterdam.org/2025-10-02-october-bitdevs-amsterdam"><![CDATA[<h2 id="bitdevs-amsterdam-meeting-022">BitDevs Amsterdam meeting 022!</h2>

<p>It’s time for another BitDevs! A big thanks to <a href="https://www.bitonic.nl">Bitonic</a> for sponsoring us with the meeting space. Drinks will be provided, so please ensure you have some dinner beforehand or bring it along to the seminar.</p>

<h3 id="thursday-october-2nd-2025--7pm">Thursday, October 2nd, 2025 @ 7PM</h3>

<p>Doors open at 6:30PM and we will try to start promptly at 7PM. As a reminder, the ground rules of BitDevs are as follows:</p>

<ol>
  <li>No photos, videos, or recordings.</li>
  <li><a href="https://en.wikipedia.org/wiki/Chatham_House_Rule">Chatham House Rule</a>: you may
reiterate the contents of the meeting <em>without</em> attribution.</li>
</ol>

<p>These rules exist so that BitDevs participants can speak freely within the event.</p>

<h1 id="agenda">Agenda</h1>

<h2 id="prs--releases">PRs / Releases</h2>

<ul>
  <li><a href="https://groups.google.com/g/bitcoindev/c/BvNQ3YdI4_k">Bitcoin Core v30rc2 release candidate available</a>
    <ul>
      <li><a href="https://github.com/bitcoin-core/bitcoin-devwiki/wiki/30.0-Release-Candidate-Testing-Guide">Bitcoin Core v30 Testing Guide</a></li>
      <li><a href="https://github.com/bitcoin-core/bitcoin-devwiki/wiki/v30.0-Release-Notes-Draft">Release notes draft</a></li>
    </ul>
  </li>
  <li><a href="https://delvingbitcoin.org/t/peer-observer-a-tool-and-infrastructure-for-monitoring-the-bitcoin-p2p-network-for-attacks-and-anomalies/1988">peer-observer: Monitoring the Bitcoin p2p network</a></li>
  <li><a href="https://github.com/rust-bitcoin/rust-bitcoin/pull/4919">rust-bitcoin: add SHA3-256</a></li>
  <li><a href="https://github.com/bitcoin-core/secp256k1/pull/1725">libsecp: refactor tagged hash verification</a></li>
  <li>Rust multiprocess support for interacting with Bitcoin Core
    <ul>
      <li><a href="https://github.com/rustaceanrob/bitcoin-core-capnp-schemas">Capnp Schemas</a></li>
      <li><a href="https://github.com/rustaceanrob/bitcoin-capnp-types">Auto generated types</a></li>
      <li><a href="https://github.com/bitcoin-core/libmultiprocess/issues/217">RFC: How to version and release Capnp schemas</a></li>
    </ul>
  </li>
</ul>

<h2 id="research">Research</h2>

<ul>
  <li><a href="https://five.bitcoin.design/">Five Years of Bitcoin Design</a></li>
  <li><a href="https://binaryigor.com/bitcoin-core-code.html">Bitcoin Core Code - a review</a></li>
  <li><a href="https://eprint.iacr.org/2025/1459.pdf">Not in The Prophecies: Practical Attacks on Nostr</a></li>
</ul>

<h2 id="proposals">Proposals</h2>

<ul>
  <li><a href="https://github.com/bitcoin/bitcoin/issues/33389">RFC: Bitcoin Core BlockTemplateManager</a>
    <ul>
      <li><a href="https://github.com/bitcoin/bitcoin/pull/33421">#33421: Add BlockTemplate cache</a></li>
    </ul>
  </li>
</ul>]]></content><author><name></name></author><summary type="html"><![CDATA[BitDevs Amsterdam meeting 022!]]></summary></entry><entry><title type="html">BitDevs Rotterdam, September 4, 2025</title><link href="//bitdevsamsterdam.org/2025-09-04-bitdevs-rotterdam" rel="alternate" type="text/html" title="BitDevs Rotterdam, September 4, 2025" /><published>2025-09-04T00:00:00+00:00</published><updated>2025-09-04T00:00:00+00:00</updated><id>//bitdevsamsterdam.org/bitdevs-rotterdam</id><content type="html" xml:base="//bitdevsamsterdam.org/2025-09-04-bitdevs-rotterdam"><![CDATA[<h2 id="bitdevs-rotterdam-meeting-021">BitDevs Rotterdam meeting 021!</h2>

<p>It’s time for another BitDevs! A big thanks to <a href="https://www.blockrise.com/nl">Blockrise</a> for sponsoring us with the meeting space. Drinks will be provided, so please ensure you have some dinner beforehand or bring it along to the seminar.</p>

<h3 id="thursday-september-4rd-2025--7pm">Thursday, September 4rd, 2025 @ 7PM</h3>

<p>Doors open at 6:30PM and we will try to start promptly at 7PM. As a reminder, the ground rules of BitDevs are as follows:</p>

<ol>
  <li>No photos, videos, or recordings.</li>
  <li><a href="https://en.wikipedia.org/wiki/Chatham_House_Rule">Chatham House Rule</a>: you may
reiterate the contents of the meeting <em>without</em> attribution.</li>
</ol>

<p>These rules exist so that BitDevs participants can speak freely within the event.</p>

<h1 id="agenda">Agenda</h1>

<h2 id="policy-policy-policy">Policy, policy, policy!</h2>

<ul>
  <li><a href="https://delvingbitcoin.org/t/stats-on-compact-block-reconstructions/1052/35">“Stats on compact block reconstruction”</a></li>
  <li><a href="https://delvingbitcoin.org/t/changing-the-minimum-relay-feerate/1886">“Changing the mimimum relay feerate”</a></li>
  <li><a href="https://github.com/bitcoin/bitcoin/pull/33106">“#33106: policy: lower default {*}fee”</a></li>
</ul>

<h2 id="notable-prs--proposals">Notable PRs / proposals</h2>

<ul>
  <li><a href="https://github.com/bitcoin/bitcoin/pull/32279">“#32279: [IBD] store common scripts inline”</a></li>
  <li><a href="https://github.com/bitcoin/bitcoin/pull/31802">“#38102: add bitcoin-{gui,node} to release binaries for IPC”</a></li>
  <li><a href="https://github.com/bitcoin/bitcoin/pull/31244">“#31244: musig2 descriptors”</a></li>
</ul>

<h2 id="research">Research</h2>

<ul>
  <li><a href="https://qubic.org/pr/qubic-overtakes-monero-s-hash-rate-in-live-51-takeover-demo">“Live 51% attack on Monero”</a>
    <ul>
      <li><a href="https://delvingbitcoin.org/t/qubic-attack-on-monero/1920">“Qubic Attack on Monero”</a></li>
    </ul>
  </li>
  <li><a href="https://github.com/jlopp/physical-bitcoin-attacks/blob/master/Wrench_Attacks_Research.pdf">“Wrench Attacks Research”</a></li>
</ul>]]></content><author><name></name></author><summary type="html"><![CDATA[BitDevs Rotterdam meeting 021!]]></summary></entry></feed>