WhiSPa Bitcoin-only · self-custodial · Silent Payments
Try it on Signet → Get the app →

How WhiSPa works

Why registering asks for an email, how to give one without giving your name, and the open components doing the work underneath — none of which ever see the key that spends your bitcoin.

Registration
Why WhiSPa asks for an email

WhiSPa ships as an LNbits extension, so the wallet has a server-side account behind it. That account needs one contact address, and it is the only personal detail you are ever asked for.

Proving the address works sign-up
No account is created until you click the link we send. On a server anyone can reach, that is what stops the instance filling with automated sign-ups.
Getting back in password reset
Forget your password and the reset link goes to that address. There is no other route back into the account.
Confirming a new device login
A login from a device the server has not seen before has to be confirmed by email first, so a stolen password on its own isn't enough to get in.
Nothing else no marketing
No newsletter, no analytics, no sharing with anyone. Those three messages are every email WhiSPa will ever send you.

The email has nothing to do with your bitcoin. Your spend key is derived and kept on your device and never reaches the server, so no one holding your email — us, your mail provider, or somebody who takes the account over — can move your coins. The other half of that matters just as much: the email cannot recover your bitcoin either. A reset link gets you back into the account; only your seed backup gets you back to your funds.

Recommended
Register with an alias, not your real inbox

We don't care which address you use — so use one that isn't tied to your name. An alias forwards to your real inbox, so reset and device-confirmation mail still reaches you, while WhiSPa only ever stores the alias.

Step 01 · Pick a provider

An aliasing or private-mail service

Free: SimpleLogin, addy.io, Firefox Relay or DuckDuckGo Email Protection for masked addresses, or a fresh account at Proton Mail or Tuta. Paid, if you already have one: Apple Hide My Email, Fastmail Masked Email, 1Password, or Bitwarden Premium.

Step 02 · Generate

One alias used only here

Not an address you have given out anywhere else. A single-purpose alias means this account can't be correlated with your others by email address.

Step 03 · Register

Sign up with the alias

Put it in the email field when you register. Open the mail that arrives and either click the link or type the six-digit code it carries — either one creates the account.

Step 04 · Record it

Store it beside your password

Keep the alias in your password manager next to your WhiSPa username and password. Lose track of which alias you used — or let the alias itself lapse — and you lose the only route back into the account. Your seed still recovers the bitcoin; it does not recover the account.

Architecture
Layers doing one job

WhiSPa is the interface. Open components do the work underneath, each with a single responsibility.

Layer 01 · Interface

WhiSPa — the wallet you see

Derives keys and signs on your device. The server only broadcasts what you already signed.

Layer 02 · Backend

LNbits — accounts & orchestration

WhiSPa ships as an LNbits extension, inheriting multi-user accounts, auth, and device confirmation.

Layer 03 · Indexing

BlindBit & Fulcrum — indexing the chain

BlindBit precomputes tweak and UTXO data so scanning is quick; Fulcrum serves lookups. Neither sees your spend key.

Built on
Open foundations

Every piece is open source and self-hostable — run your own and nothing sits between you and the chain.

LNbits accounts + API
Multi-user, self-hosted Bitcoin backend. WhiSPa is an extension on top.
BlindBit SP oracle
Silent Payments indexer — precomputed tweak and UTXO data for fast scanning.
Fulcrum electrum server
Address and transaction lookups without a third-party explorer.

The security model — where keys live and what a server compromise can and can't reach — is on Privacy & security.