Newsletters: add 400 (2026-04-10)#2707
Newsletters: add 400 (2026-04-10)#2707bitschmidty wants to merge 5 commits intobitcoinops:masterfrom
Conversation
| store recovery hints, such as a birthday height to speed up | ||
| [silent payment][topic silent payments] scanning. |
There was a problem hiding this comment.
Would suggest to rephrase: this will speed up any wallet’s scanning, not just ones that use silent payments, although it is especially relevant for silent payments because the scanning cost is much higher.
| [tapscript][topic tapscript] version that restores opcodes disabled in 2010 | ||
| such as [OP_CAT][topic op_cat] (see [Newsletter #374][news374 tapscript]). |
There was a problem hiding this comment.
Perhaps the connection of the two BIPs could be clarified by adding something along the lines of:
| [tapscript][topic tapscript] version that restores opcodes disabled in 2010 | |
| such as [OP_CAT][topic op_cat] (see [Newsletter #374][news374 tapscript]). | |
| [tapscript][topic tapscript] version that restores opcodes disabled in 2010 | |
| such as [OP_CAT][topic op_cat] (see [Newsletter #374][news374 tapscript]) and limits script evaluation costs per the Varops budget introduced in BIP440. |
| - [BIPs #2134][] updates [BIP352][] ([silent payments][topic silent payments]) to | ||
| warn wallet developers not to let policy filtering, such as for | ||
| [dust][topic uneconomical outputs], affect whether scanning continues after a | ||
| match is found. Treating a filtered-out output as if there were no match can | ||
| cause the wallet to prematurely stop scanning and miss later outputs from the | ||
| same sender. |
There was a problem hiding this comment.
I don’t think this is newsworthy. It’s just a non-functional change that clarifies to implementers how to correctly scan in exceedingly rare circumstances.
|
I think the file was accidentally named |
|
Added a review club summary mirroring a previous edition: https://bitcoinops.org/en/newsletters/2024/09/13/ |
4 participants
Uh oh!
There was an error while loading. Please reload this page.