Clave

Everyone thinks a Nostr signer is for logging into dedicated social clients like

or

.

We built Clave for the other stuff… the recipe apps, the workout trackers, the games, the music players, the experiments someone ships in a weekend.

One key unlocks a world of “other stuff”.

Drop a few of your favorites👇

#clave

https://clave.casa

Clave v0.2.0 Build 94 released on iOS Testflight. Now supporting NIP-44 v3.

In NIP-44 v2, an encrypt or decrypt request to a signer carries no information about what kind of event it's for. The request is just (pubkey, ciphertext). The signer can't tell whether an app is decrypting its own chat traffic, your Cashu wallet (kind 17375), or your gift-wrapped DMs (kind 1059). So when you grant an app "can decrypt for me," you're necessarily granting it for everything — the protocol gives the signer no handle to gate per-kind.

NIP-44 v3 puts the kind and scope into the request and binds them into the encryption itself. Now the signer knows what kind of data is being touched, and grants can be per (app, kind, scope). An app authorized to "save its deck (kind 30078, scope spectr_decks)" cannot silently decrypt your wallet or your DMs with that grant. The cryptography enforces it.

First reference-implementation pair shipped today:

(iOS signer) and Spectr (web client at https://spectr.clave.casa ).

Thanks to

for the NIP-44 v3 spec, the Go reference library at github.com/nostr-land/ncrypt-go, and the 228 test vectors that made porting safely possible. Thanks also to the

team and nostr:npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w and Nostr Build Shack for paving the way and being the first to implement. #nip46 #clave

https://testflight.apple.com/join/5Mx5AZx7

Clave v0.2.0 build 79 — what to test

What's new:

• New Connect tab in the bottom bar (between Activity and Discover) — replaces the old "Connect a Client" button on Home
• New Discover tab — placeholder for now, will eventually list NIP-46-compatible apps
• Multi-account pairing flow: when you have multiple accounts in Clave, you explicitly pick which account each app should sign for (no more implicit "use whichever is current")
• Bunker URIs now ask which account first, then show that account's URI + avatar (was: always used current account)
• New help sheet explaining Nostrconnect vs Bunker, including a note about same-device pairing reliability

To try:

1. Find the Connect tab — fourth icon from the left on the bottom (⚡ bolt). Tap it.
2. Pair with your favorite Nostr app using its sign-in / NIP-46 flow:
   • Scan the QR with Clave's camera, or
   • Tap "Paste Nostrconnect URI" and paste from clipboard
3. Multi-account folks: after pasting/scanning, you'll see an account picker. Pick one. The picker shows your avatar, display name, and a short npub.
4. Try the bunker flow — tap "Share a code from Clave" → pick an account → copy or scan the URI for that account. Paste into the other app.
5. Tap the help link at the bottom of the Connect tab and read the methods comparison. Does it make sense?
6. Same-device pairing: if you've struggled with nostrconnect URIs between apps on the same iPhone before, try Bunker for that case and see if it works better.

Report bugs via the signal group or tag #clave on Nostr. Include:

• Which step failed
• Single-account or multi-account?
• Same-device or cross-device pairing?
• A screenshot if possible

https://testflight.apple.com/join/5Mx5AZx7

https://signal.group/#CjQKIPbS1HXpkoSjreRFls_gL3lwSd7Sk6VLKvPYDnO1oF2bEhAPcsWVvLMiPXzHiqFLxmBi

Hello Nostr. The keys stayed home today. #clave