👀 I'm listening.

WHY CAN'T WE PAY WITH SOMETHING OTHER THAN LIGHTNING, SO THAT USERS ARE FORCED TO USE ECASH "FOR THE UX" OR HOST A FRIGGIN SERVER?

I have a Bitcoin wallet, you know. Everyone and their mother has a Bitcoin wallet. We're not only moving individual sats, anymore.

nostr:nevent1qvzqqqqqqypzq9h35qgq6n8ll0xyyv8gurjzjrx9sjwp4hry6ejnlks8cqcmzp6tqyg8wumn8ghj7mn0wd68ytnddakj7qpqcm3uxxsx0rm9src55cs8u920yymfym5tpl7jecu3pdun8fytem0qu9nsmg

Reply to this note

Please Login to reply.

Discussion

This is so much easier than zaps too... The receipt event can just be generated by the user istead of the lnurl server and it would just show the txid.

I honestly don't know why this didn't come first or why it doesn't already exist.

I'll make the PR for NIP24 and put the addresses in my metadata and implement an example if I have some support.

nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug of I workshop this, is it something you would be willing to implement in Amethyst? Similar to how you have a tag for GitHub verification, it would be a tag with the asset and address? I'm trying to think of how I should specify the network too, so you could do USDT over multiple networks.

Like this. Doesn't require a PR, does it?

https://github.com/nostr-protocol/nips/blob/master/39.md

Couldn't you just add a verifying message to a transaction? Nostr ordinals LOL.

I think you could absolutely put a nostr event in an OP return.

Noster doesn't have to verify the payment, the blockchain will. The original event would have the transaction ID referenced in it.

Then it would be a new nip how I'm thinking right

I guess if you just consider the wallet an external identity then no it could be implemented just like this nip here. And it could be implemented right now. Hell you don't even need to implement actually opening a wallet You could literally just copy paste the address on the client.

Sure, just add to the metadata. A simple PR should do it.

An I tag is in my metadata for a BTC receiving address. Lmk what you think of this scheme. I'll have a client up tomorrow to look at it.

Just realized it should probably be BTC:Bitcoin:

Instead of how I currently have it.

ark ? 😁

this.

the problem is not being slow. it's fees. ppl don't even zap 1000 sats now imagine 10 usd fees. but nostr is permissionless it's just a matter of implementing.

I have people zapping me large enough amounts, that the fees are not an issue. People are moving hundreds or thousands of dollars over ecash, at the moment. Kinda crazy.

And really is asking for a rug pull. 🤷‍♀️

large payments yes onchain but that is not the norm on Nostr, makes sense to be LN first/mostly. Still you have some problems, if you use a static address you loose your privacy, so it would be better to use paynim or silent payments, but not all wallets support these. I think it would be possible to run a simple app on any always on pc/laptop that would generate bitcoin addresses from your wallet, and nostr clients could just send a specific nip04 to your app npub to request an address.

Running a server (that's a server, not an app, as it's constantly running a service) is the thing we're trying to get around.

I think we can see, that Nostr has been steadily discouraging self-custody options and funneling everyone into "private" and "good UX" e-cash. I'm interested in some pushback. E-cash is probably less-secure than Monero or USDT, in practice, as the chances of getting rugged are quite high.

And what is the norm, depends upon the use case. We should maybe think harder about use cases, where people might want to move more than 1000 sats. Those use cases apparently exist and aren't rare, but people shouldn't be using ecash for them, out of desperation and exasperation.

Best options silent payments or paynym, eg: https://paynym.rs/+nappydirection53 what matters is the payment code.

Yeah, we can use those.