@jdlcdl
80% bug-fix, 19% new-bugs.
No relay list published yet.
Recent Notes
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
~
```
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
~
12❤️3🤙2₿1☦️1♥️1❤️1
Why I'm for loosening the OP_RETURN limits ⏎
- In practice, OP_RETURN is already unconstrained: see Carman's OP_RETURN bot or Portland's Slipstream.
- Encoding arbitrary data via OP_RETURN is far...
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).
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).
RIP, a lot of files are corrupted...
https://nostr.download/c1f041dab282be896f5c85cf6aacc7b4dad2cfec89059723d74574882e50abc7.webp
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.
RIP, a lot of files are corrupted...
https://nostr.download/c1f041dab282be896f5c85cf6aacc7b4dad2cfec89059723d74574882e50abc7.webp
What does "corrupted" mean?
Does it really the case that those files' contents don't each hash to their name?
Does it really the case that those files' contents don't each hash to their name?
1
Hoping to clarify what seems to be a misunderstanding by nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx about how the Pi Zero hardware shapes the nostr:npub17tyke9lkgxd98ruyeu...
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.
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.
1👍1💜1
WHAT IS THE POINT OF FUCK YOU TECH IF YOU ARE NOT WILLING TO SAY FUCK YOU
Maybe it's "Nah, no thanks!" tech? Same difference, better received.