Freakoverse's avatar
Freakoverse nabandondelivera 4 days ago
Nostr Silent Payments (NSP) (sorry for the shit quality) Send to random addresses derived from and controlled by the recepient's npub. Receive to random address derived from and controlled by your npub. Bitcoin and other compatible chains (Yes, silent shitcoin sending on nostr). Compatible with most/all wallets (the transacations part), you don't have to use a special wallet to send a transaction (but of course you'd need the client to be able to send No scanning/processing blockchains, an encrypted notification event is sent (by an ephemeral key) to the recepient's user-relay-list, then upon discovery and confirmation it would be saved (the tweak) to a self-encrypted event list. The sender would also have a self-encrypted event list that stores transactions they've sent (just in case). For sending from an NSP wallet, Bitcoin and other UTXO-based won't have trouble as it'll behave like other wallets combining multiple inputs to an output. However, the luxury isn't available for account-based addresses, you have to manually send out one address at a time, and if you receive a token on them but don't have gas, you have to gas up one by one as well (that of course sucks, but that's the system you're dealing with, however, I did add a system to automate adding gas to each of the needed addresses (maybe I should add an automated system as well for the send part... dunno). For silent (?😅) zapping, it'll be a private (another '?😅') zap if you want to do it (slap an a or e tag for the event your zapping), where only the recepient can decrypt the zap and confirm if it's legit to see it in the UI (client handles this). Notification kind: 1604 Records: NIP-78 Any of this good? bad? horrible? Who knows, maybe a lot of funds will be lost because it can easily happen (i accidentally lost a few sats while testing this xD), but hey it's here we can play with it (haven't updated DENOS repo with this yet, will do it later) NIP-NSP link:
Gitea
DNN/docs/NIPS/NIP-NSP.md at main
DNN - A decentralized, Bitcoin-anchored naming system for nostr and the web.

Replies (8)

Freakoverse's avatar
Freakoverse nabandondelivera 4 days ago
yea i thought of having some sort of tiny hint in op_return, but then the sender would need to use a wallet that does this which brings it closer to what Bitcoin SP does kind of in terms of needing to use a wallet that supports Bitcoin SP flow. Also I don't think I can add stuff in other chains nessarily? I guess where I'm going with this is: Discover valid sends > save them in your own nip78 > empty them out > clean up The sender, assuming a nostr user utilizing a client/signer that supports this, would also have his own nip78 of what he sent (same cleanup of empied balances) as another just-in-case sort of thing where he can rebroadcast or republish if the event got lost. Is there a risk? yup, but hey draft 1 or something x3 I'll probably add a warning on this NSP page in this signer mention the loss risk.
Freakoverse's avatar
Freakoverse nabandondelivera 4 days ago
I looked at this briefly in the past before and have since forgotten about it. Will look at it again. I thinking somone is working on Bitcoin SP implementation, and I made this NSP thing, perhaps someone will come along and make a BIP47 implementation. We'll have 3 to play around with and see how things fair x3
1 replies ↓
Freakoverse's avatar
Freakoverse nabandondelivera 2 days ago
*(but of course you'd need the client to be able to send the nostr notification, either from the sender or wherever this has been implemented, like a client or a site that decided to put this on their donation page or eCommerce) (Yes I forgot to continue writing that =P)
↑