Forum

Hankin, Aaron. "Bitcoin Pizza Day: Celebrating the $80 Million Pizza Order". In order to solve for required intermediaries to enable digital transactions, Satoshi Nakamoto developed Bitcoin to solve the problem known in computer science as double spend. The mainnet blockchain contains two duplicate coinbase transactions, at height 91,842 and 91,880. They are identical to previous coinbase transactions and overwrote existing coinbase outputs before they were spent, reducing total available supply by 100 BTC. 23882 contains an update of the documentation in validation.cpp regarding the operation of testnet3. The pull request also improves test coverage, adds more documentation to the address validation code, and improves error messages when decoding fails, especially to distinguish use of bech32 and bech32m. This allows wallet users to generate and use P2TR addresses by creating a default bech32m descriptor with their wallet instead of importing one. Similarly, having one automobile as opposed to zero is a significant boon for personal transportation, https://www.youtube.com/@Coinuniverse_ whereas if you already have 99 the 100th is nearly useless.

In the original version of Bitcoin, it was possible for transactions to have identical content and thus colliding txids. A Return to Fees - why fees spike in Bitcoin, why high fees may return, and how businesses can thrive in a high-fee environment. This week’s newsletter links to a discussion about how to allow LN users to choose between higher fees and higher payment reliability. ● LN reliability versus fee parameterization: Joost Jager started a thread on the Lightning-Dev mailing list about how to best allow users to choose between paying more fees for faster payments or waiting longer to save money. Since the height is unique, the content of coinbases could no longer be identical at different heights, which also prevents the issue in descendant transactions inductively. A bank is hired by the merchant to monitor the transactions with credit and debit cards and usually charges a monthly fee, a transaction fee, and a commission for this service. A connection’s reconciliation salt is the combination of both peers’ locally-generated salts and is used to create shortids for each transaction.

The peer must also support witness transaction identifier (wtxid) relay, because sketches for transaction reconciliation are based on the transaction wtxids. There is no enforced order; either peer may send it first. Are there any drawbacks to this approach? Department of Justice prosecutors are delaying the conclusion of a long-running criminal investigation into the world's largest cryptocurrency exchange Binance, four people familiar with the matter have told Reuters. For anyone interested in participating in such testing, the Optech newsletter lists RCs from four major LN implementations, plus various other Bitcoin software. LN developers participating in the discussion noted that catching these sort of bugs is why every major implementation provides release candidates (RCs) and why expert users and administrators of production systems are encouraged to contribute to the testing of those RCs. This week’s newsletter describes a recently fixed interoperability issue between different LN software and includes our regular sections with a list of new releases and release candidates plus notable changes to popular Bitcoin infrastructure software.

LND users are encouraged to upgrade to a bug fix release, 0.14.1 (described in the Releases and release candidates section below). 6026 in the Notable changes section below. Non-controversial and mechanical code changes can be merged more quickly, and contentious bits can be discussed over more time. The salted hash function used for shortids is designed to efficiently create compact ids, but is not guaranteed to be secure against collisions if an attacker can control what the salt is. Older nodes that don’t understand Erlay messages such as sendrecon would simply ignore them and still be able to function normally. After version messages are sent, but before verack messages are sent, peers each send a sendrecon message containing information such as their locally-generated salt. 165 was implemented in different ways by different LN nodes, resulting in nodes running the latest version of LND being unable to open new channels with nodes running the latest versions of C-Lightning and Eclair. A new protocol version is not necessary for things to work; nodes using Erlay would not be incompatible with the existing protocol.