Weekly delight to read the optech newsletter and listen to the podcast.
Mandatory for any sufficiently advanced Bitcoin wizard.
Bitcoin Optech newsletter #339 is here:
- describes a vulnerability affecting older versions of LDK
- looks at a newly disclosed aspect of a vulnerability originally published in 2023
- summarizes renewed discussion about compact block reconstruction statistics
- summarizes popular Q&A from Stack Exchange
- Optech Newsletter #339 Recap on Riverside
Matt Morehouse posted to Delving Bitcoin to disclose a vulnerability affecting LDK that he responsibly disclosed and which was fixed in LDK version 0.1...
Antoine Riard posted to the Bitcoin-Dev mailing list to disclose an additional vulnerability possible with the replacement cycling attack he originally publicly disclosed in 2023...
Developer 0xB10C posted to Delving Bitcoin updated stats on the frequency at which his Bitcoin Core nodes needed to request additional transactions to perform compact block reconstruction...
Selected Q&A from Bitcoin Stack Exchange:
- Who uses or wants to use PSBTv2 (BIP370)?
- In the bitcoin’s block genesis, which parts can be filled arbitrarily?
- Lightning force close detection
- Is a segwit-formatted transaction with all inputs of non-witness program type valid?
- P2TR Security Question
- What exactly is being done today to make Bitcoin “quantum-safe”?
- What are the harmful effects of a shorter inter-block time?
- Could proof-of-work be used to replace policy rules?
- How does MuSig work in real Bitcoin scenarios?
- How does the -blocksxor switch that obfuscates the blocks.dat files work?
- How does the related key attack on Schnorr signatures work?
https://bitcoinops.org/en/newsletters/2025/01/31/
Bitcoin Optech will host an audio recap discussion of this newsletter with special guest Matt Morehouse on Riverside.fm Tuesday at 15:30 UTC. Join us to discuss or ask questions!
Weekly delight to read the optech newsletter and listen to the podcast.
Mandatory for any sufficiently advanced Bitcoin wizard.
The focus ad nauseam on core architecture, ibd, and mempool policy may be prudent. But I would like to see discussion around the merits of narrowly scoped op codes that enable robust exit bandwidth from higher layers to base chain
They recently announced a monthly section on consensus changes.
I read and listen just to larp as one