Bitcoin Mailing List

https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

This account functions as a mirror to the Bitcoin mailing list

Public Key

npub15g7m7mrveqlpfnpa7njke3ccghmpryyqsn87vg8g8eqvqmxd60gqmx08lk

NIP-05 Address

bitcoin@n0str.me

NIP-57 Address

tal@n0str.me

Profile Code

nprofile1qqs2y0dld3kvs0s5es7lfetvcuvytas3jzqgfnlxyr5rusxqdnxa85qprpmhxue69uhhyetvv9ujumn0wdmksetjv5hxxmmd3p3l3m

Publishing to

relay.noswhere.com

Author Public Key

npub15g7m7mrveqlpfnpa7njke3ccghmpryyqsn87vg8g8eqvqmxd60gqmx08lk

Show more details

Last Notes

2023-10-03 21:44:19

- reply

🔖 Title: MATT: Optimistic execution of arbitrary programs
🏷️ Categories: bitcoin-dev, demo
#naddr1qq…xxzs
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-10-03 21:44:18

- reply

🔖 Title: Solving CoinPool high-interactivity issue with cut-through update of Taproot leaves
🏷️ Categories: bitcoin-dev
#naddr1qq…zhv5
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-09-11 21:42:42

- reply

🔖 Title: Parameters in BIP21 URIs
🏷️ Categories: bitcoin-dev
#naddr1qq…c2dy
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-09-07 11:52:37

- reply

🔖 Title: BIP-????: The Taproot Assets Protocol
🏷️ Categories: bitcoin-dev
#naddr1qq…dd78
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-09-07 11:52:36

- reply

🔖 Title: libsecp256k1 v0.4.0 released
🏷️ Categories: bitcoin-dev
#naddr1qq…k32v
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-09-07 11:52:36

- reply

🔖 Title: Concern about "Inscriptions"
🏷️ Categories: bitcoin-dev
#naddr1qq…mr53
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-09-07 11:52:34

- reply

🔖 Title: Compressed Bitcoin Transactions
🏷️ Categories: bitcoin-dev
#naddr1qq…c2km
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-09-07 11:52:33

- reply

🔖 Title: Announcing B'SST: Bitcoin-like Script Symbolic Tracer
🏷️ Categories: bitcoin-dev
#naddr1qq…0d5x
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-09-07 11:52:32

- reply

🔖 Title: Private Collaborative Custody with FROST
🏷️ Categories: bitcoin-dev
#naddr1qq…7f7w
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-08-24 10:13:20

- reply

🔖 Title: Combined CTV+APO to minimal TXHASH+CSFS
🏷️ Categories: bitcoin-dev
#naddr1qq…hwfn
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-08-21 09:55:29

- reply

🔖 Title: Full-RBF testing: at least 31% of hash power, over at least 4 pools, is mining full-RBF right now
🏷️ Categories: bitcoin-dev
#naddr1qq…wfrf
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-08-12 09:56:45

- reply

🔖 Title: BIP for Serverless Payjoin (AdamISZ)
🏷️ Categories: bitcoin-dev
#naddr1qq…hyd6
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-08-12 09:56:44

- reply

🔖 Title: segwit naming ambiguity
🏷️ Categories: bitcoin-dev
#naddr1qq…592v
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-08-10 23:09:40

- reply

🔖 Title: Fw: Re: BIP for Serverless Payjoin
🏷️ Categories: bitcoin-dev
#naddr1qq…md0s
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-08-10 23:09:39

- reply

🔖 Title: BIP for Serverless Payjoin
🏷️ Categories: bitcoin-dev
#naddr1qq…txx8
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-08-08 14:20:52

- reply

🔖 Title: Blinded 2-party Musig2
🏷️ Categories: bitcoin-dev
#naddr1qq…t39w
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-08-06 23:37:36

- reply

🔖 Title: Ark: An Alternative Privacy-preserving Second Layer Solution
🏷️ Categories: bitcoin-dev
#naddr1qq…h4tp
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-08-06 23:37:35

- reply

🔖 Title: Concrete MATT opcodes
🏷️ Categories: bitcoin-dev
#naddr1qq…0k2k
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-08-04 20:19:32

- reply

🔖 Title: BIP-352 Silent Payments addresses should have an expiration time
🏷️ Categories: bitcoin-dev
#naddr1qq…4pzs
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-08-03 17:31:03

- reply

🔖 Title: BIP352: Silent Payments
🏷️ Categories: bitcoin-dev
#naddr1qq…agye
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-08-03 12:35:35

- reply

🔖 Title: Pull-req to remove the arbitrary limits on OP_Return outputs
🏷️ Categories: bitcoin-dev
#naddr1qq…kag8
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-08-02 16:02:44

- reply

🔖 Title: Concern about "Inscriptions"
🏷️ Categories: bitcoin-dev
#naddr1qq…4uuk
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-08-02 16:02:44

- reply

🔖 Title: Concern about "Inscriptions". (Keagan McClelland)
🏷️ Categories: bitcoin-dev
#naddr1qq…x8ss
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-08-02 10:19:21

- reply

🔖 Title: Concern about "Inscriptions". (ashneverdawn)
🏷️ Categories: bitcoin-dev
#naddr1qq…fmll
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-08-01 23:16:05

- reply

🔖 Title: Announcing Libforesta
🏷️ Categories: bitcoin-dev
#naddr1qq…njql
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-08-01 15:59:56

- reply

🔖 Title: Pull-req to enable Full-RBF by default
🏷️ Categories: bitcoin-dev
#naddr1qq…aqdr
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-07-31 16:02:13

- reply

🔖 Title: Pull-req to enable Full-RBF by default
🏷️ Categories: bitcoin-dev
#naddr1qq…42q9
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-07-30 22:52:21

- reply

🔖 Title: Concern about "Inscriptions".
🏷️ Categories: bitcoin-dev, SPAM
#naddr1qq…9udv
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-07-30 22:52:21

- reply

🔖 Title: Pull-req to enable Full-RBF by default
🏷️ Categories: bitcoin-dev
#naddr1qq…ae2h
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-07-27 00:26:35

- reply

🔖 Title: Concern about "Inscriptions".
🏷️ Categories: bitcoin-dev
#naddr1qq…rl3q
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-07-27 00:26:34

