Skip to main content

Claiming Funds

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 wallet, the Zapf network does not reject the payment.

Instead, the funds are safely escrowed via the Fallback Lightning Address mechanism. This guide explains how to claim those funds through your Connections page.

How to Claim​

1. Log in​

Visit zapf.app/login and authenticate with your Nostr key. If you don't have one yet, the login flow will create one for you and guide you through connecting a wallet.

2. Go to your Connections page​

After logging in, navigate to your profile and open the Connections tab (zapf.app/{your-id}/connections).

This page shows all Legacy Identity connections linked to your Nostr key — X, Telegram, GitHub, Instagram, email, and domain — along with any pending balances held in custodial fallback for each one.

3. Claim pending funds​

For any connection showing a pending balance, click Claim. The app will:

  1. Confirm the connection belongs to you.
  2. Use your connected wallet (NWC) to request a Lightning invoice.
  3. Ask the ZSP to pay that invoice from its custodial ledger.

Your balance clears in seconds. The connection's pending balance resets to zero once settlement completes.

4. Connect a wallet first (if needed)​

You need a Nostr Wallet Connect (NWC) string to receive funds. If you haven't set one up:

  1. Open your Flokicoin wallet (LokiHub).
  2. Go to NWC or Nostr Wallet Connect settings and generate a new connection pairing secret.
  3. Paste the NWC string into your Zapf wallet settings.

The NWC connection must have the ability to receive invoices (generate invoices on your behalf).

The Underlying Protocol​

The claim process is a stateless, cryptographic sweep. When you click Claim, the Zapf web client:

  1. Encrypts your NWC connection string using NIP-44 encryption ↗, addressed exclusively to the ZSP's public key.
  2. Submits the encrypted payload alongside your identity proof to the ZSP.

The ZSP then:

  1. Validates your identity proof against the provider's API.
  2. Decrypts the payload using its private server key to read your NWC string.
  3. Queries its internal ledger for all custodial Zap Receipts attributed to the hash of your identifier (via the resolver tag).
  4. Uses your NWC string to request a Lightning invoice from your wallet.
  5. Pays that invoice instantly from its Master Node.

Your dashboard updates to reflect a $0 pending balance, and the funds appear in your self-custodied wallet.