Is there a NIP or something already which defines how silent payment addresses and/or BIP-353 identifiers are to be added to a nostr profile's metadata? #asknostr #devstr
Discussion
Also interested in the answer
Last time I shoved them in the kind0 lud16 if they came in the form of an email address, which is needless to say not okay 😆. So maybe just add “bip353” followed with address 🤷♂️
PayTo: Payment Targets (RFC-8905)
I remember nostr:nprofile1qqspdudqzqx5ellme3prp68qus5se3vynsddcexkv5la5p7qxxcswjcpzdmhxue69uhk7enxvd5xz6tw9ec82c30qythwumn8ghj7un9d3shjt3s0p3ksct59e3k7mf0mj6y3a wrote a nip proposal related to this some time ago
I tried a few times. nostr:nprofile1qqsd6ejdteqpvse63ntf7qz6u9yqspp4z7ymt8094urzwm0x2ceaxxgprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qg3waehxw309ahx7um5wghxcctwvshszythwden5te0dehhxarj9emkjmn99uugqss6 made a NIP I believe to put them in their own kind because we could never get anything through on the NIPs repo to put it in kind 0.
No clients support it afaik right now
I agree with Vitor on this point fwiw: nostr:nevent1qqsxt543ckp0d87eyk537q09fs0zp5ygm7pu0sz6zm9y5vz97vvnxrspzamhxue69uhkzarvv9ejumn0wd68ytnvv9hxgtczyphydppzm7m554ecwq4gsgaek2qk32atse2l4t9ks57dpms4mmhfxqcyqqqzvjsr76qaf
Spam the relays with a different event for every payment address that someone has and load all of them, every time you load their profile? And then you have to retool the clients, every time someone comes up with another payment address.
Nah, kind 0 and kind 10133 and you're done.
I proposed an idea that supports NIPs - that would probably help deal with what you've highlighted.... I called them Nostr Community Convention (NCCs)...