Also included are our regular sections describing new software releases, available release candidates, and notable changes to popular Bitcoin infrastructure software. This week’s newsletter describes a discussion about rescuing lost LN funding transactions and includes our regular sections with announcements of releases, release candidates, and notable changes to popular Bitcoin infrastructure software. ● BTCPay Server 1.0.7.0 is the latest release for this self-hosted payment processing software. This week’s newsletter describes discussion about a desired replacement for some of the features of the BIP70 payment protocol and summarizes proposals for a standardized way to exchange fraud proofs for Discreet Log Contracts (DLCs). ● Discussion about a BIP70 replacement: Thomas Voegtlin started a thread on the Bitcoin-Dev mailing list about a replacement for some of simply click the up coming webpage features of the BIP70 payment protocol, specifically the ability to receive a signed payment request. Kozlik’s scheme is closer in spirit to BIP70 but drops its use of X.509 certificates and adds features for exchange-based coin swaps (e.g. trading BTC for an altcoin or vice-versa). Voegtlin wants to be able to prove that the address he paid was actually the address provided to him by the receiver (e.g. an exchange). As discussed, the signal was never standardized and the procedure implemented by LND didn’t depend on signaling, so this change should allow C-Lightning to send to roughly the same set of nodes that LND can address.

135, BlockSource allows software to obtain data from sources other than a standard Bitcoin Core compatible node, allowing redundancy that can help prevent eclipse attacks or other security problems. The way this was implemented created problems when the user explicitly specified the sortedmulti descriptor option that implements BIP67 key sorting. He also described alternative solutions for related problems as well as the impact of the proposed channel dual-funding protocol on this problem. 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. 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. ● Equivocation: where an oracle signs for the same event more than once, producing conflicting results. ● Lying: where an oracle signs for an outcome that users know is wrong. When the format of those proofs has been established, software can then be updated to take two separate proofs for the same oracle and event to create a proof of equivocation. This will almost always depend on evidence not available to the user’s contract software, so this type of fraud proof must be verified manually by the user, who can compare the original contract to the outcome signed by the oracle.

● Fraud proofs in the v0 Discreet Log Contract (DLC) specification: Thibaut Le Guilly started a discussion on the DLC-dev mailing list about the goal to include fraud proofs in the version 0 DLC coordination specification. Discussion participants seemed to all favor providing an equivocation proof, although there was some concern that it could be too much work for the v0 specification. 4410 brings the experimental implementation for dual-funded channels in line with the most recent draft specification changes. Christian Decker also posted a proposed change to the LN specification to help facilitate funding recovery efforts. Segwit eliminated third-party malleability as a concern for most transactions, but it doesn’t address the case where the creator of a transaction mutates its txid themselves, such as by fee bumping the funding transaction using Replace-by-Fee (RBF). Notable improvements include a more featureful and visually appealing wallet setup wizard, the ability to import wallets created using Specter, and more efficient QR codes for bech32 addresses.

According to Upbit’s website, on November 27, hackers had stolen $49 Mn worth of Ethereum from its hot wallet. The firm recently added Ethereum 2.0 staking to its portfolio and supports yield farming. Some terminals have a limit on the number of characters that can be added to stdin simultaneously (i.e. pasted), which made PSBTs over 4096 base64 characters (equivalent to 3.072 bytes of binary) unusable. 5083 allows a PSBT to be read from a file rather than by reading the standard input (stdin) file descriptor. These shutdown scripts are limited to standard forms to avoid expensive fee-heavy scripts or transactions with oversized scripts not propagating due to non-standardness. As it became possible to relay payments to any segwit script in Bitcoin Core 0.19.0.1 (released November 2019), it’s now safe to include them in LN’s standard forms. Bitcoin Core will relay and mine by default. 16546 introduces a new signer interface, allowing Bitcoin Core to interact with external hardware signing devices through the HWI or any other application which implements the same interface. ● 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.