# Zapf Docs

> Zap anyone, anywhere

This file contains links to documentation sections following the llmstxt.org standard.

## Table of Contents

- [The Fallback Address](https://docs.zapf.app/concepts/fallback-address.md): How Zapf ensures payments never fail by safely holding funds for users without wallets.
- [Identity Authority (IA)](https://docs.zapf.app/concepts/identity-authority.md): An **Identity Authority (IA)** is a service that verifies a user's ownership of a legacy account (like Discord, X, or Email) and issues cryptograph...
- [Legacy Identity Providers (LIDP)](https://docs.zapf.app/concepts/legacy-identity-providers.md): A **Legacy Identity Provider (LIDP)** is any traditional identity or social platform that a Zap Settlement Provider (ZSP) uses to verify a user's o...
- [Verification Model](https://docs.zapf.app/concepts/verification-model.md): When a client application (like a wallet or a social client) parses a [Proxy Request (Kind 5523)](/protocol/on-behalf-zap-request-5523) or its resu...
- [Zap Settlement Provider (ZSP)](https://docs.zapf.app/concepts/zap-settlement-provider.md): The **Zap Settlement Provider (ZSP)** acts as the **Payment Processor** within the Zap Protocol.
- [Flokicon](https://docs.zapf.app/ecosystem/flokicon.md): **Flokicon** is the native currency and high-speed settlement layer deeply integrated into the open Zap Protocol network.
- [Discord](https://docs.zapf.app/ecosystem/lidps/discord.md): The Discord Legacy Identity Provider (LIDP) integration allows users to bind their Discord account to their Nostr public key. This lets anyone rece...
- [Email](https://docs.zapf.app/ecosystem/lidps/email.md): Email is the most widely used Legacy Identity Provider (LIDP). It lets anyone receive zaps using a standard email address.
- [Other Providers](https://docs.zapf.app/ecosystem/lidps/other-oauth.md): As an open protocol, Zapf is designed to be extensible. Independent Identity Authorities (IAs) can implement any number of Legacy Identity Provider...
- [Phone (RCS)](https://docs.zapf.app/ecosystem/lidps/phone.md): The Phone Legacy Identity Provider (LIDP) links a phone number to a Nostr public key so users can receive Lightning payments via text messages or m...
- [Telegram](https://docs.zapf.app/ecosystem/lidps/telegram.md): Integrating Telegram as a Legacy Identity Provider (LIDP) via OIDC.
- [X (Twitter)](https://docs.zapf.app/ecosystem/lidps/x.md): The X (formerly Twitter) Legacy Identity Provider (LIDP) integrates one of the web's largest public social graphs into the open Nostr and Lightning...
- [Lokihub](https://docs.zapf.app/ecosystem/lokihub.md): **Lokihub** is a self-custodial Lightning wallet and node interface for the [Flokicon](/ecosystem/flokicon) ecosystem.
- [Supported Wallets](https://docs.zapf.app/ecosystem/supported-wallets.md): Zapf is a non-custodial-first, open protocol powered by **Nostr Wallet Connect (NWC - [NIP-47](https://github.com/nostr-protocol/nips/blob/master/4...
- [Adding a Legacy Identity Provider](https://docs.zapf.app/guides/adding-lidp.md): As a permissionless protocol, Zapf lets anyone integrate a new Legacy Identity Provider (LIDP).
- [Claiming Funds](https://docs.zapf.app/guides/claiming-funds.md): If someone sends a zap to your Legacy Identity (e.g., your X handle, Telegram username, or GitHub account) *before* you have set up a Lightning wal...
- [Evidence Sharing](https://docs.zapf.app/guides/evidence-sharing.md): Because the Zap Protocol is a federated open standard, users can strengthen their identity by having it verified by multiple independent Identity A...
- [Receiving Zaps](https://docs.zapf.app/guides/receiving-zaps.md): The Zap Protocol makes it effortless to receive Lightning payments directly to your own wallet using **Nostr Wallet Connect (NWC)**.
- [Running an Identity Authority (IA)](https://docs.zapf.app/guides/running-an-ia.md): Zapf is an open, federated protocol. While `zapf.app` operates a public Authority, anyone can spin up their own independent Identity Authority (IA).
- [Sending Zaps](https://docs.zapf.app/guides/sending-zaps.md): As an open protocol, Zapf extends standard [NIP-57](https://github.com/nostr-protocol/nips/blob/master/57.md) ↗ and LUD-16 payment flows with a per...
- [What is Zapf?](https://docs.zapf.app/intro.md): Zapf is an application and Zap Settlement Provider (ZSP) that bridges the **Nostr** protocol and **Lightning** network to web identities by impleme...
- [IA Attestation](https://docs.zapf.app/protocol/ia-attestation-35522.md): As part of Zapf's open identity model, a **Kind 35522** (IA Attestation) is the cryptographic proof generated by an Identity Authority (IA) stating...
- [Identity Connection](https://docs.zapf.app/protocol/identity-connection-35521.md): A **Kind 35521** is a publicly verifiable Nostr event published by an end-user to announce that their Nostr public key is linked to a Legacy Identi...
- [LNURL Integration](https://docs.zapf.app/protocol/lnurl.md): The **Zap Protocol** implements the open **LUD-06** and **LUD-16** standards to bridge Lightning Network wallets with Nostr identity resolution.
- [On-Behalf Zap Request](https://docs.zapf.app/protocol/on-behalf-zap-request-5523.md): A specialized NIP-57 variant designed to explicitly proxy legacy off-chain identities
- [Zap Receipt](https://docs.zapf.app/protocol/zap-receipt-5521.md): A **Kind 5521** (Zap Receipt) is the open standard published by a Lightning Network provider *after* a Lightning invoice has been successfully paid.
- [Zap Request](https://docs.zapf.app/protocol/zap-request-5520.md): To initiate a payment across the open network, a client generates a **Kind 5520** (Zap Request) event.