The wallet provider also needs to implement NIP-57 for Zaps to work.
KYC requirements a function of regulations where the provider operates, not how the user logs in (LN Auth).
Discussion
Thanks Nathan - if you are ok with follow up questions,
1) how to know which wallet has NIP 57?
I know WoS, Alby, Lightining TipBot, Zeus works based on users who have mentioned it on Nostr (i use the first 2) - how about the rest?
2) on LN Auth - so it determines custodial (3rd party with info) vs non-custodial ?
There's not a list of wallets that support Zaps that I know of. Eeasy enough to check, by seeing if a Zap works or is just a regular LN payment.
LN Auth can be done from either a custodial or self-custodial wallet. Its simply a way if linking an LN Wallet to a service, regardless of level of custodianship.
Make sense?
got it - on wallets supporting zap, i'm hoping to help ease up onboarding when new users ask abt this - so i probably go with suggesting what I know, works. on LN auth - understood on a surface level, which is good enough for now. I recall bluewallet removing custodial recently and its ability to link up to services (not their self custody wallet).
Thanks Nathan, I appreciate this !
Yeah, Blue removed custodial lightning as it was a regulatory liability for them. You can still connect it to other custodial services though or, even better, your own LN Node. 🤟