@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 a fork of Signal with self-custodial Bitcoin Lightning. All your chats and your entire network move along with it."
(ODELLXYZ) and nostr:npub1guh5grefa7vkay4ps6udxg8lrqxg2kgr3qh9n4gduxut64nfxq0...
You can even send sats directly to the recipients’ lightning address which I thought was pretty cool
For some reason I thought it’ll only work for lightning invoices
For some reason I thought it’ll only work for lightning invoices
Someone from Nostr should make a QuickBooks alternative. That would be killer. I hate uploading all my data to QB. It is easily the biggest data leak i have.
I'd fund the development if anyone is up...
I’m working on something similar to this but it’s engineered specifically for Bitcoin-backed loans, but I can extract the engine and build a QuickBooks alternative around it
Actually depending on the situation I wouldn't mind placing the order on the webpage. If we're doing this through phones then do it right. A superfast simple website, click to order, pay with Bitcoin,...
It sucks that a lot of major fast food restaurant establishments are pushing towards non-contact menu ordering through their apps and offer rewards platform-locked to their services only
Which also requires signing up for them to sell your data as part of their revenue model
Family/dine-in restaurants may be going down that direction, too, for convenience and efficiency because their business model greatly depends on online advertising to bring in more foot traffic but at the cost of data retention to sell to advertisers
Even SteakNShake requires an account or data before checkout and reward distribution
Which also requires signing up for them to sell your data as part of their revenue model
Family/dine-in restaurants may be going down that direction, too, for convenience and efficiency because their business model greatly depends on online advertising to bring in more foot traffic but at the cost of data retention to sell to advertisers
Even SteakNShake requires an account or data before checkout and reward distribution
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! 🫂
1❤️2
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❤️2
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
