It’s time for another BitDevs! A big thanks to Blockrise 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.

Thursday, September 3rd, 2026 @ 7PM

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:

1. No photos, videos, or recordings.
2. Chatham House Rule: you may reiterate the contents of the meeting without attribution.

These rules exist so that BitDevs participants can speak freely within the event.

Agenda

TBA

There will be no BitDevs meetup in August. Enjoy the summer!

We’ll be back in September. Keep an eye on our Meetup page for the next announcement.

It’s time for another BitDevs! A big thanks to Bitonic 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.

Thursday, July 2nd, 2026 @ 7PM

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:

1. No photos, videos, or recordings.
2. Chatham House Rule: you may reiterate the contents of the meeting without attribution.

These rules exist so that BitDevs participants can speak freely within the event.

Agenda

Bitcoin Core

• PrivateBroadcast IP leak: A privacy bug in Bitcoin Core 31.0 where a failed BIP324 v2 handshake retries over v1 without Tor, leaking the sender’s IP despite -privatebroadcast; fixed in 31.1.
  • https://bitcoincore.org/en/2026/06/06/privatebroadcast-ip-leak/
• Full Libevent removal (Bitcoin Core #34411): Completes the long-running, multi-contributor effort to fully drop the libevent dependency from Bitcoin Core.
  • https://github.com/bitcoin/bitcoin/pull/34411

P2p

• BIP54 coinbase-locktime compliance over 40%: Over 40% of coinbase transactions now set their nLockTime per BIP-54 (block height minus 1), reflecting actual compliance rather than mere signaling.
  • https://mainnet.observer/charts/transactions-coinbase-locktime-bip54/

Mining

• BitAxe Stratum V2 support: Adds Stratum V2 binary protocol support with Noise encryption to the open-source BitAxe miner alongside V1, tested at full 1.3 TH/s against an SRI pool.
  • https://github.com/bitaxeorg/ESP-Miner/pull/1553

Post-quantum

• Public key recovery for EC leaves in P2MR (BIP-360): Proposes recovering the public key from the signature instead of revealing it in the witness, shrinking the EC spending path of this post-quantum address scheme from 135 to ~100 bytes.
  • https://delvingbitcoin.org/t/public-key-recovery-for-ec-leaves-in-p2mr-bip-360/2603
• Framework for post-quantum outputs: {Never, Later, Now} × {Merkle, Taproot}: Pieter Wuille’s bitcoin-dev framework for reasoning about when to deploy quantum-resistant outputs and whether to structure them as Merkle-based (P2MR) or Taproot-based commitments.
  • https://groups.google.com/g/bitcoindev/c/p8AVEmAtWdA/m/Gona1fr3AgAJ

Layer 2 and scaling

• Credible Exit and the Law of Conservation of Blockspace: Argues that the blockspace needed for users to credibly exit to the base layer imposes a fundamental limit on how many users Bitcoin layers can support trust-minimally.
  • https://delvingbitcoin.org/t/credible-exit-and-the-law-of-conservation-of-blockspace/2503
• Ark: offchain transaction batching: A commit-chain protocol where an untrusted operator batches transfers of virtual UTXOs into a near-constant ~200 vB onchain footprint, letting recipients accept payments without pre-locking funds.
  • https://arxiv.org/abs/2605.20952
• Bark now on Bitcoin mainnet: Second has launched Bark, their self-custodial implementation of the Ark protocol, on mainnet, shipping an SDK and apps spanning Ark, Lightning, and on-chain payments.
  • https://blog.second.tech/bark-now-on-bitcoin-mainnet/

Lightning Network

• lnd zero-timestamp gossip DoS disclosure: A validly signed gossip message with timestamp 0 panics and crashes lnd nodes before v0.20.1, which now rejects such messages at parse time.
  • https://delvingbitcoin.org/t/lnd-zero-timestamp-gossip-dos-disclosure/2621
• Fast Neutrino header sync (lnd PR #10552): Cuts lnd’s Neutrino initial sync from hours to minutes by importing pre-built block and filter headers from files or HTTP before falling back to peer-to-peer sync.
  • https://github.com/lightningnetwork/lnd/pull/10552
• Scaling the Lightning Network with Practical Set Reconciliation: Replaces inefficient flooding-based gossip with set reconciliation via a new adaptive IBLT scheme, cutting reconciliation from hours to minutes in Core Lightning simulations.
  • https://ipsit.bu.edu/documents/icbc26.pdf
• LNTest: evaluating Lightning-based botnets: A containerized Core Lightning testbed for studying botnets that abuse Lightning for command-and-control, which debunks prior D-LNBot claims by showing fragile topologies and linear rather than logarithmic scaling.
  • https://arxiv.org/abs/2606.12887

Community

• Want to submit a discussion topic? Open an issue or PR at https://github.com/bitdevsamsterdam/bitdevsamsterdam.github.io

It’s time for another BitDevs! A big thanks to Blockrise 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.

Thursday, June 4th, 2026 @ 7PM

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:

1. No photos, videos, or recordings.
2. Chatham House Rule: you may reiterate the contents of the meeting without attribution.

These rules exist so that BitDevs participants can speak freely within the event.

Agenda

First half

Bitcoin CoreDev topics recap

Second half

Lightning Network spec meeting topics recap

It’s time for another BitDevs! A big thanks to Bitonic 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.

Thursday, May 14th, 2026 @ 7PM

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:

1. No photos, videos, or recordings.
2. Chatham House Rule: you may reiterate the contents of the meeting without attribution.

These rules exist so that BitDevs participants can speak freely within the event.

Agenda

Bitcoin Core

• CVE-2024-52911 disclosure: A use-after-free bug in Bitcoin Core’s script validation that could allow attackers to crash nodes or potentially execute remote code. The flaw involves PrecomputedTransactionData being destroyed before the CCheckQueueControl, causing background validation threads to access freed memory when processing crafted blocks.
  • https://bitcoincore.org/en/2026/05/05/disclose-cve-2024-52911/
• Knotzi death march: A countdown timer page tracking BIP-110 nodes that will eventually be disconnected from the Bitcoin network. Provides background reading and visibility into the node deprecation process.
  • https://jlopp.github.io/knotzi-death-march/
• Slow block propagation and validation on signet: Measurements showing that slowly-validating blocks on Bitcoin’s Signet testnet propagate approximately 160 times slower than normal blocks. Median validation took around 20 seconds compared to 176 milliseconds for standard blocks, highlighting real-world impact of BIP 54’s targeted issues.
  • https://b10c.me/observations/16-slow-block-propagation-validation-signet/

Mining and consensus research

• Inertial Mining: A proposed mining protocol that produces Nakamoto’s intended single longest chain outcome while constituting a true game-theoretic equilibrium. The authors show that neither selfish mining nor any other deviation is profitable for miners controlling less than half the network’s power.
  • https://arxiv.org/abs/2604.06092
• Temporary Power Adjusting Withholding (T-PAW) attack: A generalized block withholding attack strategy targeting mining pools that improves on the existing PAW attack. The research demonstrates that small miners can achieve up to 22x revenue increases in certain scenarios, exposing a structural weakness in pooled mining.
  • https://arxiv.org/abs/2604.14135

Post-quantum

• Localhost Research Post Quantum Cryptography Group: Localhost Research announces a new PQC group with cryptographers Benedikt Bünz and Dan Boneh to research solutions protecting Bitcoin from future quantum threats. The initiative focuses on conservative hash-based signature schemes and threshold constructions suitable for Bitcoin’s operational constraints.
  • https://lclhost.org/blog/post-quantum-cryptography-group/
• Avoiding an Unnecessary Quantum Freeze: Proposes an alternative to automatically freezing quantum-vulnerable coins after a fixed period. Instead, a “canary” address would trigger the freeze only if someone proves a quantum computer exists by spending from it, keeping vulnerable coins spendable in the meantime.
  • https://www.bitmex.com/blog/Avoiding-An-Unnecessary-Quantum-Freeze

Lightning Network

• LDK Server: A fully-functional Lightning node in daemon form, providing an API-first solution for deploying and managing a Lightning Network node. It abstracts over LDK and BDK, exposing a gRPC interface for cross-language integration.
  • https://spiral.xyz/ldkserver.pdf
• Onion message jamming in the Lightning Network: Adversaries can flood the network with onion message spam to degrade service for legitimate users. The vulnerability exists because routing nodes currently forward these messages for free, making large-scale jamming economically trivial while legitimate traffic gets rate-limited.
  • https://delvingbitcoin.org/t/onion-message-jamming-in-the-lightning-network/2414
• Towards a k-of-n Lightning Network node: Proposes making multisignature Lightning nodes feasible by removing the shachain requirement from BOLT specifications. True k-of-n security (where k devices must be compromised to steal funds) is currently impossible with shachains, requiring protocol changes and gateway nodes to bridge legacy systems.
  • https://delvingbitcoin.org/t/towards-a-k-of-n-lightning-network-node/2395
• Simple Taproot Channels (BOLT PR #995): An extension BOLT spec for Taproot-based Lightning channels using Schnorr signatures, MuSig2 key aggregation, and Taproot scripts. Establishes the minimal changes needed to upgrade channels while maintaining backward compatibility with existing implementations.
  • https://github.com/lightning/bolts/pull/995

Community

• Want to submit a discussion topic? Open an issue or PR at https://github.com/bitdevsamsterdam/bitdevsamsterdam.github.io

It’s time for another BitDevs! A big thanks to Blockrise 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.

Thursday, April 2nd, 2026 @ 7PM

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:

1. No photos, videos, or recordings.
2. Chatham House Rule: you may reiterate the contents of the meeting without attribution.

These rules exist so that BitDevs participants can speak freely within the event.

Agenda

• Disposing of dust attack UTXOs: 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.
  • https://delvingbitcoin.org/t/disposing-of-dust-attack-utxos/2215
• BIP 54 (Consensus Cleanup) active on Bitcoin Inquisition: 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.
  • https://groups.google.com/g/bitcoindev/c/wOVjJoLDWfA
• Hourglass V2 update: 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.
  • https://groups.google.com/g/bitcoindev/c/0E1UyyQIUA0
• BIP 360: Pay to Merkle Root (P2MR): 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.
  • https://github.com/bitcoin/bips/pull/1670
• BIP 392: Silent Payment Output Script Descriptors: Introduces a new output descriptor format for Silent Payments (BIP352), proposing sp() script expressions with spscan and spspend key expressions, allowing wallets to represent and manage silent payment keys using a standardized descriptor format.
  • https://github.com/bitcoin/bips/pull/2047
• Two-block reorg at height 941880: 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.
  • https://bnoc.xyz/t/two-block-reorg-at-height-941880/97
• Fuzzor: continuous fuzzing infrastructure: 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.
  • https://github.com/dergoegge/fuzzor
• Want to submit a discussion topic? Open an issue or PR at https://github.com/bitdevsamsterdam/bitdevsamsterdam.github.io

It’s time for another BitDevs! A big thanks to Bitonic 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.

Thursday, March 5th, 2026 @ 7PM

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:

1. No photos, videos, or recordings.
2. Chatham House Rule: you may reiterate the contents of the meeting without attribution.

These rules exist so that BitDevs participants can speak freely within the event.

Agenda

• hArk (hash-lock-Ark): 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.
  • https://x.com/2ndbtc/status/2015401100355002626
• ZK Statechains: 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.
  • https://delvingbitcoin.org/t/zk-statechains-without-states/2166
• Taproot Quantum Spend Paths: 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.
  • https://www.bitmex.com/blog/Taproot-Quantum-Spend-Paths
• Lightning Network surpassed $1B in monthly volume
  • https://x.com/SDWouters/status/2024507942708351443
  • River: Bitcoin Adoption 2026 — 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.
• L402 Apps: 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.
  • https://www.l402apps.com/
• BIP352 update: 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.
  • https://github.com/bitcoin/bips/pull/2055
• sedited added to trusted-keys: Adds sedited to Bitcoin Core’s trusted-keys file, granting cryptographic signing authority for the release process.
  • https://github.com/bitcoin/bitcoin/pull/34236
• Incremental mutation testing in Bitcoin Core: 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.
  • https://delvingbitcoin.org/t/incremental-mutation-testing-in-the-bitcoin-core/2197
• Binohash: Transaction Introspection Without Softforks: A collision-resistant hash function for Bitcoin Script that enables limited transaction introspection without consensus changes.
  • [https://robinlinus.com/binohash.pdf][https://robinlinus.com/binohash.pdf]

It’s time for another BitDevs! A big thanks to Blockrise 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.

Thursday, February 5th, 2026 @ 7PM

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:

1. No photos, videos, or recordings.
2. Chatham House Rule: you may reiterate the contents of the meeting without attribution.

These rules exist so that BitDevs participants can speak freely within the event.

Agenda

Part I: BIP54 (Consensus Cleanup Revival)

• BIP: bips.dev/54
• Bitcoin Inquisition PR: bitcoin-inquisition/bitcoin#99
• Ongoing discussion
  • Modifying BIP54 timestamp restriction to support a future “ntime soft fork”
    • Bitcoin-Dev list
    • delvingbitcoin.org

Part II: Bitcoin Open Source vs LLM coding

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.

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

We’ll announce the next meetup and location soon(tm).

It’s time for another BitDevs! A big thanks to Bitonic 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.

Thursday, December 4th, 2025 @ 7PM

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:

1. No photos, videos, or recordings.
2. Chatham House Rule: you may reiterate the contents of the meeting without attribution.

These rules exist so that BitDevs participants can speak freely within the event.

Agenda

The mysterious Bitcoin Core developers met in October. Minutes of meeting were leaked!

We’ll cover these topics based on the collected notes:

• https://btctranscripts.com/bitcoin-core-dev-tech/2025-10

Softforks

• CISA FullAgg BIP

Networking

• Package Relay
• ASMap
• Security Audit
• Low Level Sockets Abstraction
• net - net_processing split

Plumbing

• Cluster Mempool
• Multiprocess and mining interface
• CMake
• Batch Validation
• libsha

Privacy and security

• Private broadcast
• Fingerprinting
• A secp256k1 break? (quantum)

Test, developer tools

• Fuzzamoto
• Debugging
• CoreCheck

Meta

• Subject matter experts and working groups