Bitcoin and Ethereum both Suffered Losses

This week’s newsletter contains our regular sections with announcements of new releases and release candidates, plus notable changes to popular Bitcoin infrastructure projects. This week’s newsletter describes the results of discussion about choosing activation parameters for a taproot soft fork and includes our regular sections with selected questions and answers from the Bitcoin Stack Exchange, releases and release candidates, and notable changes to popular Bitcoin infrastructure software. Several recent releases of Bitcoin Core might be re-released with slightly different version numbers so that their Windows binaries can use this certificate. 22017 updates the code signing certificate used for Windows releases after the previous certificate was revoked by its issuer without them providing an explicit reason. This allows the user or parent process to more easily know whether the daemon started successfully by observing the program’s output or exit code. If a txid mutation happens, then the pre-signed refund transaction is not valid, so the user can’t get their funds back.

2. You can only edit certain details of the transaction. 5033 adds an updatechanstatus RPC that can advertise that a channel has been disabled (similar to your node going offline) or bitcoinxxo.com that it’s been re-enabled (similar to your node coming back online). 1 hundreds of "btcwire 0.5.0/neutrino" connections are downloading TB from my Bitcoin node While running Bitcoin Core 0.21.0 with compact block filters enabled, qertoip notices a large number of connections (75%) and bandwidth usage (90%) from btcwire 0.5.0/neutrino user agents. This week, Rusty Russell posted to the Lightning-Dev mailing list about a quick and experimental feature he implemented in C-Lightning to help a user with this problem recover their funds. ● Discussion about a BIP70 replacement: Thomas Voegtlin started a thread on the Bitcoin-Dev mailing list about a replacement for some of the features of the BIP70 payment protocol, specifically the ability to receive a signed payment request. ● Candidate Set Based (CSB) block template construction: Mark Erhardt posted to the Bitcoin-Dev mailing list about an analysis he and Clara Shikhelman performed on an alternative transaction selection algorithm for miners.

● Rescuing lost LN funding transactions: LN funding transactions are not safe in the presence of transaction malleability. However, Erhardt and Shikhelman note that a more sophisticated algorithm that may require a bit more CPU can find sets of related transactions that are even more profitable to mine than Bitcoin Core’s existing simple algorithm. This fixes an interoperability issue when opening channels with LND, which may request a delay up to 2016 blocks, larger than the previous Rust-Lightning maximum of 1008 blocks. Pieter Wuille clarifies that since 0.10.0, Bitcoin Core uses headers-first IBD (initial block download) which eliminates the possibility of orphan blocks (as defined by the questioner). Bitcoin Core has been able to interface with hardware signers using HWI since Bitcoin Core version 0.18. Until this PR, however, the process required use of the command line to transfer data between Bitcoin Core and HWI. ● HWI 2.0.0 is the release for the next major version of HWI. ● Rust-Lightning 0.0.13 is the latest release for this LN library containing improvements aimed at forward compatibility with multipath payments and future script upgrades such as taproot.

4501 adds JSON schemas for the output of roughly half of C-Lightning’s current commands (with schemas for the other half planned to be added in the future). Later, explicit detection of inbound onion connections was added. 20197 improves the diversity of peer connections by updating the inbound peer eviction logic to protect the longest-running onion peers. 139), a next step will be to extend eviction protection to I2P peers, as they generally have higher latency than onion peers.