OceanSlim on Nostr: It's taking too long to ask how I should do it. I'm about just say fuck it and make a ...
It's taking too long to ask how I should do it. I'm about just say fuck it and make a new nip after I make an implementation and we can workshop it after.
I think a new "w" tag in the kind 0 with an array that looks like
["BTC:bitcoin:<address>], or [XMR:monero:<address>],
[<ASSET>:<network>:<address>]
The "w" tag is an "Accepted Form of Payment"
You can have as many as you want as long as the network and asset are unique from each other.
Client can decide what to show.
Should define a few networks in the nip but it should be noted that clients can interpret the w tag however they want.
You could even deprecate ln address in the content of you did something like
w ,
BTC:lightning:<address, lnurl, bolt12>
I think a new "w" tag in the kind 0 with an array that looks like
["BTC:bitcoin:<address>], or [XMR:monero:<address>],
[<ASSET>:<network>:<address>]
The "w" tag is an "Accepted Form of Payment"
You can have as many as you want as long as the network and asset are unique from each other.
Client can decide what to show.
Should define a few networks in the nip but it should be noted that clients can interpret the w tag however they want.
You could even deprecate ln address in the content of you did something like
w ,
BTC:lightning:<address, lnurl, bolt12>