📄️ Sending Zaps
As an open protocol, Zapf extends standard NIP-57 ↗ and LUD-16 payment flows with a permissionless identity resolution step. This lets your wallet or app route funds to user-friendly identifiers like discorduser@example.com.
📄️ Receiving Zaps
The Zap Protocol makes it effortless to receive Lightning payments directly to your own wallet using Nostr Wallet Connect (NWC).
📄️ Claiming Funds
If someone sends a zap to your Legacy Identity structure (e.g., your Discord account) before you have set up a Lightning wallet, the Zapf network does not reject the payment.
📄️ Adding a Legacy Identity Provider
As a permissionless protocol, Zapf lets anyone integrate a new Legacy Identity Provider (LIDP).
📄️ Running an Identity Authority (IA)
Zapf is an open, federated protocol. While zapf.app operates a public Authority, anyone can spin up their own independent Identity Authority (IA).
📄️ Evidence Sharing
Because The Zap Protocol is a federated open standard, users can strengthen their identity by having it verified by multiple independent Zap Settlement Providers at once.