jdlcdl
Jean Do

I think it's worth recording and timestamping the`whois` reports for these domains today. Many were updated -- within minutes or hours of each other. It feels like they're all controlled by the same decision maker. If you don't timestamp these as they are right now, will lose that this activity occurred in response to this post since someone can decide to update later in a less suspicious manner.

2025-07-28 21:50:50 UTC

- reply

Apparently, seedsigner is directly over the target?

2025-07-01 17:23:16 UTC

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
~ https://blossom.primal.net/73e232993e508ea1edcc9a46cf8aadfb035f5574a0136527322d5eeab3aedcb1.png

2025-05-03 19:01:55 UTC

- reply

Couldn't the same result be achieved -- over time with an option for opting-out, by doubling the -datacarriersize default with each future release?
It might leave the choice (at least the perception of choice) with the individual node runner.
It might offer the chance to learn over time that it is, or is not making things any worse.
It might not be so much different than node runners upgrading slowly.
It might not provoke node runners who are worried about this change to considering ditching bitcoin-core right now, many years before this merge would even make a difference (since many won't upgrade immediately).

2025-02-12 12:29:55 UTC

- reply

If those file contents don't each hash to their name and they're not empty contents: Is it possible that there is some common "seed" that they were hashed with and you just need to find that seed? Or some common xor that is needed but not known that makes them appear "corrupted"? If they're not empty contents, I wouldn't ditch them just yet.

2025-02-12 12:26:03 UTC

- reply

What does "corrupted" mean?
Does it really the case that those files' contents don't each hash to their name?

2025-02-11 17:04:40 UTC

- reply

While github's SeedSigner/seedsigner-translations repo, a submodule of seedsigner, will be the target for pull-requests, the idea is to organize all translators and one validator per language within transifex. The validator for each language would then issue the pull request once translations are polished.
So all translations for untranslated strings, and suggestions for already-translated strings can be done exclusively in transifex.
Thank you in advance for taking a look. No matter how many times a single translator looks at a translation catalog, another translator can almost always easily identify improvements.
I'll let Ace/BitcoinPrecept know to look out for you.

2025-02-11 15:12:10 UTC

- reply

OMG -- how kind! I cannot resist such an offer.
Hoping to have more eyes on the french translation of seedsigner v0.8.5 soon. Currently there is a natural francophone translating and validating at transifex -- and myself (qui parle le français comme une vache espagnole, "Mooo").
Latest screenshots are in my fork:
https://github.com/jdlcdl/seedsigner-screenshots/blob/v0.8.5%2Bfr/fr/README.md
Note that these screenshots are static, but the app on device is not. Where you see overruns in screenshots (text running past the right side of the screen) at least for the PageTitleLines and Buttons... that text will gently scroll back and forth on a seedsigner device so that all text is readable.
...while the project is:
https://github.com/SeedSigner/seedsigner/blob/dev/README.md
...and translators (and validators) organize per language at:
https://explore.transifex.com/seedsigner/

2025-02-08 17:01:14 UTC

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

2025-02-08 16:54:14 UTC

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

2025-02-05 10:59:02 UTC

- reply

SeedSigner v0.8.5, released on the evening of February 4th 2025, brings multi-language internationalization to the entire code-base with an initial localization in Spanish.
Since v0.7.0 SeedSigner has supported binary reproducibility which effectively obsoletes the need for verifying a signed release-manifest from somebody that most of us cannot know, because it enables anyone to rebuild the same release-image, byte-for-byte, directly from the open-source code repository.
I hereby attest that:
* I've been following the SeedSigner project since October 2022,
* I take great pride in helping out however I can as part of that team -- following and testing code changes as it evolves, exchanging ideas with the wonderful SeedSigner Community,
* and that I was able to reproduce ALL of the release images for v0.8.5, matching the sha256 hashes that Nick mentions in nostr event "nevent1qvzqqqqqqypzqxj6lwv69s9n5z9y52h0c9r2ec8fuak2pe9nuarj6dy3eqp4hta3qqsxu2zt9v9004u8ndn7ggxeem98u0fqrn372ku3c6v4u3dpst265ag8vykap" and also contained in the release-manifest "seedsigner.0.8.5.sha256.txt" signed by SeedSigner-the-man having rsa fingerprint ~ "4673 9B74 ... 0726 0119".
-jdlcdl
#nevent1q…ykap

2025-02-04 21:32:10 UTC

- reply

Related to the gist shared above,
Following is a similar Liana Simple-Inheritance Taproot setup.
Same secrets, same pubkeys, same Miniscript within the descriptor,
but that's where the similarities end:
note: I have yet to fully understand the taproot script-path debugger session... this is a learning-in-progress exercise after all. Will get to it.
https://gist.github.com/jdlcdl/b17c6b551839adb5b7b7d4ef9574e48e

2025-02-04 19:33:00 UTC

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

2025-02-04 15:38:29 UTC

"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.

2025-02-01 15:26:13 UTC

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

2025-01-25 16:05:51 UTC

- reply

Somebody put their money where their mouth is.
#nevent1q…pwpa

2025-01-24 14:44:58 UTC

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.

2025-01-10 13:44:24 UTC

- reply

The above two commitments are part of a project I'm working on:
to repeat Rob Hamilton's `Miniscript` template known as "mint-005"
(aka: AnchorWatch's "Trident Vault")
... with a slight twist (block-heights instead of timestamps)
I've been keeping notes of this work-in-progress at the link below:
https://gist.github.com/jdlcdl/f719db259ceea821cde541d9754c1f56
Learning as I go, it feels great to have finally resolved to learning about Miniscript in 2025.
I may share more "W"s a they occur.

2025-01-08 21:05:40 UTC

- reply

It was a commitment, a prediction about the future. But predictions can be wrong, just like this one will be. And you never know how many other "wrong" predictions were made that you never hear about.
Since it's so easy, let's try again.
https://mempool.space/signet/tx/9cfeece131e843dca6aa1df07e59aed9e10666b03811498b2e72efb7786f1eb0

2025-01-05 19:16:48 UTC

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

2024-09-26 14:27:54 UTC

- reply

Thought experiment:
All of the devices have a zero-day from the factory. We won't learn about them until it's too late; nobody will/can prove or disprove it.
* Stay updated on current attacks. Get comfortable remaining at a heightened alert-level; everyone wants your bag.
* Don't keep all of your eggs in the same basket(s).
* Don't trust, verify. But also, maybe remember that more of us are good actors than bad ones, we are making individuals and the collective stronger. We ARE on the same team.

2024-09-07 13:18:15 UTC

- reply

FOSS is very difficult when it comes to making ends meet. I've been a "user" of FOSS since the mid 90s, and used it exclusively in my professional life since the early 2000s — just to avoid myself and clients becoming prisoners of a particular platform. Until recently — and for ideological reasons, certainly not for financial ones, my only contributions were relatively meager donations to particular projects behind the tools I needed professionally.
But lately with OpenSats, HRF and others, empowered by appreciative folks who donate like heroes to make freedom possible, there is finally hope that FOSS might be something that can help pay the bills and not just be a "loss-leader" effort of passion for contributors.
Speaking for myself, I wish we could pile-on tremendous support (written, meme-etic, financial, screaming-from-the-rooftops, etc) behind contributors who apply for grants so that they can focus on a particular project. Whether developing specific new features, keeping "working" code working, or reviewing and curating others' contributions, it is required that developer minds are not wandering between the projects they love and how they'll keep a roof over their loved-ones' heads with food on the table.
Keith, if you think that my written support might help, I'd stop what I'm doing to express support for you to decision makers. If they're already reading this here, then I'll say that I know Keith as a key player whose focus on seedsigner results in real-world value that many (even ones we'll never know about) benefit from seasonally as they revisit their self-custody setups. His focus also results in magnifying the efforts of new contributors who may lack the scarce historic perspective that Keith, SeedSigner and Nick have gained over the lifetime of the project; I can say that from first-hand experience.
Thank you Keith for arriving here and doing what you've already done, for pressing to find a sustainable long-term financial reason to continue being here, and for staying here anyways even when it's difficult to find that reason.
And thank you to all of the other heroes keeping solutions for freedom moving forward. In my gut it feels inevitable, but in our lifetimes — sooner than later, is what keeps me going and checks the "purpose" box.
Lean on that needle! ...a little harder now ...I think it's budging... Onward!!!

2024-08-20 21:26:16 UTC

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

2024-08-17 00:19:53 UTC

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

2024-07-27 19:54:43 UTC

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!

2024-07-04 20:29:47 UTC

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!!! 🙏

2024-06-12 14:10:30 UTC

- reply

as mechanic said:
since the car body is ground, open the circuit on negative terminal first when disconnecting then close the circuit last on negative terminal when reconnecting -- so that you don't accidentally close that circuit with your wrench when working on the positive terminal.

2024-06-12 14:03:38 UTC

- reply

I wouldn't make it in "sales" because I'd be too honest with potential customers about the downsides.
But there are exceptions for products and projects that are so good that I'd be able to shill with, if not better than, the very best of 'em.
Here's one.
#note1c4u…32pq

2024-05-31 14:32:34 UTC

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

2024-05-30 11:21:37 UTC

- reply

🔥
#note1zav…82r6

2024-04-05 17:59:23 UTC

Hi @npub1jmr…ukpd,
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

2023-12-25 12:43:29 UTC

- reply

Beautiful Christmas message Seed. Merry Christmas to you and yours!

2023-12-18 22:20:47 UTC

- reply

toggle bg to fg...
* based on a threshold triggered, w/ an icon to indicate trigger type?
* based on fees
* based on price
* for significant block-heights
???

2023-11-23 11:45:49 UTC

- reply

When will regulators hold OFAC compliant miners responsible for failing to protect users from such obvious mistakes? /s

2023-11-23 08:51:03 UTC

- reply

#note1xfa…qfuh
I confirm.

2023-11-07 12:05:35 UTC

- reply

`vcgencmd otp_dump` will dump an RPi's otp registers, w/ entries 28 and 29 being the id and its ones-compliment. I don't know if the otp id is related to the etched id, but Im also not sure what the concern is.
Can someone enlighten me?

2023-11-06 13:38:44 UTC

- reply

"not nearly enough."
or is it
"thankfully, more than yesterday."
???

2023-11-06 10:38:49 UTC

- reply

Making it happen. Good job!

2023-11-03 11:35:35 UTC

With time, this one keeps getting better and better.
TGIF!
https://www.youtube.com/watch?v=RZVFTV4SV44

2023-10-31 10:03:54 UTC

🧀🗝 nacho keys == nacho cheeze 🧀🗝
Happy 15th "Bitchycoin" white-paper day!

2023-10-26 18:55:33 UTC

- reply

Maybe it's "Nah, no thanks!" tech? Same difference, better received.

2023-10-24 12:00:42 UTC

"Can you keep a secret?"
Asking seriously, while looking into the eyes of a fellow confidant, we might expect to hear a convincing "Yes I can, you can trust me."
But mostly, we know different. We've learned that this response is rarely the truth, if ever long-lasting.
Then again, there exist exceptional ones. I'm referring to all those who have reflected this question inwards, upon themselves, to discover its nuance, adding:
"But am I sure?
That this secret is truly of my creation?
And that I will never forget it?
And that it will remain exclusively mine?"
Many have taken a deep dive into this reflection. They've iterated alone and alongside scrutinizing peers, exhausted imaginative role-playing scenarios in theory, and dissected tragic failures in real life. Competing atop the shoulders of giants, they continue evolving material and digital solutions for mastering one of the fundamental user challenges required by freedom-tech.
And they keep releasing their refined knowledge to all, free and open,
* to harden the individual -- thereby the collective,
* to level the playing field -- turning the tables,
* and to claw-back freedom, for our children,
in order to rectify many of the violated-promises that have been left behind for us.
They have enabled anyone, who reflects on that nagging question, to easily and honestly answer:
"Yes, now I can!"
To the #seedsigner community, which I stumbled into one year ago today, and to all of you exceptional ones, you legendary giants -- past and present, from my family to yours,
Thank you!

2023-10-23 06:54:58 UTC

Recently after a series of careless "follow" actions (I'm sure I signed these events without careful review), I found I was following just 1.
Was it iris, coracle, nostrgram or snort? I'm not sure but I suspect it was iris.
Many were restored via nostrgram and now I've saved a '~/kind3.json' locally, which I'll make a habit of doing. But, what's the correct to avoid losing contacts?

2023-02-19 14:35:00 UTC

- reply

"back at'cha", said f7849c6c90c4ffe3be8059bd899d85d3fd38c0bb79749f9e79653820351ad8f8

2023-02-19 14:27:26 UTC

"hello world", said npub177zfcmyscnl7805qtx7cn8v9607n3s9m096fl8nev5uzqdg6mruqshdp8e