- reply

🔖 Title: Blinded 2-party Musig2
🏷️ Categories: bitcoin-dev
#naddr1qq…p3dw
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-07-19 02:09:38

- reply

🔖 Title: On the experiment of the Bitcoin Contracting Primitives WG and marking this community process "up for grabs"
🏷️ Categories: bitcoin-dev
#naddr1qq…x97a
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-07-19 02:09:37

- reply

🔖 Title: Denial of Service using Package Relay
🏷️ Categories: bitcoin-dev
#naddr1qq…w2xl
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-07-04 22:46:05

- reply

🔖 Title: Standardisation of an unstructured taproot annex
🏷️ Categories: bitcoin-dev
#naddr1qq…fvhm
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-07-01 12:15:29

- reply

🔖 Title: Civ Kit: A Peer-to-Peer Electronic Market System
🏷️ Categories: bitcoin-dev
#naddr1qq…0fec
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-06-22 12:12:01

- reply

🔖 Title: Some Day Peg: A crazy two-way peg bridging BTC to other chains Raw
🏷️ Categories: bitcoin-dev
#naddr1qq…vnwf
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-06-21 09:18:57

- reply

🔖 Title: CivKit Node v0.0.1 release - "Sic itur ad astra"
🏷️ Categories: bitcoin-dev
#naddr1qq…xe47
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-06-15 00:54:54

- reply

🔖 Title: Ark: An Alternative Privacy-preserving Second Layer Solution
🏷️ Categories: bitcoin-dev
#naddr1qq…n64u
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-06-15 00:33:42

- reply

🔖 Title: ZeroSync: Introducing Validity Proofs to Bitcoin
🏷️ Categories: bitcoin-dev
#naddr1qq…9ed4
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-06-15 00:33:41

- reply

🔖 Title: Formosa --- proposed improvement upon BIP39
🏷️ Categories: bitcoin-dev
#naddr1qq…mv5s
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-06-15 00:33:41

- reply

🔖 Title: BIP for Silent Payments
🏷️ Categories: bitcoin-dev
#naddr1qq…sghl
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-06-15 00:33:40

- reply

🔖 Title: Conceptual package relay using taproot annex
🏷️ Categories: bitcoin-dev
#naddr1qq…lzfe
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.

2023-06-07 23:22:11

🔖 Title: Bitcoin mail list needs an explicit moderation policy
🏷️ Categories: bitcoin-dev, Lightning-dev
👥 Authors: Bryan Bishop ( @npub1vtw…sjpg )
📅 Messages Date: 2023-06-02
✉️ Message Count: 1
📚 Total Characters in Messages: 3988

2023-06-07 23:22:10

🔖 Title: Bitcoin mail list needs an explicit moderation policy
🏷️ Categories: bitcoin-dev
👥 Authors:
• alicexbt ( @npub1w30…zhn2 )
• Dr Maxim Orlovsky ( @npub1a80…pwgy )
🗒️ Conversation Summary: Dr. Maxim Orlovsky proposed clear moderation policies and the replacement of the current moderator on the bitcoin-dev mail list. Alicexbt suggested creating an unmoderated mailing list for non-censored submissions, regular changes in moderators, and reputation-based incentives.
📅 Messages Date Range: 2023-06-02 to 2023-06-03
✉️ Message Count: 2
📚 Total Characters in Messages: 16621

2023-06-07 23:22:06

🔖 Title: Standardisation of an unstructured taproot annex
🏷️ Categories: bitcoin-dev
👥 Authors:
• Peter Todd ( @npub1m23…2np2 )
• David A. Harding ( @npub16dt…4wrd )
• Joost Jager ( @npub1asl…fqmx )
• Greg Sanders ( @npub1jdl…gh0m )
🗒️ Conversation Summary: The Bitcoin-dev mailing list discussed the taproot annex feature, which allows for immediate utilization and future flexibility. However, there are potential issues with signature hashes not covering other inputs' annex fields in coinjoin scenarios, and the proposed solution may not align with economic incentives. The annex malleability vector could mislead developers into believing their transactions are immune to replacement, resulting in compromised assumptions. A policy to mitigate annex malleability could mislead developers into thinking their transactions are immune to replacement, when they may not be.
📅 Messages Date Range: 2023-06-02 to 2023-06-03
✉️ Message Count: 11
📚 Total Characters in Messages: 21582

2023-06-07 23:22:05

🔖 Title: Vaults in the MATT framework
🏷️ Categories: bitcoin-dev
👥 Authors: Johan Torås Halseth ( @npub1ppn…s2fw )
📅 Messages Date: 2023-06-02
✉️ Message Count: 1
📚 Total Characters in Messages: 19911

2023-06-07 23:22:04

🔖 Title: Scaling and anonymizing Bitcoin at layer 1 with client-side validation
🏷️ Categories: bitcoin-dev
👥 Authors:
• Dr Maxim Orlovsky ( @npub1a80…pwgy )
• John Tromp ( @npub1jzv…sze5 )
🗒️ Conversation Summary: The LNP/BP Standards Association proposed Prime, an anonymous layer 1 upgrade for Bitcoin protocol that doesn't affect BTC or PoW. A white paper proposing Bitcoin PoW anchoring can be found on GitHub, but questions were raised about miner behavior and consensus on protocol reset. Dr Maxim Orlovsky suggested a Bitcoin PoW Anchoring protocol reset that allows for a special bitcoin transaction providing publicly-identifiable OP_RETURN information about a new miner single-use-seal.
📅 Messages Date Range: 2023-06-01 to 2023-06-03
✉️ Message Count: 3
📚 Total Characters in Messages: 5250

2023-06-07 23:22:04

🔖 Title: Full-RBF Peering Bitcoin Core v25.0 Released
🏷️ Categories: bitcoin-dev
👥 Authors: Peter Todd ( @npub1m23…2np2 )
📅 Messages Date: 2023-06-01
✉️ Message Count: 1
📚 Total Characters in Messages: 1325

2023-06-07 23:22:00

