OK I did it. Instead of a P2TR address for your npub, I implemented Silent Payments. I managed to: 1. Create a Silent Payment address from my npub, 2. Send a Silent Payment from Cake Wallet (the only wallet I could find that supported it) 3. Detect the valid transaction outputs that containthe Silent Payment 4. Swept the funds from the Silent Payment to a fresh bitcoin address that I control using the corresponding nsec (redacted in diagram, below, of course) So the bottom line, I have shown that any npub can receive silent payments and sweep those funds to another wallet. Total privacy on the public blockchain. No one know I received or sent the funds. I have the command line working and I will figure how to wire this into the web app in the coming days. That should put an end to the debate of using your social nsec as a wallet. The command line looks like: $>openetr sweep-silent-payment NSEC TXID DESTINATION_ADDRESS /cc @Alex Gleason @Gigi @Vitor Pamplona @jb55 @Derek Ross #silentpayments image

Replies (51)

I really need to dig into this. I still don’t have a good understanding of how you can’t follow the inputs and outputs. Any recommendation for a video explaining this, not like using it but explaining how it works?
imo the SP address should be decoupled completely from the identity key and only announced via nostr. As built here it's derived from the npub. so it's still deterministic and computable from the npub by anyone, which is the nasty property of doxxcoin. And then it leans on the nsec for the sweep, exposing it to shell history etc. let me know if I'm missing something. I eat crayons.
yeah I was gonna say this. If its a default then thats still an issue for people targeting nsecs. Should be a separate address in the profile, but i can see the appeal of everyone having an address by default, even if it makes me a bit uneasy. Not like you can stop it
> That should put an end to the debate of using your social nsec as a wallet. It ends the privacy part of the debate, but not the 'dusty' part If we're going to have small amounts, let's try to do something to be more efficient (like make it an Ark vTXO)
For the record, these silent payments don't show up as time-stamped, public zaps, do they?
maybe silent payments will finally gain traction from this whole saga
It can start with the one generated from nsec, but users should be allowed to change it and then that one should be used by zapper...
If you add an SP address to your payment targets (like I just did), clients can simply default to that. You can't opt-out of npub-based SP addresses, but you can opt-in to a different address and publically signal that.
I think it's a reasonable balance and default to have that automatic SP address. New user comes, creates npub and they are immediately ready to accept bitcoin.
Not everyone can run a lighting node, not everyone can run a Bitcoin node. Not everyone can mine Bitcoin. Monero let's anyone participate, out of the box. Ever used the GUI or CLI? You'd know
Yes, but dust isn’t even a static thing so one day it might be okay to receive a transaction and a week later (or a year later) it’s unspendable dust.
This is the way to use an npub if it is to be done. Though I still don't think it's easier than Lightning. But it's a cool additional option for when on chain is indeed called for.
Only if you're going to set a MUCH higher minimum zap to go with it. A 21 sat on chain tx is impossible at even 1 sat/vbyte fees.
Yes, but this is about signaling which one you prefer people use. The user can define what they want in an event. But if they define nothing, the client falls back to defaults, so that the functionality is not broken. Same way we do relay selection.
zaps are public which is a feature so people can see who finds what content valuable. lightning has decent privacy features. ecash is even better. you can use other wallets in Primal that have whats called Nostr Wallet Connect. @Minibits is a good one to play with. @Gigi may be willing to fill you in further. Also @calle is leading the ecash charge. and the note below is next level, but also useful and bullish to see privacy built on bitcoin. View quoted note →
Dana Wallet is another great option for Silent Payments. Their block scanning worked better for me than Cake wallet. I also did some work on sending a Nostr encrypted DM to let the receiver know they've received a Silent Payment from you. They don't need to even scan, getting rid of the primary negative of Silent Payments: