Skip to content

Newsletters: add 403 (2026-05-01)#2736

Open
bitschmidty wants to merge 4 commits intobitcoinops:masterfrom
bitschmidty:2026-05-01-newsletter
Open

Newsletters: add 403 (2026-05-01)#2736
bitschmidty wants to merge 4 commits intobitcoinops:masterfrom
bitschmidty:2026-05-01-newsletter

Conversation

@bitschmidty bitschmidty self-assigned this Apr 24, 2026
Comment on lines +74 to +77
to migrate to post-quantum cryptography at their discretion. In the
subsequent conversation, some agreement was reached on both adding
post-quantum signing to tapscript and adding a plain post-quantum output
type. Several open questions remain, including whether and to what degree to
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

It may make sense to clarify who agreed here:

Suggested change
to migrate to post-quantum cryptography at their discretion. In the
subsequent conversation, some agreement was reached on both adding
post-quantum signing to tapscript and adding a plain post-quantum output
type. Several open questions remain, including whether and to what degree to
to migrate to post-quantum cryptography at their discretion. In the
subsequent conversation, the participants agreed on both adding
post-quantum signing to tapscript and adding a plain post-quantum output
type. Several open questions remain, including whether and to what degree to

Comment on lines +101 to +102
([consensus cleanup][topic consensus cleanup]) prevents. Over nearly a full
day, 3 batches of slow to validated blocks were signed on the most popular
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

How about:

Suggested change
([consensus cleanup][topic consensus cleanup]) prevents. Over nearly a full
day, 3 batches of slow to validated blocks were signed on the most popular
([consensus cleanup][topic consensus cleanup]) prevents. Repeated three times over the course of a
day, batches of slow to validated blocks were signed on the most popular

Antoine Poinsot [wrote][ap delving slowblocks] about a demonstration of the
types of slow to validate blocks that part of [BIP54][]
([consensus cleanup][topic consensus cleanup]) prevents. Over nearly a full
day, 3 batches of slow to validated blocks were signed on the most popular
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

slow to validated ↦ slow to validate

Suggested change
day, 3 batches of slow to validated blocks were signed on the most popular
day, 3 batches of slow to validate blocks were signed on the most popular

BIP54.

- **Post-Quantum BIP-86 Recovery via zk-STARK Proof of BIP-32 Seed Knowledge**:
Olauluwa Osuntokun (roasbeef) [posted][oo ml pqrecovery] on the Bitcoin-Dev
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
Olauluwa Osuntokun (roasbeef) [posted][oo ml pqrecovery] on the Bitcoin-Dev
Olaoluwa Osuntokun (roasbeef) [posted][oo ml pqrecovery] on the Bitcoin-Dev

genesis, the merge fails. See Newsletters [#372][news372 checkpoint] and
[#390][news390 checkpoint] for previous work on `CheckPoint`.

- [BIPs #1548][] adds [BIP391][], a specification for Binary Output Descriptors
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Reminder to reorder

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.

5 participants