Oh, did @ZBD put KYC on incoming #zaps? We had it working with @zapplepay a few weeks ago, maybe they cut that off. Kind of a shame to build something on open standards and then ditch the standards.
I have no idea; I don’t work for nostr:nprofile1qqsv73e7h6tndwngn3ccmc74auufpx722ldncw8rl8087hddljyw6mcpzdmhxw309ucnydewxqhrqt338gmnwdehv07p8s
I know, but I’m not going to put in any work to try to figure out how to zap the zebs. It’s not my battle to fight.
its geofenced. eg if you’re in FL, WA, etc youll get an error back when attempting to fetch an invoice from their ln provider
Heaven forbid someone in New York is allowed to send half a cent to someone in New Jersey.
This is what I assumed might be happening after my little imromptu trial and error test. I don’t understand why it matters where the sender is located since I’m not a ZBD customer/user. I am not bound by their terms of service. The nature of VPNs and the lightning network means that a sender could potentially be anywhere in the world, and the payment could route through multiple of their “prohibited” jurisdictions before it reaches the ZBD user’s wallet. Blocking outgoing payments is bad enough. Blocking incoming payments is even worse. I would not recommend anyone use ZBD for nostr and lightning.
Yeah, this really is the last straw. @ZBD became a shitcoin.