BIP-39 PBKDF2-HMAC-SHA512 brute-force caveat
llfourn-bip39-pbkdf2-brute-force
- Author
- @LLFOURN
- Organisation
- independent
- Evidence role
- social statement
- Posted
- 31 Jul 2026, 01:05 UTC
- Capture status
- capture held
LLFOURN revises an earlier estimate, noting that BIP-39 key derivation uses PBKDF2-HMAC-SHA512, so the relevant metric is the laptop's GPU rather than raw SHA-512 speed. Held as a dated technical correction about the compute requirements for attacking the disclosed entropy weakness. The observation is the poster's own and is not independently verified here.
This post is registered as evidence and has a locally held capture. The original remains the canonical publication. Last checked .
This post is held twice: here, with this project's own note on why it matters, and again as part of the conversation captured at , which is polled for changes. Both copies are the same post; neither is a separate event.
Snapshot and diff bodies for this chain monitor are held in the local evidence archive but withheld from the public site because they can contain the addresses of people who published nothing themselves. Capture times and reviewed change summaries remain available below.
Held captures
0 presentation-noise differences. Sidebar, ticker and other page chrome churn that our review classified as not being changes to what the source says.
The excerpts and plain unified diffs above show the text this project held and how it changed. To verify a quotation, compare it against the page itself or against the Internet Archive's copies, which are independent of this project.
Complete captures are held offline rather than mirrored here, so this page shows diffs and excerpts. If a quotation is ever disputed, the full copy can be produced. Ask.
Compare the screenshot or a quotation against the original while it is available.