A single typo on a BIP39 passphrase can lock you out of your #Bitcoin forever with zero warning. Here is why hardware wallet teams like Blockstream Jade and Trezor should introduce a simple, life-saving UX feature: Passphrase Double-Entry Confirmation. 🧵👇

Is it the right time for those again?

Honeybadger didn’t care about a loud minority. Proof of Social Media didn’t work for Roger, Jihan and Faketoshi. Neither did it for Luke, Mechanic and friends. Something to take note of when the next folks inevitably will come along in a few years.

Time to increase my KYC free stack further 💪

Hardfork and new shitcoin confirmed #bip110

The regular person doesn’t know what a fingerprint is and how to spot it. You need something simpler that catches most potential error cases for the average user.

That wouldn’t be caught. Strongly recommend to physically back up the phrase in a different location than your BIP39 words

Whatever you make it out to be

Except, we're probably not. I have quite some high hopes for sciences after AI acceleration.

Would love to see this safety feature considered for future firmware updates by Blockstream Jade, Trezor, and across the hardware wallet ecosystem. Small UX safeguards like this save real Bitcoin from being lost to simple human error. What do you think?

Double-entry password verification has been a standard security UX pattern in software for decades. Bringing this native check to hardware signing devices directly protects users from catastrophic, irreversible fund loss.

To keep the UX flexible, make it a toggle in device settings: Passphrase Confirmation: [Always / Off] Power users who prioritize speed can disable it; users prioritizing safety can keep the safety net active.

The Workflow: • Step 1: Enter passphrase • Step 2: Prompt: "Re-enter passphrase to confirm" • Match: Derive wallet & addresses • Mismatch: Show alert ("Passphrase mismatch. Please try again.") and wipe the buffer

The Proposal: Native Passphrase Double-Entry. When entering a passphrase on the device, prompt the user to re-enter it a second time to verify proof-of-knowledge before deriving the master key and revealing addresses.

The nightmare scenario: You enter a passphrase with a typo you didn't notice You generate & deposit funds into that address You turn off the device Next time you enter your intended passphrase: Balance: 0 BTC Those funds are effectively gone forever.

5/ What peak cinema looks like: • JPEG posters pivot to a new workaround within 48 hours. • Your Liana inheritance vault gets bricked as collateral damage. • You survived a Coldcard seed exploit only to softfork your own recovery keys into oblivion. REKT. ☠️

4/ Literally ⁠OP_IF⁠. 😂

3/ Because JPEGs hide data in ⁠OP_FALSE OP_IF⁠ envelopes, BIP 110's galaxy-brain fix to "rug the spammers" is restricting conditional ⁠OP_IF⁠ execution paths in Tapscript. Guess what Liana's policies depend on for decaying multisig and timelocked spending conditions?

2/ Ironically half of these guys are proudly sporting "BIP 110" badges in their bio while setting up Liana vaults. They genuinely believe they’re modern-day protocol guardians, yet they don't have the slightest clue how their own execution scripts function. 🤡

1/ Coldcard’s RNG firmware exploit drains in excess of 100Mio, sending folks to @lianabitcoin and Miniscript for multi-key self-custody at rates never seen before. A totally sensible move until you look at the handles migrating. 🧵