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!
Yesterday @Murch and @schmidty had on Jonas Nick and Salvatore Ingala to cover Newsletter #351: - The DahLIAS Interactive aggregate signatures compatible with secp256k1 - Standardized backup for wallet descriptors - Stack Exchange questions including: half-aggregated schnorr signatures, OP_RETURN, reorg statistics, and more Catch up:
Bitcoin Optech newsletter #351 is here: - announces a new aggregate signature protocol compatible with secp256k1 - describes a standardized backup scheme for wallet descriptors - summarizes popular Q&A from Stack Exchange - Optech Newsletter #351 Recap Jonas Nick, Tim Ruffing, Yannick Seurin posted to the Bitcoin-Dev mailing list to announce a paper they’ve written about creating 64-byte aggregate signatures compatible with the cryptographic primitives already used by Bitcoin... Salvatore Ingala posted to Delving Bitcoin a summary of various tradeoffs related to backing up wallet descriptors and a proposed scheme that should be useful for many different types of wallets, including those using complex scripts... Selected Q&A from Bitcoin Stack Exchange: - Practicality of half-aggregated schnorr signatures? - What’s the largest size OP_RETURN payload ever created? - Non-LN explanation of pay-to-anchor? - Up-to-date statistics about chain reorganizations? - Are Lightning channels always P2WSH? - Child-pays-for-parent as a defense against a double spend? - What values does CHECKTEMPLATEVERIFY hash? - Why can’t Lightning nodes opt to reveal channel balances for better routing efficiency? - Does post-quantum require hard fork or soft fork? 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!
Earlier today @Murch and @schmidty spoke with Niklas Gögge about Newsletter #350: - Fuzz testing tool for Bitcoin nodes - Message signing - PSBTv2 explorer - MPC Library - Bitcoin Core 29.0 - And more! Catch up:
Last week @Murch and @David A. Harding spoke with Sebastian Falbesoner, Ruben Somsen, and Abubakar Sadiq Ismail about Newsletter #349: - IBD using SwiftSync - Bitcoin Core fee estimation - And more! Catch up:
In Podcast #348 we had on Jonas Nick, Jameson Lopp, Steven Roose, Gregory Sanders, and Salvatore Ingala: - secp256k1lab - discussions about quantum computer theft and resistance - discussions about a CTV+CSFS soft fork - OP_CHECKCONTRACTVERIFY - Consensus cleanup draft BIP - And more! Catch up:
Bitcoin Optech newsletter #349 is here: - describes a proposal for speeding up Bitcoin Core initial block download, with a proof-of-concept implementation that shows a roughly 5x speed up compared to Bitcoin Core’s defaults - recaps the "Stricter internal handling of invalid blocks " PR Review Meeting - Optech Newsletter #349 Recap on Riverside Sebastian Falbesoner posted to Delving Bitcoin a sample implementation and performance results for SwiftSync, an idea proposed by Ruben Somsen during a recent Bitcoin Core developers meeting and later posted to the mailing list... 'Add Fee rate Forecaster Manager' is a PR by ismaelsadeeq that upgrades the transaction fee forecasting (fee estimation) logic... 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 #348 is here: - links to an educational implementation of elliptic curve cryptography for Bitcoin’s secp256k1 curve - Changing consensus covering: discussions about quantum computer theft and resistance, a CTV+CSFS soft fork, OP_CHECKCONTRACTVERIFY semantics, and a consensus cleanup draft BIP - Optech Newsletter #348 Recap on Riverside Sebastian Falbesoner, Jonas Nick, and Tim Ruffing posted to the Bitcoin-Dev mailing list to announce a Python implementation of various functions related to the cryptography used in Bitcoin... Several conversations examined how Bitcoiners could respond to quantum computers becoming powerful enough to allow stealing bitcoins... Several conversations examined various aspects of soft forking in the OP_CHECKTEMPLATEVERIFY (CTV) and OP_CHECKSIGFROMSTACK (CSFS) opcodes... Salvatore Ingala posted to Delving Bitcoin to describe the semantics of the proposed OP_CHECKCONTRACTVERIFY (CCV) opcode, link to a first draft BIP, and link to an implementation draft for Bitcoin Core... Antoine Poinsot posted to the Bitcoin-Dev mailing list a link to a draft BIP he’s written for the consensus cleanup soft fork proposal. It includes several fixes... 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!