Hey daniel I noticed I cant zap you on nostruddle and amethys now?
Discussion
I’m using an nostr:npub19tcpurtt6xulhw0r6sc404j9jraj0h8me2lzs7z2tqewz7l0hpas59nlea Ghost address on my node, and most people have been able to zap. 👻⚡️
What wallet are you using?
Actually I just logged into nostrudel myself and I see that my ⚡️ button is inactive.
nostr:npub18yvpnchj7yaepjk8yz2pn66hfmmup505aqvx0lpyc3aree0g5fyq8clpz3 Any idea why this is happening?
Yah just noticed that but mine is fine so know it should be working. Why had to bring it up cause noticed others were unzappable now with same zapurl as they always had.
No idea! Could it be the stench?
I'm not sure what logic nostrudel is using... Does it require nip 57?
I'm able to zap you just fine from Amethyst
nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr Any ideas? Maybe you and nostr:npub18yvpnchj7yaepjk8yz2pn66hfmmup505aqvx0lpyc3aree0g5fyq8clpz3 can test this out.
nostr:npub1aeh2zw4elewy5682lxc6xnlqzjnxksq303gwu2npfaxd49vmde6qcq4nwx it looks like your lightning address is missing the "allowsNostr" field. noStrudel relies on that field to know if the address is zappable
https://ghst.to/.well-known/lnurlp/daniel
I don't know what ghost addresses are but they might not support zaps
Hmm, is this a NIP-57 field? I can get zaps on pretty much all other clients at this address. Sounds like something nostr:npub19tcpurtt6xulhw0r6sc404j9jraj0h8me2lzs7z2tqewz7l0hpas59nlea has to enable.
it probably still works as a lightning address, but for it to be a "zappable" address is has to be able to create and publish the "zap receipt" event https://github.com/nostr-protocol/nips/blob/master/57.md#appendix-e-zap-receipt-event
The "allowsNostr" field is a way for the LNURL server to let clients know that it can publish zap receipts