@silentius
Relays (5)
- wss://relay.damus.io/ – read & write
- wss://nos.lol/ – read & write
- wss://relay.nostr.band/ – read & write
- wss://relay.primal.net/ – read & write
- wss://relay.divine.video – read & write
Recent Notes
It's cool to see how many people have started genuinely caring about their privacy after governments began pushing heavily for age verification and VPN bans. It's very validating to know that people c...
You’re here! I’ve been following you on X (with a lurker burner ofc) for YEARS & so so glad you’re here with us outside of X 🥹
You’re my fav (and only) Brave influencer and hope to see more of your thoughts & content here on nostr! 🫂
You’re my fav (and only) Brave influencer and hope to see more of your thoughts & content here on nostr! 🫂
Updated Nostr Silent Payments gist at the link below.
The gist now includes two example scripts to validate a silent payment transaction and sweep a silent payment transaction. The example scripts ha...
@Tim Bouma pushed three NIPs to close the full NSP stack – derivation (PR #2355 https://github.com/nostr-protocol/nips/pull/2355), receipt notifications (PR #2362 https://github.com/nostr-protocol/nips/pull/2362), and a Silent Wallet Connect NIP modeled on NIP-47 (PR #2369 https://github.com/nostr-protocol/nips/pull/2369).
The stack handles on-chain privacy cleanly but the wallet service is still a surveillance point – a third-party operator accumulates a complete payment graph regardless of what BIP-352 does on-chain. Posted a design note on splitting the wallet service into two blind TEE-attested components so neither operator can reconstruct who paid whom.
The TEE guarantee is probabilistic not mathematical and doesn’t touch amount privacy or timing correlation – but it closes the operator surveillance gap. Curious if this maps to anything you’ve been thinking about on the OpenETR side.
https://gist.github.com/silentius-satoshi/fd4a4e479f8b9540436b9058b7b158bd
The stack handles on-chain privacy cleanly but the wallet service is still a surveillance point – a third-party operator accumulates a complete payment graph regardless of what BIP-352 does on-chain. Posted a design note on splitting the wallet service into two blind TEE-attested components so neither operator can reconstruct who paid whom.
The TEE guarantee is probabilistic not mathematical and doesn’t touch amount privacy or timing correlation – but it closes the operator surveillance gap. Curious if this maps to anything you’ve been thinking about on the OpenETR side.
https://gist.github.com/silentius-satoshi/fd4a4e479f8b9540436b9058b7b158bd
13❤️1
Signing up with SMS seems so out-of-touch with the current reality of today’s technology & privacy methods
I get that friction has to be implemented somewhere, but SMS is def not the way to do it
potential malicious data harvesting on obsolete tech is part of why we left legacy platforms and migrated to nostr
I get that friction has to be implemented somewhere, but SMS is def not the way to do it
potential malicious data harvesting on obsolete tech is part of why we left legacy platforms and migrated to nostr
👍️1
Patiently waiting on the Neuralink BIP-174 integration. ColdCard is still the best airgap on the market — but nothing beats signing a PSBT with your skull. Until then: get a ColdCard.
https://npub1...
there’s gotta be a better port than that… I wouldn’t trust myself going to sleep when someone can just hijack my skull with malware
I was driving through the middle of nowhere when I ran over a hoe in the road. Instant flat tire.
Instead of stressing, I stepped out of the car, soaked in the sunshine, and decided to embrace the whi...
I couldn’t help but think of this part lmao
love this “glass half full” mindset!! 🥹 and super glad you’re safe!
love this “glass half full” mindset!! 🥹 and super glad you’re safe!
❤️1🤙1
Trying to create a eBay listing automation workflow for my dad using Google Lens & Gemini (based on his preference) which involves using their API keys
and came across this for the first time. What the f?
and came across this for the first time. What the f?
👀1
Read my comment in the GitHub repo. Interesting times ahead!
I worked on the NIP spec last night and just uploaded the updated version - let me know what you think of it & also left you a technical question that needed clarification
I think your npub-derivation approach is the most trust-minimized implementation of the other iterations, but there’s still some work to do on client-side guidance
But for now, the foundation of NSW seems promising
I think your npub-derivation approach is the most trust-minimized implementation of the other iterations, but there’s still some work to do on client-side guidance
But for now, the foundation of NSW seems promising
❤️1
We've had some interesting insights. Can we chat via DM or Signal?
Sure! Does White Noise work for you? I think we need to update it
Also sorry for the late response, spent all morning catching flights
Also sorry for the late response, spent all morning catching flights
1
We settled on nostr-sp/scan and nostr-sp/spend what are you proposing? It is still early and we can change.
The tag strings match - great!
The question is the derivation method. Your diagram shows BIP32. The NIP draft uses BIP340 tagged hashes: scan_privkey = int(tagged_hash(“nostr-sp/scan”, sk)) mod n. Same tag strings, different operation, different output keys.
Which does your code actually use? If it’s BIP32 I can align the NIP to match.
Either way let’s nail this down - here’s the draft: https://github.com/nostr-protocol/nips/pull/2355
The question is the derivation method. Your diagram shows BIP32. The NIP draft uses BIP340 tagged hashes: scan_privkey = int(tagged_hash(“nostr-sp/scan”, sk)) mod n. Same tag strings, different operation, different output keys.
Which does your code actually use? If it’s BIP32 I can align the NIP to match.
Either way let’s nail this down - here’s the draft: https://github.com/nostr-protocol/nips/pull/2355
2
nostr:nprofile1qqszd44fgen4ucpl3hjt7muuaazzqdahp3lwu9c07phdweelcdxf3ugpzpmhxue69uhkummnw3ezumt0d5hszrnhwden5te0dehhxtnvdakz7qg6waehxw309aex2mrp0yhxwet5v9kxy7fwvdhk6tmkxytswl7z plz confirm
Literally was about to request further clarification from @Noshole aka the hummingbird ballsack babies whisperer
1❤️1🔥1😂1