Zapf Docs
Integrate lightning-fast micro-payments into your platform using identities your users already have.
A recognized Fun Enhancement Possibility (FEP) powering the Web of Fun (WoF).
AI Context Files
Load the full Zap Protocol spec into any AI assistant or LLM chat for accurate, grounded answers.
Agent Skill
Equip your AI agent with the Zap Protocol as a callable skill — resolve identities, build zap flows, and query specs directly from your agent.
npx skills add ohstr/zap-protocolExplore the Protocol
Everything you need to understand, implement, and integrate.
Concepts
Identity Authorities, LIDPs, the Verification Model, and the Fallback Lightning Address.
- Map traditional identities (Discord, Email, Phone) to Nostr pubkeys
- Non-custodial first — Fallback Lightning Address for users without wallets
- Cryptographic attestation model with portable evidence sharing
Protocol Specs
Open Nostr event kinds and multi-chain LNURL integration.
- Kind 5520 (Zap Request) · Kind 5521 (Zap Receipt)
- Kind 35521 (Identity Connection) · Kind 35522 (IA Attestation)
- LUD-06 / LUD-16 LNURL with multi-chain denominations
Guides
Step-by-step tutorials for implementors and users.
- Send and receive zaps to any identity
- Claim custodial funds with NWC wallets
- Add new LIDPs and share evidence between IAs
Ecosystem
Supported chains, wallets, and identity providers.
- Flokicoin — multi-chain Lightning settlement
- NWC wallets: Alby, Mutiny, Zeus, Strike
- LIDPs: Discord, Email, Phone, X, and custom OAuth