Sebastian Falbesoner, PortlandHODL, Tadge Dryja, and Antoine Poinsot joined Optech to discuss Newsletter #379: - ECDSA signature validation in OpenSSL vs. libsecp256k1 - Multiple discussions about restricting data - Post-quantum signature aggregation - Native STARK proof verification in Bitcoin Script - BIP54 implementation and test vectors - And more You can listen on our website: Fountain: Spotify: Apple Podcasts:
Bitcoin Optech newsletter #379 is here: - shares an analysis comparing the historical performance of the OpenSSL and libsecp256k1 libraries - highlights multiple discussions about restricting data - summarizes a proposed post-quantum signature aggregation opcode - summarizes an idea for STARK proof verification in Bitcoin Script - updates progress on BIP54's consensus cleanup - Optech Newsletter #379 Podcast Sebastian Falbesoner posted to Delving about comparing the performance of ECDSA signature validation between OpenSSL and libsecp256k1 over the last decade... Multiple conversations examined ideas to change the limits of various fields in consensus... Tadge Dryja posted to the Bitcoin-Dev mailing list a proposal for an OP_CHECKINPUTVERIFY (OP_CIV) opcode that enables a locking script to commit to a specific UTXO being spent in the same transaction... Abdelhamid Bakhta posted to Delving Bitcoin a detailed proposal for a new tapscript opcode OP_STARK_VERIFY which would enable the verification of a specific variant of STARK proof in Bitcoin Script... Antoine Poinsot posted to the Bitcoin-Dev mailing list an update on his consensus cleanup work on BIP54... 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!
Mark “Murch” Erhardt and Mike Schmidt discuss Newsletter #378: - Disclosure of four low-severity vulnerabilities in Bitcoin Core - Q&A from Bitcoin Stack Exchange including questions on datacarriersize, OP_TEMPLATEHASH and others - And more You can listen on our website: Fountain: Spotify: Apple Podcasts:
Bitcoin Optech newsletter #378 is here: - announces four vulnerabilities affecting older versions of the Bitcoin Core full node - summarizes popular Q&A from Stack Exchange - Optech Newsletter #378 Podcast Antoine Poinsot recently posted to the Bitcoin-Dev mailing list four Bitcoin Core security advisories for low-severity vulnerabilities that were fixed in Bitcoin Core 30.0... Selected Q&A from Bitcoin Stack Exchange: - Why was -datacarriersize redefined in 2022, and why was the 2023 proposal to expand it not merged? - What is the smallest valid transaction that can be included in a block? - Why does Bitcoin Core continue to give witness data a discount even when it is used for inscriptions? - The ever-growing Bitcoin blockchain size? - I read that OP_TEMPLATEHASH is a variant of OP_CTV. How do they differ? 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!
Francesco Madonna and supertestnet joined Optech to discuss Newsletter #376: - Continued discussion of block template sharing - B-SSL a Secure Bitcoin Signing Layer - Bitcoin Core 30.0 - And more You can listen on our website: Fountain: Spotify: Apple Podcasts:
Bitcoin Optech newsletter #376 is here: - shares an update on the proposal for nodes to share their current block template - summarizes a paper outlining a covenant-less vault construction - Bitcoin Core 30.0 release - Optech Newsletter #376 Podcast Discussion continued around the proposal for full node peers to occasionally send each other their current template for the next block using compact block relay encoding... Francesco Madonna posted to Delving Bitcoin about a concept which is a covenant-less vault model using taproot, OP_CHECKSEQUENCEVERIFY, and OP_CHECKLOCKTIMEVERIFY... Bitcoin Core 30.0 is the latest version release of the network’s predominant full node. Its release notes describe several significant improvements... 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!