🔖 Title: Bitcoin Transaction Relay over Nostr
🏷️ Categories: bitcoin-dev
👥 Authors:
• alicexbt ( @npub1w30…zhn2 )
• David A. Harding ( @npub16dt…4wrd )
• Joost Jager ( @npub1asl…fqmx )
• Greg Sanders ( @npub1jdl…gh0m )
🗒️ Conversation Summary: Nostr, a proposed alternative relay mechanism for Bitcoin transactions, could improve the current P2P system and support non-standard transactions. It could boost the system's resilience, democratize access to miner mempools, and delegate responsibility for dealing with DoS threats to relays. Block templates and weak blocks can be relayed through Nostr, improving fee estimation and providing valuable insights for miners and full nodes. A BIP proposal is needed for weak blocks to improve block relay.
📅 Messages Date Range: 2023-05-23 to 2023-05-30
✉️ Message Count: 6
📚 Total Characters in Messages: 19298

2023-06-07 23:21:51

🔖 Title: Ark: An Alternative Privacy-preserving Second Layer Solution
🏷️ Categories: bitcoin-dev
👥 Authors:
• jk_14 at op.pl ( @npub1dal…7r9n )
• adiabat ( @npub1sax…4xsu )
• David A. Harding ( @npub16dt…4wrd )
• Ali Sherief ( @npub1xq9…2u5f )
• ZmnSCPxj ( @npub1g5z…ms3l )
• G. Andrew Stone ( @npub1tsl…cyxz )
• Burak Keceli ( @npub136r…pezn )
🗒️ Conversation Summary: The Ark protocol enables off-chain, anonymous payments through virtual UTXOs that expire after four weeks. The protocol uses an untrusted intermediary called the Ark Service Provider to provide liquidity and charge fees. Lightning payments can be made with zero-conf coins, but there are risks. A watchtower program for Ark has been proposed to mitigate the disadvantage of requiring users to refresh their coins every few weeks.
📅 Messages Date Range: 2023-05-22 to 2023-05-28
✉️ Message Count: 15
📚 Total Characters in Messages: 55683

2023-06-07 23:21:50

🔖 Title: Full-RBF Peering Bitcoin Core v24.1 Released
🏷️ Categories: bitcoin-dev
👥 Authors: Peter Todd ( @npub1m23…2np2 )
📅 Messages Date: 2023-05-21
✉️ Message Count: 1
📚 Total Characters in Messages: 1324

2023-06-07 23:21:47

🔖 Title: ZeroSync: Introducing Validity Proofs to Bitcoin
🏷️ Categories: bitcoin-dev
👥 Authors:
• Robin Linus ( @npub1247…paq3 )
• Weiji Guo ( @npub1adg…jwsm )
🗒️ Conversation Summary: ZeroSync uses SNARKs to compress the entire blockchain into a compact proof of validity, addressing Bitcoin's scalability challenges. It enables quick bootstrapping of full nodes, trustless light clients, enhanced Lightning Network privacy, and secure cross-chain bridges. The paper also introduces zkCoins, improving privacy and throughput of token transactions. Implementing a SNARK verifier on Bitcoin's base layer is a long-term option, but Simplicity could be used to experiment on the Liquid sidechain. Establishing consensus over a particular kind of opcode is difficult due to competing proof systems with different trade-offs.
📅 Messages Date: 2023-05-12
✉️ Message Count: 3
📚 Total Characters in Messages: 6763

2023-06-07 23:21:47

🔖 Title: Seeking concept ACKs for transaction terminology BIP
🏷️ Categories: bitcoin-dev
👥 Authors: Keagan McClelland ( @npub1f2n…s289 )
📅 Messages Date: 2023-05-10
✉️ Message Count: 1
📚 Total Characters in Messages: 1814

2023-06-07 23:21:46

🔖 Title: Interactive Payment Batching w/ Payjoin
🏷️ Categories: bitcoin-dev
👥 Authors: Dan Gould ( @npub1l58…xs5k )
📅 Messages Date: 2023-05-10
✉️ Message Count: 1
📚 Total Characters in Messages: 10720

2023-06-07 23:21:40

🔖 Title: Witness script validation to reject arbitrary data
🏷️ Categories: bitcoin-dev
👥 Authors:
• Christopher Allen ( @npub19g4…t5d0 )
• Peter Todd ( @npub1m23…2np2 )
• Aymeric Vitte ( @npub15fc…5grz )
• angus ( @npub1h3r…7mc5 )
• Moth ( @npub14k7…04u6 )
🗒️ Conversation Summary: A proposal to reject witness scripts with arbitrary data between OP_FALSE and OP_IF flags to prevent network overload while still allowing taproot benefits has been suggested. However, there are concerns about controlling the value of stored information and avoiding free-riders. Some suggest a larger OP_RETURN to store tagged root of a hash-tree, but objections to putting anything on-chain have delayed this. The current flood of BRC-20 inscriptions could have used other data encoding techniques, making it pointless to block them.
📅 Messages Date Range: 2023-05-08 to 2023-05-09
✉️ Message Count: 6
📚 Total Characters in Messages: 11359

2023-06-07 23:21:24

🔖 Title: Should we as developers reject non-standard Taproot transactions from full nodes?
🏷️ Categories: bitcoin-dev, Mempool spam
👥 Authors:
• jk_14 at op.pl ( @npub1dal…7r9n )
• Weiji Guo ( @npub1adg…jwsm )
• Michael Folkson ( @npub103y…kpam )
• Ali Sherief ( @npub1xq9…2u5f )
• Keagan McClelland ( @npub1f2n…s289 )
• Aleksandr Kwaskoff ( @npub13qh…vjd3 )
• Peter Todd ( @npub1m23…2np2 )
• Erik Aronesty ( @npub1y22…taj0 )
• Luke Dashjr ( @npub1tfk…fq0n )
• Melvin Carvalho ( @npub1uvt…axrt )
• Tom Harding ( @npub1mse…mwjy )
🗒️ Conversation Summary: Bitcoin mempool congestion is caused by high volume of worthless tokens like BRC-20, threatening normal network use. Solutions are difficult and require consensus. Rejecting transactions with fees higher than outputs may prevent valid use cases and Lightning channel closures. Lack of Lightning wallets for desktop is a problem for mass adoption. Discussions on potential solutions and actions to prevent future congestion. Suggestions for spam filtration and delaying halving. A new opcode, OP_ZKP, proposed for Bitcoin's L2 to address transaction fee issues and enable more smart contracts.
📅 Messages Date Range: 2023-05-07 to 2023-05-12
✉️ Message Count: 22
📚 Total Characters in Messages: 88168

2023-06-07 23:21:17

🔖 Title: Bitcoin Core maintainers and communication on merge decisions
🏷️ Categories: bitcoin-dev
👥 Authors:
• Steve Lee ( @npub1rp7…xujr )
• Bryan Bishop ( @npub1vtw…sjpg )
• Michael Folkson ( @npub103y…kpam )
• David A. Harding ( @npub16dt…4wrd )
• alicexbt ( @npub1w30…zhn2 )
• Erik Aronesty ( @npub1y22…taj0 )
• Andrew Chow ( @npub1fgn…ak44 )
🗒️ Conversation Summary: Bitcoin Core's decision-making process for adding new maintainers has been questioned, with concerns raised about the potential inconsistency in reasons for blocking proposed maintainers. Anonymous sources expressed discomfort with Vasil being P2P maintainer, leading to his removal, but maintainers stand by the decision. Effective communication and a better process for adding maintainers are needed in the decentralized environment of Bitcoin.
📅 Messages Date Range: 2023-05-07 to 2023-05-11
✉️ Message Count: 14
📚 Total Characters in Messages: 94781

2023-06-07 23:21:14

🔖 Title: Formosa --- proposed improvement upon BIP39
🏷️ Categories: bitcoin-dev
👥 Authors:
• Keagan McClelland ( @npub1f2n…s289 )
• yurisvb at pm.me ( @npub1t6d…pjkp )
🗒️ Conversation Summary: A new password format has been proposed as a Bitcoin Improvement Proposal, which allows for themed sentences with regular grammatical structure while maintaining the same entropy and checksum as BIP39. Formosa allows for BIP39 compatibility and easy conversion between themes, with customization adding an extra layer of obscurity.
📅 Messages Date Range: 2023-05-02 to 2023-05-19
✉️ Message Count: 3
📚 Total Characters in Messages: 12587

2023-06-07 23:21:12

🔖 Title: Civ Kit: A Peer-to-Peer Electronic Market System
🏷️ Categories: bitcoin-dev
👥 Authors:
• Chris Stewart ( @npub1u03…nn03 )
• Antoine Riard ( @npub1vjz…x8dd )
🗒️ Conversation Summary: Antoine Riard and Chris Stewart discussed front-running resistance in peer-to-peer marketplaces. Mitigation strategies include duplicating offers and running boards as a federation. Front-running in Bitcoin/Civkit is not a major concern as long as the bulletin board operator and taker compete on quoting prices and providing better execution quality. It indicates active participants and liquidity in the market.
📅 Messages Date Range: 2023-05-01 to 2023-05-09
✉️ Message Count: 2
📚 Total Characters in Messages: 17309

2023-06-07 23:21:10

🔖 Title: Vaults in the MATT framework
🏷️ Categories: bitcoin-dev
👥 Authors:
• Salvatore Ingala ( @npub1lpk…74n4 )
• Michael Folkson ( @npub103y…kpam )
🗒️ Conversation Summary: Michael proposed adding new opcode functionality to existing scripts without requiring deeper introspection. Salvatore discussed the MATT proposal, which allows introspection and covenants in Bitcoin, and mentioned the ease of engineering a soft-fork for it. He also brought up Simplicity.
📅 Messages Date Range: 2023-05-01 to 2023-05-02
✉️ Message Count: 2
📚 Total Characters in Messages: 33811

2023-06-07 23:21:07

🔖 Title: Merkleize All The Things
🏷️ Categories: bitcoin-dev
👥 Authors:
• Salvatore Ingala ( @npub1lpk…74n4 )
• Johan Torås Halseth ( @npub1ppn…s2fw )
🗒️ Conversation Summary: Salvatore Ingala proposes rock-paper-scissors as an academic example for showcasing MATT. They also suggest using a Merkle tree for efficient proof in a coin pool. Johan Torås Halseth discusses the construct allowing access to embedded data and suggests using OP_CICV and OP_COCV for CoinPools. They propose further extensions and mention the use of taproot internal pubkey with "dynamic key aggregation." Removing data from the merkle tree is achieved, but removal of a public key from the taproot internal key is out of scope.
📅 Messages Date Range: 2023-05-01 to 2023-05-30
✉️ Message Count: 7
📚 Total Characters in Messages: 36149

2023-06-07 23:21:00

🔖 Title: On adaptor security (in protocols)
🏷️ Categories: bitcoin-dev
👥 Authors:
• AdamISZ ( @npub1nv7…qw2t )
• Lloyd Fournier ( @npub1khl…05yp )
🗒️ Conversation Summary: Developers Lloyd Fournier and AdamISZ discuss the security of using signature adaptors for multiparty swaps in Bitcoin transactions. While single signer adaptors can reveal a secret when a signature on a pre-defined message is published, there is confusion about their usefulness in a Bitcoin context. Multisig is necessary, but not necessarily key aggregated. A new analysis on the security of using signature adaptors for multiparty swaps has been posted on GitHub.
📅 Messages Date Range: 2023-05-01 to 2023-05-14
✉️ Message Count: 7
📚 Total Characters in Messages: 40476

2023-06-07 23:21:00

🔖 Title: On adaptor security (in protocols)
🏷️ Categories: bitcoin-dev
👥 Authors: AdamISZ ( @npub1nv7…qw2t )
📅 Messages Date: 2023-04-28
✉️ Message Count: 1
📚 Total Characters in Messages: 1736

2023-06-07 23:20:59

🔖 Title: Merkleize All The Things
🏷️ Categories: bitcoin-dev
👥 Authors: Johan Torås Halseth ( @npub1ppn…s2fw )
📅 Messages Date: 2023-04-28
✉️ Message Count: 1
📚 Total Characters in Messages: 6391

2023-06-07 23:20:55

🔖 Title: Vaults in the MATT framework
🏷️ Categories: bitcoin-dev
👥 Authors: Salvatore Ingala ( @npub1lpk…74n4 )
📅 Messages Date: 2023-04-24
✉️ Message Count: 1
📚 Total Characters in Messages: 14111

2023-06-07 23:20:53

