I’ve not been talking to anyone else much if anything at all, Bitcoin Global shareholders included. The Bitcoin network is permissionless, which means that anyone can become a miner and participate in its consensus process. This ensures that multi-homed nodes can better inform the network of their network connectivity. 684 updates BOLT7 to suggest that nodes send their own generated announcements even when the remote peer requests a filter that would suppress that announcement. 3821 adds anchor commitments for LN channels and enables them by default if both participating nodes of a channel signal support. 3372 allows the user to specify an alternative program to use instead of one of the default sub-daemons (the C-Lightning system consists of multiple interacting daemons, referred to as sub-daemons of lightningd). Providing a descriptor here makes it easier for the user (or a program that is calling this RPC) to get all the information they need to not only monitor for payments received to the created address but to also later create unsigned transactions which start the process of spending that money. 18032 extends the results of the createmultisig and addmultisigaddress RPCs to include a descriptor field that contains an output script descriptor for the created multisig address.
3351 extends the invoice RPC with a new exposeprivatechannels parameter that allows the user to request the addition of route hints for private channels to a generated BOLT11 invoice. Previously, it returned an array of objects where the label contained fields for its name and its purpose, where purpose corresponded to the part of the wallet that generated the address. The latest error message is returned as part of the ListPeers results, making it easier to diagnose problems. In legacy and segwit v0 script, the inefficiency isn’t believed to cause any significant problems. Experienced users are encouraged to help test the software so that any problems can be identified and fixed prior to release. ● Help test Bitcoin Core 0.19.1rc1: this upcoming maintenance release includes several bug fixes. ● Help test LND 0.9.0-beta-rc1: this pre-release of the next major version of LND brings several new features and bug fixes. Subsequent to the workshop, CTV proposer Jeremy Rubin announced a mailing list to help coordinate future review and discussion of the BIP119 proposal. This can help ensure that a node gets announced to the network via its direct peers without otherwise changing how filtering works.
● Coinbase withdrawal transactions now using batching: Coinbase has rolled out batch withdrawals that they estimate will reduce their load on the Bitcoin network by 50%. Instead of each withdrawal payment generating a single onchain transaction, multiple payments will be combined into a single transaction once every 10 minutes. Unless you are eager to be deputized into a hall monitor for visit the next page new financial system, it is best to repudiate the influence that helming a PoS network would grant you. ● Discussion of soft fork activation mechanisms: Matt Corallo started a discussion on the Bitcoin-Dev mailing list about what attributes are desirable in a soft fork activation method and submitted a proposal for a mechanism that contains those attributes. ● Coinjoins without equal value inputs or outputs: Adam Ficsor (nopara73) started a discussion on the Bitcoin-Dev mailing list about two previously-published papers (1, 2) describing coinjoins that didn’t use either equal-value inputs or outputs.
70) which will need to add inputs to a transaction in order to be able to spend low-value UTXOs. 3814 allows the UTXO sweeper to add wallet inputs to a sweep transaction in order to ensure its output meets the dust limit. The transaction process is peer to peer and there is no third party interference. In the responses to the post, Jorge Timón and Luke Dashjr both proposed that any BIP8-like mechanism use mandatory versionbits signaling leading up to the flag day (similar to how BIP148 proposed to activate segwit); Corallo notes that this conflicts with the third and fourth goals. Corallo also worries that using BIP8 from the start of a soft fork deployment gives the impression that the developers of node software get to decide the rules of the system. A final discussion covered how and when to attempt to get BIP119 activated, including when a PR for it should be opened to the Bitcoin Core repository, what activation mechanism it should use (e.g. BIP9 versionbits), and what range of activation dates would be appropriate if it uses a miner-activated soft fork mechanism such as BIP9. Specifically, it uses something called Proof of Staked Authority (or PoSA), where participants stake BNB to become validators.
