Newsletters: add 392 (2026-02-13)#2642
Merged
bitschmidty merged 5 commits intobitcoinops:masterfrom Feb 13, 2026
Merged
Conversation
jirijakes
reviewed
Feb 9, 2026
Contributor
jirijakes
left a comment
jirijakes
left a comment
There was a problem hiding this comment.
Maybe also use K<sub>max</sub>?
bitschmidty
commented
Feb 12, 2026
bitschmidty
commented
Feb 12, 2026
bitschmidty
commented
Feb 12, 2026
| and adds an auxiliary file to [BIP324][] tracking one-byte ID | ||
| assignments across BIPs to help developers avoid conflicts. The file | ||
| also records [utreexo][topic utreexo]'s proposed assignments from | ||
| [BIP183][]. |
bitschmidty
commented
Feb 12, 2026
bitschmidty
commented
Feb 12, 2026
Contributor
Author
|
Added lede, topics, some changes to the SP news item. |
LarryRuane
reviewed
Feb 12, 2026
theStack
reviewed
Feb 12, 2026
theStack
left a comment
theStack
left a comment
There was a problem hiding this comment.
Thanks for covering the BIP-352 K_max protocol restriction topic! Left some late nits about that, feel free to ignore.
bitschmidty
force-pushed
the
2026-02-13-newsletter
branch
from
e3c3d74 to
1d93bc1
Compare
bitschmidty
force-pushed
the
2026-02-13-newsletter
branch
from
1d93bc1 to
74fcfdf
Compare
LarryRuane
reviewed
Feb 13, 2026
Comment on lines
+22
to
+23
| constructs a transaction with a large number of taproot outputs (23255 max outputs per | ||
| block according to current consensus rules) that all target the same entity. |
Collaborator
There was a problem hiding this comment.
Suggested change
| constructs a transaction with a large number of taproot outputs (23255 max outputs per | |
| block according to current consensus rules) that all target the same entity. | |
| constructs a transaction with a large number of taproot outputs (up to 23255 outputs per | |
| block, the current consensus limit) that all target the same entity. |
| If there were no limit on group size, it would take several minutes | ||
| to process, rather than tens of seconds. | ||
|
|
||
| This motivated a mitigation to add a new parameter, `K_max`, that limits the |
Collaborator
There was a problem hiding this comment.
Suggested change
| This motivated a mitigation to add a new parameter, `K_max`, that limits the | |
| This motivated the addition of a new parameter, `K_max`, that limits the |
| to process, rather than tens of seconds. | ||
|
|
||
| This motivated a mitigation to add a new parameter, `K_max`, that limits the | ||
| number of per-group recipients within a single transaction. In theory, this |
Collaborator
There was a problem hiding this comment.
Suggested change
| number of per-group recipients within a single transaction. In theory, this | |
| number of per-group recipients in a single transaction. In theory, this |
| protocols, such as [ECDH][ecdh wiki], in which any participant can derive a shared | ||
| secret using their private key and the other participant's public key. It also applies | ||
| a [Non-interactive Zero Knowledge proof][nizk wiki] to make circuit resolution | ||
| verifiable and to prevent cheating. |
Collaborator
There was a problem hiding this comment.
Suggested change
| verifiable and to prevent cheating. | |
| verifiable and prevent cheating. |
Comment on lines
+56
to
+57
| Another important advantage of BLISK with respect to other approaches is | ||
| eliminating the need to generate a fresh key pair. In fact, it allows connecting an |
Collaborator
There was a problem hiding this comment.
Suggested change
| Another important advantage of BLISK with respect to other approaches is | |
| eliminating the need to generate a fresh key pair. In fact, it allows connecting an | |
| Another important advantage of BLISK over other approaches is the | |
| elimination of the need to generate a fresh key pair. In fact, it allows connecting an |
Comment on lines
+60
to
+61
| Kurbatov provided a [proof-of-concept][blisk gh] for the protocol, although he stated | ||
| that the framework has not reached production maturity yet. |
Collaborator
There was a problem hiding this comment.
Suggested change
| Kurbatov provided a [proof-of-concept][blisk gh] for the protocol, although he stated | |
| that the framework has not reached production maturity yet. | |
| Kurbatov provided a [proof-of-concept][blisk gh] for the protocol, though he stated | |
| that the framework has not yet reached production maturity. |
Contributor
Author
|
Added a topic entry for the consensus cleanup Thank you @Gustavojfe @TumaBitcoiner @kevkevinpal for authoring and @LarryRuane @theStack @jirijakes for reviewing! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note: no PR Review Club this week as there was no recent meeting