📄️ Sending Zaps
Sending a Zap via Zapf follows the standard NIP-57 and LUD-16 payment flows, but adds an identity resolution step. This allows your wallet or app to send funds to user-friendly identifiers like discorduser@example.com.
📄️ Receiving Zaps
Zapf 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
To build a more connected web, Zapf encourages developers to integrate new Legacy Identity Providers (LIDPs) into the network.
📄️ Running an Identity Authority (IA)
While zapf.app operates the primary Identity Authority for the network, the protocol is federated. Anyone can run their own IA.
📄️ Evidence Sharing & Cross-IA Verification
Because Zapf operates on a federated multi-IA model, users may want to have their Legacy Identity Provider (LIDP) account verified by multiple different Identity Authorities at once (to increase trust and resilience).