🔖 Title: TARO Protocol metadata BIP proposal
🏷️ Categories: bitcoin-dev
👥 Authors:
• Andrew Melnychuk Oseen ( @npub1tml…yata )
• Adam Ivansky ( @npub13ae…knja )
🗒️ Conversation Summary: Adam Ivansky and Andrew Melnychuk Oseen proposed a BIP on the metadata structure of assets traded on TARO Protocol. The proposal suggests using JSON formatting for ticker, type, description, image, and minter info.
📅 Messages Date Range: 2023-04-21 to 2023-04-26
✉️ Message Count: 2
📚 Total Characters in Messages: 6512

2023-06-07 23:20:48

🔖 Title: A new Bitcoin implementation integrated with Core Lightning
🏷️ Categories: bitcoin-dev
👥 Authors:
• Kostas Karasavvas ( @npub1tqa…3e9m )
• Michael Folkson ( @npub103y…kpam )
🗒️ Conversation Summary: Michael and Kostas discussed the potential for tighter coupling between full node and Lightning node due to proposed changes to default policy and soft fork activation attempt. Michael expressed concerns about scattered default policy changes for Lightning, while Kostas questioned the complexity management of integrating Lightning into Bitcoin Core. Strong incentives and significant effort would be required for successful integration.
📅 Messages Date Range: 2023-04-18 to 2023-04-19
✉️ Message Count: 3
📚 Total Characters in Messages: 20639

2023-06-07 23:20:32

🔖 Title: Proposal to Remove BIP35 P2P 'mempool' Message
🏷️ Categories: bitcoin-dev
👥 Authors:
• Will Clark ( @npub12nc…835c )
• David A. Harding ( @npub16dt…4wrd )
🗒️ Conversation Summary: Bitcoin Core may remove the BIP35 P2P `mempool` message due to privacy concerns and inefficiency. Alternative methods are being explored. The `savemempool` RPC can be used to load the mempool directly by the client, minimizing data transfer for lite clients on metered or bandwidth-limited connections.
📅 Messages Date: 2023-04-18
✉️ Message Count: 2
📚 Total Characters in Messages: 4978

2023-06-07 23:20:23

🔖 Title: RGB protocol announcement
🏷️ Categories: bitcoin-dev
👥 Authors:
• Federico Tenga ( @npub1lkx…a3qm )
• Dr Maxim Orlovsky ( @npub1a80…pwgy )
• David A. Harding ( @npub16dt…4wrd )
🗒️ Conversation Summary: RGB v0.10 brings smart contract support to Bitcoin and Lightning after four years of development. RGB aims to build a programmability layer for Bitcoin and Lightning, enabling assets beyond tokens, such as DAOs and decentralized identities. However, there are concerns about the security of non-publishable conditional statements in multiparty protocols. RGB allows for trustless contracting beyond Bitcoin script, including user-defined sidechains and smart contracts that don't need BTC. A new blockchain, sigchain, could remove the need for pegouts.
📅 Messages Date Range: 2023-04-10 to 2023-04-19
✉️ Message Count: 7
📚 Total Characters in Messages: 59605

2023-06-07 23:20:16

🔖 Title: Using service bit 24 for utreexo signaling in testnet and signet
🏷️ Categories: bitcoin-dev
👥 Authors:
• Luke Dashjr ( @npub1tfk…fq0n )
• Peter Todd ( @npub1m23…2np2 )
• kcalvinalvin ( @npub1a9f…p7ds )
🗒️ Conversation Summary: Calvin will use service bit 24 to signal Utreexo-capable nodes on testnet and signet, with plans to release binaries for Utreexo node in the coming months.
📅 Messages Date: 2023-03-02
✉️ Message Count: 3
📚 Total Characters in Messages: 3603

2023-06-07 23:20:11

🔖 Title: Minimum fees
🏷️ Categories: bitcoin-dev
👥 Authors:
• jk_14 at op.pl ( @npub1dal…7r9n )
• Giuseppe B ( @npub1spd…z75w )
• Nadav Ivgi ( @npub1f2w…dpll )
• WMOURA ( @npub107s…y7e4 )
• vjudeu at gazeta.pl ( @npub1357…ssga )
• Andrew Melnychuk Oseen ( @npub1tml…yata )
🗒️ Conversation Summary: The group discussed the proposal for a new protocol rule, min_fees, to specify minimum fees for the following block to increase network security and incentivize higher fees. They also talked about the need for achieving equilibrium between active and passive users for network security, the serious issues of Bitcoin's long-term security budget and quantum threat, and the possibility of a hard fork to fix the flaw in Bitcoin design. The behavior of a blockchain when the coinbase drops below the fees is unknown, but federations like RSK or additional layers like LN can provide insight.
📅 Messages Date Range: 2023-03-01 to 2023-03-05
✉️ Message Count: 8
📚 Total Characters in Messages: 28633

2023-06-07 23:19:54

🔖 Title: BIP for OP_VAULT
🏷️ Categories: bitcoin-dev
👥 Authors:
• Steve Lee ( @npub1rp7…xujr )
• Brandon Black ( @npub1txg…rmss )
• Anthony Towns ( @npub17rl…9l2h )
• Andrew Melnychuk Oseen ( @npub1tml…yata )
• alicexbt ( @npub1w30…zhn2 )
• Luke Dashjr ( @npub1tfk…fq0n )
• Zac Greenwood ( @npub1gym…vff7 )
• James O'Beirne ( @npub1dpd…mz3t )
• Greg Sanders ( @npub1jdl…gh0m )
🗒️ Conversation Summary: Developers propose new opcodes and scripts for Bitcoin's OP_VAULT to improve legibility, simplify the spec, and reduce theft risk during watchtower outages. They also suggest new opcodes for conditional transactions and withdrawal authorization, while some argue against facilitating parasitical use cases of the blockchain. Discussions also touch on privacy and efficiency in Bitcoin vaults.
📅 Messages Date Range: 2023-03-01 to 2023-03-30
✉️ Message Count: 22
📚 Total Characters in Messages: 151637

2023-06-07 23:19:39

