Jean Do

This is just a test

On Sunday, June 29th 2025, I built and verified the following images for SeedSigner release v0.8.6: ``` file: seedsigner_os.0.8.6.pi0.img sha256: da32ce21f185404ccefd58e76e55ae7f1ac9fe2df2100bc7bbab3e03c5d71b6d file: seedsigner_os.0.8.6.pi02w.img sha256: d1669ad3aec6046dc43a673056a258e00c389ce23fa0ff754378cd0267516888 file: seedsigner_os.0.8.6.pi2.img sha256: 029ecacc6ba45ae23cb953d7111cf98b0689f1eefb1cee101300acb10167b098 file: seedsigner_os.0.8.6.pi4.img sha256: 47879ded57a91ecf46dbb44825699c53550bbf5aa6aa7c5b6519913a8863d157 ``` Others have also verified binary reproducibility; you can too. https://github.com/SeedSigner/seedsigner/releases/tag/0.8.6 ~

On resolution: "To learn about Miniscript in 2025" By the end of last week: covered Liana's Expanding-Multisig wallets. Notes for the P2WSH version: https://gist.github.com/jdlcdl/d83a83ec7d47d98888a8647b636d567d Notes for the P2TR version: https://gist.github.com/jdlcdl/c38e1b80cd814e48e1d158a98cf704f6

On resolution "Learn about Miniscript in 2025" Earlier this week: worked thru Liana's Simple Inheritance wallets. Notes for the p2wsh version: https://gist.github.com/jdlcdl/b0dea22a8a6caf0fd7c40b244357d8d2 Notes for the p2tr version: https://gist.github.com/jdlcdl/b17c6b551839adb5b7b7d4ef9574e48e

Vamos! https://github.com/SeedSigner/seedsigner/releases/tag/0.8.5

"All I have is my node, a stateless signer, and my secrets. How to...?" I've been working on learning to "make do" with minimal tools: * Bitcoin Core as a watch-only wallet (via cli and rpc), * Stateless signers SeedSigner and Krux, * SeedQReader, a QR-encoder/decoder, to cut-n-paste between my watch-only bitcoin-rpc sessions and a signing device. Last week I got thru documenting single-sig and multisig Native Segwit wallets, including sections for: * Secrets setup * Extended Public Keys * Output Descriptor * Watch-Only Wallet setup * Spending Funds (the important how-to steps) * Evolution of a PSBT and * Understanding Programmable Money (stepping thru `btcdeb` bitcoin script debugger) This week I'm working on doing the same for default Liana Miniscript wallets. Yesterday, I got thru Liana's Simple-Inheritance P2WSH setup. https://gist.github.com/jdlcdl/b0dea22a8a6caf0fd7c40b244357d8d2 Today, I'm on schedule to finish similar for Taproot. If I stay on track, I should have similar for Liana's Expanding-Multisig wallets, in P2WSH as well as Taproot, by the end of this week. These works are part of my resolution: "to learn Miniscript in 2025". I'll keep sharing small W's if and when they arrive.

Sharing another tiny W on the journey to: Better understanding of Miniscript and bitcoin script in 2025 (via Bitcoin Core, SeedQReader, and signers Krux and SeedSigner). This time, it's a 2-of-3 p2wsh (native segwit) multisig I've added a section w/ kallewoof's `btcdeb` bitcoin script debugger. It's great for learning bitcoin-script in baby-steps and will be invaluable when I finally get to spends for Miniscript. https://gist.github.com/jdlcdl/7a853ab9ff0867b060b073f22432df3c

Just before the new year, I resolved to finally learning about Miniscript. With limited wallet choices for doing so, it took me into a dive to see what could be accomplished with bitcoin-cli, a qr-code encoder/decoder for cut-n-paste, and a DIY air-gapped stateless signing device. After getting through all that, realizing I'd bitten off more than I could chew, I thought I'd step back from the Miniscript dive to get more comfortable gluing the above tools together (this time in a python session) and performing simple signing operations -- learning as I go. Yesterday's exploration: the simplest of necessities w/ limited tools. https://gist.github.com/jdlcdl/e7b3c01384c83fb7c5518c0e053747f4 More to follow? I'll do my best to share "W"s if and when they emerge.

Hmmm, What's going on here? https://mempool.space/signet/tx/a6ed9d290adcecd33be48996f89d53d4ffef35dace9ae19a180164a898cfa4e6

Go ahead, touch it! The paint is finally dry. https://github.com/SeedSigner/seedsigner/releases/tag/0.8.0

Because YOUR attentive eyes DO matter: * for yourself and for your loved-ones, present and future, * and for your fellow peers, known and unknown, * and for the beautiful future we're building together. Who the hell is @jdlcdl (Jean Do) and why is he fiddling with embit? You may find the answer to the second question below: https://gist.github.com/jdlcdl/4f9f9cc8d24f5fc6d39e833520d2f199

A crowd has been waiting for 50m already, and 6 new blocks have been mined since then. Stand up, Walk out? Tik Tock Next Block. Wait for no man's empty promises. Onward!

I repeat: My never ending gratitude to all you good folks who support developers. Whether you do so indirectly through great foundations like HRF and OpenSats, to your favorite project fund, or directly to individual devs, you're playing a real part in making the projects we love become reality. Developers cannot thank you personally, but when they put their noses down to provide solutions, they're doing it partially because you make that possible. Together, we're going leave this place better off than we found it... and our children deserve every bit of that. Thank you!!! 🙏

I don't know who you are, but you certainly do. Thank you! 🙏

Hi nostr:npub1jmr7lf85239hswjhy6jxrq2hf8cteelkddl855shfd23564ajxeseaukpd, I've bricked my K210 based sipeed-maix-amigo many times and it always comes back to life (via ktool). Rumor has it that you have an m5stickV that bricked during a recent flash operation which failed. I'd like to know the current state (still bricked? or since fixed?) and if you'd like help in debugging -- here in public or via dm, as you wish. Happy TGIF, enjoy your weekend. -jd