We will start with introductions, some basic ground rules, and jump into technical discussions. We will cover aspects of the bitcoin protocol, new research developments, recent news, and software developments.

Please note the meeting location at 4801 Glenwood Ave suite 200 in Raleigh, right above Fifth Third Bank.

Announcements

  • no pictures or recordings
  • chatham house rules
  • don’t be a dick
  • Hack Day - unstructured monthly in-person meetup for bitcoin builders
  • thank you to our sponsor Lolli
  • introductions

Bitcoin

Package Relay

Package relay is a proposed feature to allow bitcoin nodes to evaluate multiple transactions together (a package) for inclusion or rejection from the mempool. This feature is motivated by off-chain protocols such as lightning and DLCs with a security model that assumes the ability for a user to get a transaction confirmed using CPFP fee bumping within a specific timeframe. The current mempool design evaluates each transaction individually which makes these protocols inherently vulnerable to pinning attacks. The main challenge of development is insuring that the new set of mempool acceptance rules do not open new vectors of DoS attack.

V3 Transactions

Version 3 transaction relay is a proposal to create an opt-in superset of transaction relay rules that limit all pinning vectors while allowing CPFP fee bumping via package RBF. This proposal builds on package relay to create a new type of transaction that can always be fee bumped even when an adversarial party controls one or more inputs and outputs, i.e. lightning channel force closes.

Ephemeral Anchors

Ephemeral anchors are yet another proposal that builds on package relay and V3 outputs in order to cover the case of symmetric commitment transactions for protocols such as LN-symmetry. An ephemeral output is a 0-sat transaction output that must be spent by another transaction in the same package. Under these rules an ephemeral anchor output cannot be pinned in the mempool and can be fee-bumped by anyone.

Lightning

Securing a $100M Lightning node

In their latest blog post Eclair walks us through the security architecture of the ACINQ node, among the largest and most connected nodes on the network. The article is a well-written and thorough high level examination of the security issues and design space of this fascinating problem.

10101 is building DLCs on Lightning

A new company called 10101 (pronounced ten-ten-one) is building DLC capability into lightning. In this three part blog series they explain what DLCs are, how they are enabled on lightning, and how they use virtual channels to accomplish this in practice.

How the Voltage LSP Enhances Privacy for Mutiny Wallet Users

In this blog post Tony Giorgio explains how Mutiny Wallet leverages the Voltage LSP to enhance the privacy of their wallet users using just-in-time lightning channels to enable a VPN-like architecture for lightning payments.

Taproot Assets: Issuing Assets on Bitcoin

The good folks at Voltage have published this well written and accessible blog post discussing Taproot Assets–how they work, how they leverage lightning’s network effects, and introduce new liquidity management requirements and business use cases for node runners.

Ecash

Fedimint v0.1.0 release

Fedimint has cut their first official release. Plebs rejoice! Free and open source privacy-preserving bitcoin-backed federated private banking is one step closer to reality. Fuck yeah!

Cashu DLEQ proofs

Cashu has nearly completed their implementation of Discreet Log Equality Proofs (DLEQ). This is a cryptographic protocol that can be used to prove the validity of a mint’s signature without knowing the private key used to create the signature. This is an important capability that will unlock offline ecash payments. It also carries improved privacy assurances that the mint is not using distinct private keys to deanonymize users.