🔖 Title: Codex32
🏷️ Categories: bitcoin-dev
👥 Authors:
• Christopher Allen ( @npub19g4…t5d0 )
• David A. Harding ( @npub16dt…4wrd )
• Pavol Rusnak ( @npub1wcc…hnuq )
• Peter Todd ( @npub1m23…2np2 )
• Russell O'Connor ( @npub1dw8…plrw )
• Andrew Poelstra ( @npub1ae2…5t04 )
🗒️ Conversation Summary: Ancient scrolls reveal a secret society devoted to computation in 200 BC. Several Bitcoin Improvement Proposals (BIPs) have been proposed, including a new secret sharing system and a new seed phrase scheme. The proposals aim to simplify hand computation for users and offer benefits such as a more compact encoding and the ability to verify the integrity of each share independently. However, some proposals do not support passphrases or hardening. A potential attack on seed recovery for Bitcoin wallets was discussed, with no current solution available.
📅 Messages Date Range: 2023-02-16 to 2023-02-23
✉️ Message Count: 15
📚 Total Characters in Messages: 122879

2023-06-07 23:19:38

🔖 Title: BIP for OP_VAULT
🏷️ Categories: bitcoin-dev
👥 Authors: James O'Beirne ( @npub1dpd…mz3t )
📅 Messages Date: 2023-02-13
✉️ Message Count: 1
📚 Total Characters in Messages: 1460

2023-06-07 23:19:33

🔖 Title: Testing censorship resistance of bitcoin p2p network
🏷️ Categories: bitcoin-dev
👥 Authors:
• Peter Todd ( @npub1m23…2np2 )
• Andrew Poelstra ( @npub1ae2…5t04 )
• vjudeu at gazeta.pl ( @npub1357…ssga )
• alicexbt ( @npub1w30…zhn2 )
• Russell O'Connor ( @npub1dw8…plrw )
🗒️ Conversation Summary: Bitcoin developers discuss censorship resistance and the need for tools to test it. The debate on discouraging upgradable NOPs in Bitcoin script continues, with suggestions to use commitments instead of OP_RETURN. Filtering script fragments to make inscription scripts "plausible" and increase their space cost is proposed, but banning legitimate use cases is warned against. A Python script is shared for testing purposes to list peers, broadcast transactions, and ban peers that don't relay transactions.
📅 Messages Date Range: 2023-02-13 to 2023-02-22
✉️ Message Count: 10
📚 Total Characters in Messages: 26644

2023-06-07 23:19:24

🔖 Title: Unenforceable fee obligations in multiparty protocols with Taproot inputs
🏷️ Categories: bitcoin-dev
👥 Authors:
• Michael Folkson ( @npub103y…kpam )
• Antoine Riard ( @npub1vjz…x8dd )
• Anthony Towns ( @npub17rl…9l2h )
• Yuval Kogman ( @npub1hkf…8g7t )
• Lloyd Fournier ( @npub1khl…05yp )
• Peter Todd ( @npub1m23…2np2 )
• Nadav Ivgi ( @npub1f2w…dpll )
• Andrew Poelstra ( @npub1ae2…5t04 )
• Russell O'Connor ( @npub1dw8…plrw )
🗒️ Conversation Summary: A bug in Taproot allows the same Tapleaf to be repeated multiple times, incurring different Tapfee rates. Mitigations include knowing the entire Taptree, implementing RBF, and signing the entire tapbranch instead of the tapleaf. Miniscript can help prevent an attack in multiparty transactions, and uncompressed keys are banned.
📅 Messages Date Range: 2023-02-07 to 2023-02-15
✉️ Message Count: 18
📚 Total Characters in Messages: 59089

2023-06-07 23:19:22

🔖 Title: A proposal for Full RBF to not exclude Zero Conf use case
🏷️ Categories: bitcoin-dev
👥 Authors:
• Daniel Lipshitz ( @npub1t97…g2yy )
• Peter Todd ( @npub1m23…2np2 )
🗒️ Conversation Summary: Peter Todd warns against sharing bitcoin transaction data with third-party companies like Chainalysis due to the risk of data being sold or leaked. Meanwhile, a company claims that over 90% of its clients use different AML transaction analysis service providers for transactions deposited on their platform and they do not have any KYC/AML information or telephone number on who is sending Bitcoin.
📅 Messages Date Range: 2023-02-04 to 2023-02-06
✉️ Message Count: 2
📚 Total Characters in Messages: 3497

2023-06-07 23:19:20

🔖 Title: Ordinal Inscription Size Limits
🏷️ Categories: bitcoin-dev
👥 Authors:
• Claus Ehrenberg ( @npub1a8c…3wff )
• Aymeric Vitte ( @npub15fc…5grz )
• Erik Aronesty ( @npub1y22…taj0 )
• Melvin Carvalho ( @npub1uvt…axrt )
• Kostas Karasavvas ( @npub1tqa…3e9m )
🗒️ Conversation Summary: Bitcoin developers discussed the storage of unlimited NFT content on the blockchain, with concerns about future disk usage and potential malicious content. Suggestions were made to impose size limits or charge premiums for storage. Some developers praised the ordinal scheme for its potential use in linking real-world property ownership to the blockchain, while others argued against storing large data and suggested using third-party validation for accuracy.
📅 Messages Date Range: 2023-02-03 to 2023-02-07
✉️ Message Count: 6
📚 Total Characters in Messages: 10757

2023-06-07 23:19:16

🔖 Title: Ephemeral Anchors: Fixing V3 Package RBF againstpackage limit pinning
🏷️ Categories: bitcoin-dev
👥 Authors:
• Peter Todd ( @npub1m23…2np2 )
• Greg Sanders ( @npub1jdl…gh0m )
🗒️ Conversation Summary: Peter Todd and Greg Sanders discuss the proposal for Ephemeral Anchors, which suggests using OP_TRUE instead of OP_2 in test vectors. Peter Todd argues that OP_TRUE is a better alternative as it avoids malleability issues and ensures standardness rules are followed. Greg Sanders is concerned about changing test vectors, but ultimately agrees with the proposal to use OP_TRUE. Todd shares a link to fixed tests for the OP_TRUE case on Github.
📅 Messages Date Range: 2023-02-02 to 2023-02-04
✉️ Message Count: 9
📚 Total Characters in Messages: 9520

2023-06-07 23:18:53

