Bitcoin Optech newsletter #337 is here: - summarizes continued discussion about rewarding pool miners with tradeable ecash shares - describes a new proposal for enabling offchain resolution of DLCs - Optech Newsletter #337 Recap on Riverside Discussion continued since our previous summary of a Delving Bitcoin thread about paying pool miners with ecash for each share they submitted... Developer conduition posted to the DLC-dev mailing list about a contract protocol that allows an offchain spend of the funding transaction signed by both parties to create multiple DLCs... 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 discussed Newsletter #336 with Abubakar Sadiq, Gregory Sanders, and Daniel Roberts: - Double coinbase reservation - LN-Symmetry and more... Catch up:
Bitcoin Optech newsletter #336 is here: - describes a potential change to Bitcoin Core affecting miners - summarizes discussion about creating contract-level relative timelocks - discusses a proposal for an LN-Symmetry variant with optional penalties - Optech Newsletter #336 Recap on Riverside Abubakar Sadiq Ismail posted to Delving Bitcoin about a bug discovered in 2021 by Antoine Riard that results in nodes reserving 2,000 vbytes in block templates for coinbase transactions rather than the intended 1,000 vbytes... Gregory Sanders posted to Delving Bitcoin about finding a solution for a complication he discovered about a year ago when creating a proof-of-concept implementation of LN-Symmetry... Daniel Roberts posted to Delving Bitcoin about preventing a malicious channel counterparty (Mallory) from being able to delay channel settlement by deliberately broadcasting old states at a higher feerate than an honest counterparty (Bob) is paying for confirmation of the final state... Bitcoin Optech will host an audio recap discussion of this newsletter with special guests Abubakar Sadiq Ismail and Gregory Sanders on Riverside.fm Tuesday at 15:30 UTC. Join us to discuss or ask questions!
Yesterday @David A. Harding and @schmidty were joined by Yuval Kogman, Jeremy Rubin, and Steve Myers to discuss Newsletter #335: - Attacks on centralized coinjoin - ChillDKG - Changing consensus - BDK 1.0.0 Catch up:
Bitcoin Optech would like your feedback! Let us know in this survey what parts of the newsletter and website are valuable for you and how we can make Optech an even better Bitcoin technical resource.
Bitcoin Optech newsletter #335 is here: - links to information about longstanding deanonymization vulnerabilities in software using centralized coinjoin protocols - summarizes an update to a draft BIP about the ChillDKG distributed key generation protocol compatible with scriptless threshold signing - adds a new monthly section summarizing proposals and discussion about changing Bitcoin’s consensus rules - Optech Newsletter #335 Recap on Riverside Yuval Kogman posted to the Bitcoin-Dev mailing list details about several privacy-reducing vulnerabilities in the centralized coinjoin protocols used by current versions of the Wasabi and Ginger wallets, plus past versions of the Samourai, Sparrow, and Trezor Suite software wallets... Tim Ruffing and Jonas Nick posted to the Bitcoin-Dev mailing list a link to the current draft BIP for ChillDKG, which describes a distributed key generation protocol compatible with FROST scriptless threshold signatures for Bitcoin... Changing consensus: - CTV enhancement opcodes - Adjusting difficulty beyond 256 bits - Transitory soft forks for cleanup soft forks - Quantum computer upgrade path - Consensus cleanup timewarp grace period Bitcoin Optech will host an audio recap discussion of this newsletter with special guest Yuval Kogman on Riverside.fm Tuesday at 15:30 UTC. Join us to discuss or ask questions!
Bitcoin Optech newsletter #334: 2024 Year-in-Review Special is here: - notes Bitcoin developments during each month of 2024 - feature: Vulnerability disclosures - feature: Cluster mempool - feature: P2P transaction relay - feature: Covenants and script upgrades - feature: Major releases of popular infrastructure projects - feature: Optech In 2024, Optech summarized more than two dozen vulnerability disclosures... An idea for a mempool redesign from 2023 became a particular focus for several Bitcoin Core developers throughout 2024... Fee management has always been a challenge in the decentralized Bitcoin protocol, but widespread use of contract protocols such as LN-Penalty and ongoing research into newer and more complex protocols has made it more important than ever to ensure users can pay and increase fees on demand. Bitcoin Core contributors have been working on this problem for years, and 2024 saw the public release of several new features that significantly improve the situation... Several developers devoted much of their time in 2024 towards advancing proposals for covenants, scripting upgrades, and other changes that would support advanced contract protocols such as joinpools and channel factories... Optech covered major releases of popular infrastructure projects throughout the year... In Optech’s seventh year, we published: - 51 newsletters - 35 new topic pages - over 120,000 words, a 350pg book equivalent - a wallet guide for developers - over 59hr of podcasts, with 488,000 words of transcripts w/75 guests - 200+ non-English translations Bitcoin Optech will host an audio recap discussion of this special newsletter with special guests Dave Harding, Niklas Gögge, Gloria Zhao, and Brandon Black on Riverside.fm Monday at 15:30 UTC. Join us to discuss or ask questions!
Bitcoin Optech newsletter #333 is here: - describes a vulnerability that allowed stealing from old versions of various LN implementations - announces a deanonymization vulnerability affecting Wasabi and related software - summarizes a post and discussion about LN channel depletion - links to a poll for opinions about selected covenant proposals - describes two types of incentive-based pseudo-covenants - references summaries of the periodic in-person Bitcoin Core developer meeting - recaps the "Track and use all potential peers for orphan resolution" PR Review Meeting - summarizes changes to services/client software - summarizes popular Q&A from Stack Exchange - Optech Newsletter #333 Recap on Riverside David Harding announced to Delving Bitcoin a vulnerability he had responsibly disclosed earlier in the year. Old versions of Eclair, LDK, and LND with default settings allowed the party who opened a channel to steal up to 98% of channel value... A developer of GingerWallet disclosed a method a coinjoin coordinator could use to prevent users from gaining any privacy during a coinjoin... René Pickhardt posted to Delving Bitcoin and participated, along with Christian Decker, in an Optech Deep Dive about his research into the mathematical foundations of payment channel networks... /dev/fd0 posted to the Bitcoin-Dev mailing list a link to a public poll of developer opinions about selected covenant proposals... Jeremy Rubin posted to the Bitcoin-Dev mailing list a link to a paper he authored about oracle-assisted covenants. The model involves two oracles: a covenant oracle and an integrity oracle... Many Bitcoin Core developers met in person in October, and several notes from the meeting have now been published... 'Track and use all potential peers for orphan resolution' is a PR by glozow that improves the reliability of orphan resolution by letting the node request missing ancestors from all peers instead of just the one that announced the orphan... Changes to services and client software: - Java-based HWI released - Saving Satoshi Bitcoin development education game announced - Neovim Bitcoin Script plugin - Proton Wallet adds RBF Selected Q&A from Bitcoin Stack Exchange: - How long does Bitcoin Core store forked chains? - What is the point of solo mining pools? - Is there a point to using P2TR over P2WSH if I only want to use the script path? Bitcoin Optech will host an audio recap discussion of this newsletter with special guests Dave Harding and /dev/fd0 on Riverside.fm Tuesday at 15:30 UTC. Join us to discuss or ask questions!
Bitcoin Optech newsletter #332 is here: - announces the disclosure of a transaction censorship vulnerability - summarizes discussion about the consensus cleanup soft fork proposal - Optech Newsletter #332 Recap on Riverside Antoine Riard posted to the Bitcoin-Dev mailing list about a method for preventing a node from broadcasting a transaction belonging to a connected wallet... Antoine Poinsot posted to the existing Delving Bitcoin thread about the consensus cleanup soft fork proposal. In addition to the already proposed fix for the classic time warp vulnerability, he proposed also including a fix for the recently discovered Zawy-Murch time warp... Bitcoin Optech will host an audio recap discussion of this newsletter with special guest Antoine Poinsot on Riverside.fm Tuesday at 15:30 UTC. Join us to discuss or ask questions!
Bitcoin Optech newsletter #331 is here: - summarizes several recent discussions about a Lisp dialect for Bitcoin scripting - adds a Basic Bitcoin Lisp Language topic - summarizes popular Q&A from Stack Exchange - Optech Newsletter #331 Recap on Riverside Anthony Towns made several posts about a continuation of his work on creating a Lisp dialect for Bitcoin that could be added to Bitcoin in a soft fork... Basic Bitcoin Lisp language (bll) is a proposed scripting language that could be added to Bitcoin in a soft fork... Selected Q&A from Bitcoin Stack Exchange: - How does ColliderScript improve Bitcoin? - Why do standardness rules limit tx weight? - Is the scriptSig spending a P2A output expected to be empty? - What happens to the unused P2As? - Why doesn’t Bitcoin’s PoW algorithm use a chain of hashes? - Clarification on false value in Script - What is this micro tx? - Are there any UTXOs that cant be spent? - Why wasnt BIP34 implemented in the coinbase tx’s locktime or nSequence? Bitcoin Optech will host an audio recap discussion of this newsletter with special guest AJ Towns on Riverside.fm Tuesday at 20:30 UTC. Join us to discuss or ask questions!