Whether through this organized review or in some other way, Optech strongly encourages all technically skilled Bitcoin users to dedicate time to reviewing the taproot set of proposals. For the first time ever, this testing can include creating a reproducible build of LND and verifying that it has the same hash as the binaries distributed by the LND developers. All developers interested in these features which may be added to Bitcoin in the future are encouraged to review the study material, especially developers participating in the taproot review described in last week’s newsletter. ● LN simplified commitments: in two separate threads, developers of LND discussed their work on implementing simplified commitments, which are LN settlement transactions that only pay a minimal onchain transaction fee and which contain two additional outputs (one for each party). ● Publication of videos and study material from schnorr/taproot workshop: Optech published a blog post with links to videos, Jupyter notebooks, GitHub repositories, and more information produced for the schnorr and taproot workshops held in San Francisco and New York City last month. However, ZmnSCPxj describes why this might be unsafe given Wagner’s algorithm as described in last week’s newsletter.
This is the last significant feature in Bitcoin Core to depend on OpenSSL, and a PR has been opened to complete the removal of that dependency. Centarra – Removal from list requested. They also keep a small list of the growing number of services that accept Monero. This week’s newsletter describes a demo implementation of eltoo and several discussions related to it, https://youtu.be requests comments on limiting the normal number of LN gossip updates to one per day, and provides our longest-to-date list of notable changes to popular Bitcoin infrastructure projects. The goal of the proposed specification is to allow all LN implementations to interoperate with any watchtower rather than there being a different watchtower implementation for every LN implementation. This week’s newsletter requests help testing release candidates for Bitcoin Core and LND, tracks continued discussion about the proposed noinput and anyprevout sighash flags, and describes several notable changes to popular Bitcoin infrastructure projects. In addition to the name change, Rubin has also added additional details to the proposed BIP and he plans to hold a review workshop in the first few months of 2020 (fill out this form if you’re interested in attending). Chances are if you’re reading this, you already have a Binance account.
Economists define money as serving the following three purposes: a store of value, a medium of exchange, and a unit of account. It is important to note that Binance is a crypto-only exchange, and does not cater to fiat deposits. For security measures, make sure to download the Binance app only from the official Binance website. In the first thread, Johan Halseth posted an email about loosening mempool policy in order to make simplified commitments even simpler. Always paying the same address allows that address to be a normal derivable address in the client’s HD wallet, making it possible for the user to recover their funds even if they’ve lost all of their state besides their HD seed. This is believed to be superior to the data loss protection protocol which depends on storing enough state to be able to at least contact the remote peer and identify the channel.
This is a simplified alternative to the data loss protection protocol that LND previously used and continues to understand. The LN protocol only allows the node that opens a channel to propose new commitment transactions with feerate changes, so this change only applies to channel initiators. 15759 increases the number of outbound connections the node will make from 8 to 10. The two new connections will only be used to announce and relay new blocks; they won’t announce or relay unconfirmed transactions or addr peer-discovery messages. If and when you are ready to make your first purchase, this guide and the rest of BuyBitcoinWorldwide should put you on the right path. A PR has been opened to Bitcoin Core to make it harder for users to configure their node this way and to print additional warnings about enabling such behavior. O’Connor’s concerns seemed to focus on this odd behavior of CTV making it harder to model the semantics of Bitcoin Script, something which O’Connor has previously worked on and which is related to his continuing work on the Simplicity scripting language. On-list, Russell O’Connor restated a previous concern of his about CTV pulling data off the stack in an abnormal order for Bitcoin Script.