Skip to content

Newsletters: add 408 (2026-06-05)#2773

Open
bitschmidty wants to merge 9 commits into
bitcoinops:masterfrom
bitschmidty:2026-06-05-newsletter
Open

Newsletters: add 408 (2026-06-05)#2773
bitschmidty wants to merge 9 commits into
bitcoinops:masterfrom
bitschmidty:2026-06-05-newsletter

Conversation

@bitschmidty bitschmidty self-assigned this Jun 1, 2026
@TumaBitcoiner
Copy link
Copy Markdown
Contributor

I can take care of this @bitschmidty

Comment thread _posts/en/newsletters/2026-06-05-newsletter.md Outdated
Comment thread _posts/en/newsletters/2026-06-05-newsletter.md Outdated
Comment thread _posts/en/newsletters/2026-06-05-newsletter.md Outdated
Comment thread _posts/en/newsletters/2026-06-05-newsletter.md Outdated
Comment thread _posts/en/newsletters/2026-06-05-newsletter.md Outdated
Comment thread _posts/en/newsletters/2026-06-05-newsletter.md Outdated
Comment thread _posts/en/newsletters/2026-06-05-newsletter.md Outdated
current BIP324 handshake first to open a classical channel to be used
to negotiate the post-quantum one. Another approach, based on Outer
Encrypts Inner Nested Combiner (OEINC), would use an outer KEM to
encrypt another inner KEM, achieving post-quantum channel in a single step.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
encrypt another inner KEM, achieving post-quantum channel in a single step.
encrypt another inner KEM, achieving a post-quantum channel in a single step.

@bitschmidty
Copy link
Copy Markdown
Contributor Author

Pushed some style fixups and other things for @reardencode section that I hope he wont be mad about
Added qr miniscript news item
Added topic entries, lede
Left suggestions for @TumaBitcoiner item

Comment thread _posts/en/newsletters/2026-06-05-newsletter.md
change to make 64-byte witness-stripped transactions consensus invalid. This
change is intended to prevent a class of [merkle tree vulnerabilities][topic
change is intended to make a class of [merkle tree vulnerabilities][topic
merkle tree vulnerabilities] impossible and therefore make implementing
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove impossible

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But isnt this "change is intended to make a class of merkle tree vulnerabilities impossible" correct?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah, right. sorry, misread the diff.

Co-authored-by: Mike Schmidt <schmidty@gmail.com>
Comment thread _posts/en/newsletters/2026-06-05-newsletter.md Outdated
Co-authored-by: Jiří Jakeš <jiri@jirijakes.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants