Earlier this week @Murch and @Sjors Provoost discussed Newsletter #352: - Cluster linearization techniques for cluster mempool - Increasing or removing Bitcoin Core’s OP_RETURN size limit - Bitcoin Core removing legacy wallets - And more... Catch up:
Bitcoin Optech newsletter #352 is here: - links to comparisons between different cluster linearization techniques - briefly summarizes discussion about increasing or removing Bitcoin Core’s OP_RETURN size limit - Optech Newsletter #352 Recap Pieter Wuille posted to Delving Bitcoin about some of the fundamental tradeoffs between three different cluster linearization techniques, following up with benchmarks of implementations of each... In a thread on Bitcoin-Dev, several developers discussed changing or removing Bitcoin Core’s default limit for OP_RETURN data carrier outputs. A subsequent Bitcoin Core pull request saw additional discussion... Bitcoin Optech will host an audio recap discussion of this newsletter on Riverside.fm Tuesday at 16:30 UTC. Join us to discuss or ask questions!
Bitcoin Optech newsletter #347 is here: - describes upfront and hold fees in LN based on burnable outputs - summarizes discussion about testnets 3 and 4 - announces a plan to relay certain transactions containing taproot annexes - summarizes popular Q&A from Stack Exchange - Bitcoin Core 29.0rc2 - Optech Newsletter #347 Recap John Law posted to Delving Bitcoin the summary of a paper he’s written about a protocol nodes can use to charge two additional types of fees for forwarding payments... Sjors Provoost posted to the Bitcoin-Dev mailing list to ask whether anyone was still using testnet3 now that testnet4 has been available for about six months... Peter Todd announced to the Bitcoin-Dev mailing list his plan to update his Bitcoin Core-based node, Libre Relay, to begin relaying transactions containing taproot annexes if they follow particular rules... Selected Q&A from Bitcoin Stack Exchange: - Why is the witness commitment optional? - Can all consensus valid 64 byte transactions be (third party) malleated to change their size? - How long does it take for a transaction to propagate through the network? - Utility of longterm fee estimation - Why are two anchor outputs are used in the LN? - Why are there no BIPs in the 2xx range? - Why doesn’t Bech32 use the character “b”? - Bech32 error detection and correction reference implementation - How to safely spend/burn dust? - How is the refund transaction in Asymmetric Revocable Commitments constructed? - Which applications use ZMQ with Bitcoin Core? Bitcoin Core 29.0rc2 is a release candidate for the next major version of the network’s predominate full node. Please see the version 29 testing guide. Bitcoin Optech will host an audio recap discussion of this newsletter on Riverside.fm Tuesday at 15:30 UTC. Join us to discuss or ask questions!
Bitcoin Optech newsletter #345 is here: - looks at an analysis of P2P traffic experienced by a typical full node - summarizes research into LN pathfinding - describes a new approach for creating probabilistic payments - recaps the "Stricter internal handling of invalid blocks " PR Review Meeting - Optech Newsletter #345 Recap on Riverside Developer Virtu posted to Delving Bitcoin an analysis of the network traffic generated and received by his node in four different modes: initial block download (IBD), non-listening (outbound connections only), non-archival (pruned) listening, and archival listening... Sindura Saraswathi posted to Delving Bitcoin about research she conducted with Christian Kümmerle about finding optimal paths between LN nodes for sending payments in a single part... Robin Linus replied to the Delving Bitcoin thread about probabilistic payments with a conceptually simple script that allows two parties to each commit to an arbitrary amount of entropy that can later be revealed and xored together, to produce a value that can be used to determine which one of them receives a payment... 'Stricter internal handling of invalid blocks' is a PR by mzumsande that improves the correctness of two non-consensus-critical and expensive-to-calculate validation fields by immediately updating them when a block is marked as invalid... Bitcoin Optech will host an audio recap discussion of this newsletter on Riverside.fm Tuesday at 15:30 UTC. Join us to discuss or ask questions!
Bitcoin Optech newsletter #344 is here: - announces the disclosure of a vulnerability affecting old versions of LND - summarizes a discussion about the Bitcoin Core Project’s priorities - Changing consensus covering: Bitcoin Forking Guide, BIP360 pay-to-quantum-resistant-hash (P2QRH) updates, and Private block template marketplace to prevent centralizing MEV - Optech Newsletter #344 Recap on Riverside Matt Morehouse posted to Delving Bitcoin to announce the responsible disclosure of a vulnerability that affected LND versions before 0.18... Several blog posts by Antoine Poinsot about the future of the Bitcoin Core project were linked in a thread on Delving Bitcoin... Anthony Towns announced to Delving Bitcoin a guide to how to build community consensus for changes to Bitcoin’s consensus rules... Developer Hunter Beast posted an update on his research into quantum resistance for BIP360 to the Bitcoin-Dev mailing list... Matt Corallo and developer 7d5x9 posted to Delving Bitcoin about allowing parties to bid in public markets for selected space within miner block templates... Bitcoin Optech will host an audio recap discussion of this newsletter on Riverside.fm Tuesday at 15:30 UTC. Join us to discuss or ask questions!
Last week Bastien Teinturier Joost Jager joined @David A. Harding and @npub1zsu6...k4em for #342: - settling channels w/o extra UTXOs - LN QoS flag - Ark SDK, Zaprite, Iris, Sparrow, Scure, py and rust bitcoinkernel libs, cbip32, Loop MuSig2 Catch up:
Bitcoin Optech newsletter #343 is here: - summarizes a post about having full nodes ignore transactions that are relayed without being requested first - summarizes popular Q&A from Stack Exchange - Optech Newsletter #343 Recap on Riverside Antoine Riard posted to Bitcoin-Dev two draft BIPs that would allow a node to signal that it will no longer accept tx messages that it had not requested using an inv message, called unsolicited transactions... Selected Q&A from Bitcoin Stack Exchange: - What’s the rationale for how the loadtxsoutset RPC is set up? - Are there pinning attacks that RBF rule #3 makes impossible? - Unexpected locktime values - Why is it necessary to reveal a bit in a script path spend and check that it matches the parity of the Y coordinate of Q? - Why does Bitcoin Core use checkpoints?? - How does Bitcoin Core handle long reorgs? - What is discard feerate? - Policy to miniscript compiler Bitcoin Optech will host an audio recap discussion of this newsletter on Riverside.fm Tuesday at 15:30 UTC. Join us to discuss or ask questions!