“Moving forward, Binance will support Indian regulators in the ongoing matters concerning WazirX. ● LND 0.13.0-beta.rc2 is a release candidate that adds support for using a pruned Bitcoin full node, allows receiving and sending payments using Atomic MultiPath (AMP), and increases its PSBT capabilities, among other improvements and bug fixes. ● BTCPay 1.0.7.2 fixes minor issues discovered after last week’s security release. CAT. Hopefully the discussion will be able to settle the major unresolved issues related to noinput and help get this proposal on track for inclusion in a subsequent soft fork. Onion peers have historically been disadvantaged by the eviction criteria due to their higher latency relative to IPv4 and IPv6 peers, leading to users filing multiple issues. 139), a next step will be to extend eviction protection to I2P peers, as they generally have higher latency than onion peers. With the updated logic, half of the protected slots are allocated to any onion and localhost peers, with onion peers receiving precedence over localhost peers. AMP invoices are currently an LND-only feature and only accept HTLCs that have the AMP feature bits set as well as an AMP payload.
This extends prior work that enabled use of AMP by providing manually specfied payment parameters to the SendPayment RPC. If they need to close more than 10 channels, they can use the funds received from closing one channel to close the next channel in a domino effect. ● Equivocation: where an oracle signs for the same event more than once, producing conflicting results. ● 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. This week’s newsletter relays a request for comments on a proposed change to the BIP341 taproot transaction digest and briefly summarizes discussion about a new and more concise protocol for atomic swaps. 146, Antoine Riard will be hosting IRC-based meetings to discuss how to make unconfirmed transaction relay more reliable for contract protocols such as LN, coinswaps, and DLCs.
Charles Hill and Andrew Kozlik each replied with information about protocols they’re working on. This allows fee bumping a transaction using CPFP and was added for that reason by a developer working on implementing anchor outputs in the Eclair LN node. Instead, it works using a P2P internet protocol. 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 the 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). In addition, to further this analysis, information has been gathered on the first people who orbited close to Satoshi (e.g. Hal Finney, Nick Szabo). 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).
When a well-defined address exists, the responses now include the optional field address instead. Now just replace the example Bitcoin address with your own or change the crypto style to represent the type of crypto you need to generate a QR code for. Ruben Somsen noted that a hypothetical variation of spacechains, a type of one-way pegged sidechain, would be affected by the problem. The only problem with stop-limit orders is that they force you to pick a direction. This is mainly meant for container-based setups where the passphrase is already stored in a file, so using that file directly doesn’t create any additional security problems. One commentator points out that the use of BIP69 has so far caused three separate problems that may have led to accidental channel closures and small amounts of funds lost to unnecessary onchain fees. ● Sparrow 1.4.0 released: Sparrow 1.4.0 adds the ability to create a child pays for parent (CPFP) transaction from the transaction list screen, user-defined fee amounts during coin selection, and various other improvements.
Comments