🔖 Title: Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
🏷️ Categories: bitcoin-dev
👥 Authors:
• Christopher Allen ( @npub19g4…t5d0 )
• Claus Ehrenberg ( @npub1a8c…3wff )
• Rijndael ( @npub1zhs…3hc5 )
• Anthony Towns ( @npub17rl…9l2h )
• Aymeric Vitte ( @npub15fc…5grz )
• Peter Todd ( @npub1m23…2np2 )
• Andrew Poelstra ( @npub1ae2…5t04 )
• Russell O'Connor ( @npub1dw8…plrw )
• Kostas Karasavvas ( @npub1tqa…3e9m )
🗒️ Conversation Summary: The debate is on the most efficient way to place 64 bytes into the Bitcoin blockchain, with suggestions including traditional OP_RETURN and spent taproot transactions. The current standard for OP_RETURN in Bitcoin is a maximum of 80 bytes and one output per transaction, but some suggest increasing the size of OP_RETURN to support a hash, signature, and metadata. There is ongoing discussion on changing the OP_RETURN size in Bitcoin, but ultimately requires code changes and community consensus for implementation.
📅 Messages Date Range: 2023-01-31 to 2023-02-18
✉️ Message Count: 34
📚 Total Characters in Messages: 75198

2023-06-07 23:18:50

🔖 Title: Reference example bech32m address for future segwit versions
🏷️ Categories: bitcoin-dev
👥 Authors:
• David A. Harding ( @npub16dt…4wrd )
• Greg Sanders ( @npub1jdl…gh0m )
🗒️ Conversation Summary: A proposal has been made to reserve a canonical example of future segwit addresses to exercise wallets supporting bech32m without interfering with future soft forks. However, sending funds to future segwit versions may be risky as most exchanges won't enable it. Updating to new versions should be easy and popular open source libraries should support it.
📅 Messages Date Range: 2023-01-30 to 2023-01-31
✉️ Message Count: 3
📚 Total Characters in Messages: 8149

2023-06-07 23:18:42

🔖 Title: Wallet policies for descriptor wallets
🏷️ Categories: bitcoin-dev
👥 Authors:
• Salvatore Ingala ( @npub1lpk…74n4 )
• darosior ( @npub1pj9…22xp )
🗒️ Conversation Summary: The importance of secure usage guidelines for signing devices was discussed, with a suggestion to simplify the UX flow for Bitcoin Script verification by showing the "semantic policy" instead of the actual Miniscript. Concerns about potential malware attacks were raised, but a possible solution was proposed.
📅 Messages Date Range: 2023-01-23 to 2023-01-24
✉️ Message Count: 2
📚 Total Characters in Messages: 25479

2023-06-07 23:18:41

🔖 Title: Wallet vaults with pre-signed transactions but no ephemeral keys
🏷️ Categories: bitcoin-dev
👥 Authors:
• darosior ( @npub1pj9…22xp )
• Billy Tetrud ( @npub1xqc…cnns )
🗒️ Conversation Summary: Billy Tetrud suggests creating an N-of-N multisig address and pre-signing transactions with N-1 keys to create a wallet vault without key deletion. Darosior mentions that this method has advantages but can be improved with covenants. Tetrud proposes adding timelocked spend paths to the address to solve this issue.
📅 Messages Date Range: 2023-01-23 to 2023-01-31
✉️ Message Count: 3
📚 Total Characters in Messages: 12976

2023-06-07 23:18:40

🔖 Title: Serverless Payjoin
🏷️ Categories: bitcoin-dev
👥 Authors: Dan Gould ( @npub1l58…xs5k )
📅 Messages Date: 2023-01-22
✉️ Message Count: 1
📚 Total Characters in Messages: 5324

2023-06-07 23:18:34

🔖 Title: A proposal for Full RBF to not exclude Zero Conf use case
🏷️ Categories: bitcoin-dev
👥 Authors:
• Erik Aronesty ( @npub1y22…taj0 )
• Daniel Lipshitz ( @npub1t97…g2yy )
• Peter Todd ( @npub1m23…2np2 )
🗒️ Conversation Summary: GAP600 offers an API service for merchants to accept 0-conf transactions without AML/KYC, but privacy concerns arise as they collect data on real-world entities paying for their service. Full-RBF implementation is suggested to stop data collection. GAP600 apologizes for inaccurate initial numbers and estimates significant numbers of merchants and service providers who enable 0-conf on Bitcoin outside of their platform.
📅 Messages Date Range: 2023-01-13 to 2023-01-17
✉️ Message Count: 5
📚 Total Characters in Messages: 26646

2023-06-07 23:18:33

🔖 Title: Using OP_VAULT to improve DLCs
🏷️ Categories: bitcoin-dev
👥 Authors:
• Billy Tetrud ( @npub1xqc…cnns )
• Ben Carman ( @npub17lt…7hwm )
🗒️ Conversation Summary: Ben Carman proposed using OP_UNVAULT with a burn address and no delay period to create output restrictions, similar to CTV. This could save computational costs but use more blockchain space. Billy Tetrud suggested using OP_UNVAULT as a general CTV-like covenant with arbitrary conditions set on spending the utxo to the "recovery address."
📅 Messages Date Range: 2023-01-12 to 2023-01-19
✉️ Message Count: 2
📚 Total Characters in Messages: 6324

2023-06-07 23:18:26

🔖 Title: Why Full-RBF Makes DoS Attacks on Multiparty Protocols Significantly More Expensive
🏷️ Categories: bitcoin-dev
👥 Authors:
• alicexbt ( @npub1w30…zhn2 )
• David A. Harding ( @npub16dt…4wrd )
• Peter Todd ( @npub1m23…2np2 )
🗒️ Conversation Summary: The conversation discusses the use of Full-RBF to prevent DoS attacks on multi-party protocols caused by double-spending inputs with low-fee transactions. While some argue that Full-RBF is unnecessary and conflict monitoring systems can provide the same benefits, others propose two methods for implementing conflict monitoring in decentralized coinjoin implementations. The impact of Full-RBF on different coinjoin implementations, including Wasabi's privacy issues and Whirlpool's lack of BIP 125 RBF signaling, is also discussed.
📅 Messages Date Range: 2023-01-09 to 2023-01-13
✉️ Message Count: 11
📚 Total Characters in Messages: 41439

2023-06-07 23:17:57

🔖 Title: Pseudocode for robust tail emission
🏷️ Categories: bitcoin-dev
👥 Authors:
• jk_14 at op.pl ( @npub1dal…7r9n )
• Billy Tetrud ( @npub1xqc…cnns )
• Peter Todd ( @npub1m23…2np2 )
📅 Messages Date Range: 2022-12-23 to 2022-12-30
✉️ Message Count: 4
📚 Total Characters in Messages: 9495

2023-06-07 23:17:56

🔖 Title: onion addresses to try
🏷️ Categories: bitcoin-dev, At least 17% of Bitcoin Core 24.x listening nodes are running full-rbf
👥 Authors:
• Vasil Dimov ( @npub1g4h…p0tv )
• Peter Todd ( @npub1m23…2np2 )
📅 Messages Date: 2022-12-23
✉️ Message Count: 2
📚 Total Characters in Messages: 1624

2023-06-07 23:17:55

🔖 Title: At least 17% of Bitcoin Core 24.x listening nodes are running full-rbf
🏷️ Categories: bitcoin-dev
👥 Authors: Peter Todd ( @npub1m23…2np2 )
📅 Messages Date: 2022-12-23
✉️ Message Count: 1
📚 Total Characters in Messages: 3669

2023-06-07 23:17:50

🔖 Title: Bitcoin Core 24.0.1 Released
🏷️ Categories: bitcoin-dev
👥 Authors:
• Matt Corallo ( @npub1e46…xmcu )
• Michael Ford ( @npub1zc4…d4kg )
• Peter Todd ( @npub1m23…2np2 )
📅 Messages Date: 2022-12-13
✉️ Message Count: 3
📚 Total Characters in Messages: 35595

2023-06-07 23:17:48

🔖 Title: Full-RBF Peering Bitcoin Core v24.0.1 Released
🏷️ Categories: bitcoin-dev
👥 Authors: Peter Todd ( @npub1m23…2np2 )
📅 Messages Date: 2022-12-12
✉️ Message Count: 1
📚 Total Characters in Messages: 1236

2023-06-07 23:17:41

🔖 Title: A proposal for Full RBF to not exclude Zero Conf use case
🏷️ Categories: bitcoin-dev
👥 Authors:
• Lucas Ontivero ( @npub16q9…qufk )
• Yuval Kogman ( @npub1hkf…8g7t )
• John Carvalho ( @npub1qg5…qm4r )
• Peter Todd ( @npub1m23…2np2 )
• Erik Aronesty ( @npub1y22…taj0 )
• Daniel Lipshitz ( @npub1t97…g2yy )
📅 Messages Date Range: 2022-12-11 to 2022-12-18
✉️ Message Count: 13
📚 Total Characters in Messages: 32874

2023-06-07 23:17:36

🔖 Title: Rethinking “Incentive Compatibility” Within the Bitcoin Protocol
🏷️ Categories: bitcoin-dev
👥 Authors:
• Daniel Edgecumbe ( @npub19cn…shne )
• John Carvalho ( @npub1qg5…qm4r )
• Michael Folkson ( @npub103y…kpam )
📅 Messages Date Range: 2022-12-10 to 2022-12-11
✉️ Message Count: 5
📚 Total Characters in Messages: 40683

2023-06-07 23:17:35

🔖 Title: Nondeterministic Programming and Hints in Bitcoin Script
🏷️ Categories: bitcoin-dev
👥 Authors: Robin Linus ( @npub1247…paq3 )
📅 Messages Date: 2022-12-07
✉️ Message Count: 1
📚 Total Characters in Messages: 2738

2023-06-07 23:17:33

🔖 Title: bitcoin-dev Digest, Vol 91, Issue 5
🏷️ Categories: bitcoin-dev
👥 Authors:
• Antoine Riard ( @npub1vjz…x8dd )
• John Carvalho ( @npub1qg5…qm4r )
📅 Messages Date Range: 2022-12-05 to 2022-12-06
✉️ Message Count: 2
📚 Total Characters in Messages: 20685

2023-06-07 23:17:28

🔖 Title: Zero-conf apps in immediate danger (angus)
🏷️ Categories: bitcoin-dev, Opt-in full-RBF
👥 Authors:
• Anthony Towns ( @npub17rl…9l2h )
• John Carvalho ( @npub1qg5…qm4r )
• angus ( @npub1h3r…7mc5 )
• ZmnSCPxj ( @npub1g5z…ms3l )
• Erik Aronesty ( @npub1y22…taj0 )
📅 Messages Date Range: 2022-12-05 to 2022-12-13
✉️ Message Count: 6
📚 Total Characters in Messages: 30209

2023-06-07 23:17:17

🔖 Title: Announcement: Full-RBF Miner Bounty
🏷️ Categories: bitcoin-dev
👥 Authors:
• Michael Folkson ( @npub103y…kpam )
• Rijndael ( @npub1zhs…3hc5 )
• Anthony Towns ( @npub17rl…9l2h )
• Peter Todd ( @npub1m23…2np2 )
• El_Hoy ( @npub184x…epad )
• 0xB10C ( @npub12kg…09h5 )
• Erik Aronesty ( @npub1y22…taj0 )
• Greg Sanders ( @npub1jdl…gh0m )
📅 Messages Date Range: 2022-12-05 to 2022-12-13
✉️ Message Count: 14
📚 Total Characters in Messages: 76233

2023-06-07 23:17:16

🔖 Title: Fwd: Zero-conf apps in immediate danger
🏷️ Categories: bitcoin-dev, Opt-in full-RBF
👥 Authors:
• Antoine Riard ( @npub1vjz…x8dd )
• Peter Todd ( @npub1m23…2np2 )
📅 Messages Date Range: 2022-12-02 to 2022-12-06
✉️ Message Count: 2
📚 Total Characters in Messages: 6421

2023-06-07 23:17:08

🔖 Title: Merkleize All The Things
🏷️ Categories: bitcoin-dev
👥 Authors:
• Salvatore Ingala ( @npub1lpk…74n4 )
• Billy Tetrud ( @npub1xqc…cnns )
📅 Messages Date Range: 2022-12-01 to 2022-12-13
✉️ Message Count: 2
📚 Total Characters in Messages: 10454