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.

Reply to this note

Please Login to reply.

Discussion

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.