newtonick / Nick Klockenga is on Nostr

seedsigner contributor among other things

Last Notes

2026-01-06 01:49:30 UTC

- reply

WORD5 #459 5/6
⬛🟧⬛🟧⬛
🟪⬛🟪🟪🟪
🟪⬛🟪🟪🟪
🟪⬛🟪🟪🟪
🟪🟪🟪🟪🟪
https://word5.otherstuff.ai

2025-12-16 13:18:31 UTC

- reply

Can confirm. Blink and you’ll miss it!

2025-09-28 18:12:34 UTC

- reply

Update:
I now see 4 out of 68 peers identifying as Knots. 7 of these peers are relaying sub 1 vbyte txs; that seems wild to me.

2025-04-24 12:33:55 UTC

- reply

I didn’t think Apple allowed in app updates not through the App Store.
https://image.nostr.build/f7a93376f3a1d7d2777c15e7fa7992710f1b46659742d12702337dbd0f9b96a7.jpg

2025-02-05 02:44:43 UTC

SeedSigner v0.8.5 has reproducible builds from source. This means sole trust in SeedSigner the person (or any other SeedSigner contributors) isn’t needed for the image that most people run on thier SeedSigner. This trust can be distributed through others attesting they to can produce the same image byte for byte.
If you have docker installed, a few hours of CPU cycles available, then you too can contribute and attest that all 4 device images built from source match the released binaries.
```
git clone --recursive https://github.com/SeedSigner/seedsigner-os.git
cd seedsigner-os
export DOCKER_DEFAULT_PLATFORM=linux/amd64
export RELEASE_TAG=0.8.5
git checkout $RELEASE_TAG
git submodule init
git submodule update
for device in pi0 pi02w pi2 pi4
do
SS_ARGS="--$device --app-branch=$RELEASE_TAG" docker compose up --force-recreate --build
done
cd images
shasum -a 256 seedsigner_os.0.8.5*
```
My personal attestation:
bcb901e27d309d85f086dc80b49b153d6b1caab2247eba2811731384d58f2f3e seedsigner_os.0.8.5.pi0.img
398d9bf9cda0858fe97c0788b353194c1c902335a858b7dbf5d7b213bda75d96 seedsigner_os.0.8.5.pi02w.img
1e93a82e62d4a1defbdc777a6762a813f4cb5c3ef9090da0bd07542dfd6f62bf seedsigner_os.0.8.5.pi2.img
d298ffad3c765e11e48873efc6d1c65e4230528fde4d5bd4701bb507acbf493c seedsigner_os.0.8.5.pi4.img
matching https://github.com/SeedSigner/seedsigner/releases/download/0.8.5/seedsigner.0.8.5.sha256.txt #note1pv8…5s4q

2024-12-26 23:10:52 UTC

¡SeedSigner en español está aquí!
Release Candidate 1 for 0.8.5
https://github.com/SeedSigner/seedsigner/releases/tag/0.8.5-rc1
8f881e1c18f2ecee9a39a85900dc5dfbda0d613a7f1789adec64bd2258d4f970 seedsigner_os.0.8.5-rc1.pi0.img
7d731c6458e13b5090284c53fe859ba98ed3178b3690e3af29f38f4c2b902ec3 seedsigner_os.0.8.5-rc1.pi02w.img
d469d31feba8df78e4afb7514cbac50dd72cc1bd22717e1921df819aa8f13562 seedsigner_os.0.8.5-rc1.pi2.img
650dac5cf7608b9259e7272c778584104862c60089807f1d6266e374b055486a seedsigner_os.0.8.5-rc1.pi4.img

2024-11-27 13:49:08 UTC

- reply

Damn. A cold reminder that many Bitcoin companies are governed by fiat rules. I’m sure there is some legal reason they don’t say anything that protects them while screwing you.

2024-09-02 19:08:30 UTC

@npub1qny…95gx in the most recent @npub10ut…xdlq you spend a few minutes addressing accusations regarding your integrity around simultaneously supporting @npub17ty…3mgl and having a vested financial interest in the success of Cold Card. You said the SeedSigner project is “incredibly important” but continue in the same breath to deny they are competitors and described SeedSigner as only reasonable to be used as a fallback if we lived in a world where devices like Cold Card don’t exist. Far from an endorsement.
You have historically supported the SeedSigner project and I appreciate the support. There’s 100+ ways the SeedSigner project could be better. Your most notable grievance of SeedSigner seems to be solely focused on physical security attributes when comparing the two air gapped Bitcoin signing devices. Specifically you don’t like that SeedSigner doesn’t have a secure element.
Secure elements are great tech, but you never cover the actual trade offs on RHR. You gloss over how Cold Card is verifying firmware at boot on behalf of the user. You don’t discuss the trade offs at all. The verification of firmware at boot on a Cold Card requires trust in Coinkite. The user isn’t verifying, Coinkite is. You also make it sound like it’s an impossible task to verify firmware for SeedSigner.
IMO you’re getting sucked into stupid polarizing debates around Cold Card vs SeedSigner. I think Cold Card and SeedSigner are both great in their own ways. They make different trade offs and actually complement each other really well in a multisig setup with Sparrow Wallet. I personally have no issue with you recommending a Cold Card over a SeedSigner if you prefer the trade offs. Totally reasonable if you asked me. It’s way more important people self custody Bitcoin using cold storage.

2024-08-14 22:39:05 UTC

- reply

I wonder what the “associated fees” are?

2023-11-25 02:43:56 UTC

- reply

The way I read @npub1hea…g9v2’s feedback on Github is that the criticisms are more than pragmatic. He has a list of drawbacks. The lack of fountain encoding and well defined type structures (for example output descriptors) are the biggest gaps between UR and BBQr.
Many wallets like Blue Wallet, Nunchuck, and Green Wallet have adopted the BC UR standard. I don’t see what BBQr brings to the table for users of animated QRs. It doesn’t appear to solve anything for the end user over BC UR. What am I missing?
I’m not saying that BC UR is perfect. I could come up with a long list of things I wish were different about the BC UR standard.

2023-11-25 02:13:28 UTC

I’d love to listen to @npub1qny…95gx interview @npub1az9…m8y8 and @npub1hea…g9v2 on Citadel Dispatch about BBQr (http://BBQr.org).
Craig has years of experience implementing BC UR 2.0 into Sparrow Wallet and has actively worked to improve this standard in that time. I can think of no one better to discuss trade offs of BBQr vs UR.
I’d also like to hear from NVK why he thinks a new animated QR standard is needed. I have experience using/implementing UR and when I read the BBQr spec I wish it had some of the simplicity proposed in the BBQr spec.
I honestly think it could be a great (and drama free) conversation. IMO the three of you have mad respect for each others work. There are dozens of us who care about animated QR standards and would find this conversation thrilling. 😂

2023-07-24 00:18:54 UTC

- reply

Regarding #3, does this also mean mempool 3.0 will not work with other Electrum Server implementations like Fulcrum?