Skip to main content

What is Zapf?

Zapf is an open protocol and application bridging the Nostr and Lightning networks to web identities. Our mission is simple: Zap Anyone, Anywhere.

With Zapf, you can send micro-payments (zaps) to anyone using identifiers they already have—like an Email address, Discord ID, X handle, or Phone number—even if they haven't set up a Lightning wallet yet.

The Core Problem​

Traditional Lightning payments require the recipient to generate an invoice. This means both sender and recipient must be online, and the recipient must already have a wallet. This creates immense friction for onboarding new users to the Bitcoin economy.

The Zapf Solution​

Zapf introduces a non-custodial-first, federated proxy architecture built on open Nostr event kinds:

  1. Universal Identity: Map any abstract legacy identifier (email:loki@gmail.com) to a Nostr public key using Identity Authorities (IA).
  2. Fallback Custodial Proxy: If the user doesn't have a wallet, Zapf holds the funds securely via the Fallback Address and notifies them.
  3. Stateless Claiming: Users prove ownership of their legacy identifier via OAuth/OTP and decrypt funds directly using NIP-44, sweeping them to their own node.
  4. Verifiable Settlement: Every payment generates a cryptographically verifiable Zap Receipt (Kind 5521) or Payment Receipt (Kind 5522).

Key Features​

  • Decentralized Profiles: Users own their social graph and payment routing preferences via NIP-05.
  • NWC Native: Full support for Nostr Wallet Connect (NIP-47) for 1-click, non-custodial sending and receiving.
  • Flokicon Integration: Native support for high-speed, low-fee settlement using Flokicon (loki / mloki) alongside Bitcoin.
  • Protocol Extensibility: Anyone can run their own Identity Authority (IA) or integrate new Legacy Identity Providers (LIDPs).

Where to Next?​