yusuke

nostr

swift-nostr v0.6.0: NIP-46 remote signing — no nsec in your app

> 1 sat \ 0 replies \ @ek 2h
> Feedback welcome ⚡
> Did you use AI to write this?

Just an easy way to spread it

A few weeks ago I posted here about swift-nostr v0.5.0 closing the Lightning zap loop — sign the zap request, pay the invoice over NWC, verify the receipt, all in Swift.

The obvious next question for anyone actually shipping an app: *does my app have to hold the user's private key to do any of that?* For a crowd whose whole ethos is "not your keys, not your coins," pasting an nsec into some app's storage is a non-starter.

v0.6.0's answer is no.

**NIP-46 remote signing (new `NostrConnect` library).** The user's key stays in their signer/bunker. Your app asks the remote signer to sign events and to encrypt/decrypt — the nsec never enters your process. Both flows are covered: signer-initiated `bunker://` and client-initiated `nostrconnect://`, plus `auth_url` challenges and the full typed command set (sign, get_public_key, ping, nip44/nip04 encrypt/decrypt, switch_relays, logout).

And because local and remote signers now share one `NostrSigning` protocol, you write your app against a single API — `client.setSigner(...)` takes either an in-process `EventSigner` or a remote `RemoteSigner`. Develop with a local key, ship against a bunker, no code change.

**NIP-44 encryption is now spec-compliant and interoperable.** Honest bug: earlier releases used the AEAD ChaCha20 keystream (block counter 1) and a floating-point padding calc, so our encrypted payloads didn't match other Nostr clients — including the NIP-44 that modern NWC rides on. Now it's bare ChaCha20 at counter 0 with the spec's integer padding, validated against the official NIP-44 test vectors. (Payloads from older releases won't decrypt — but they never interoperated with anything else either.) If you touch encrypted DMs or NWC, this is the release you want.

**The other nine NIPs this cycle:**

* NIP-49 — password-encrypt a private key to `ncryptsec` (scrypt + XChaCha20-Poly1305). Key-at-rest to go with the key-never-in-app story above.
* NIP-13 — proof of work, with a cooperative, cancellable async miner
* NIP-23 — long-form articles + drafts (kind 30023/30024), `naddr` addressing
* NIP-51 — lists & sets (mute, pin, bookmarks, follow/relay/curation sets…) with NIP-44-encrypted private items
* NIP-50 — relay-side search
* NIP-45 — event counts (COUNT)
* NIP-27 — `nostr:` mention parsing → p/q/a tags
* NIP-21 — `nostr:` URIs
* NIP-56 — reporting

Lightning is still first-class — NIP-57 zaps and NIP-47 NWC (full command set + one-call `payZap`) are unchanged, and now ride on the fixed NIP-44.

Where it stands: **31 NIPs**, Swift 6 (actor-isolated, `Sendable`, async/await), all Apple OSes (iOS/macOS/tvOS/watchOS/visionOS), MIT. Four libraries so you pull only what you need — `NostrCore`, `NostrClient`, `NostrWalletConnect`, `NostrConnect`.

Still early and built in the open. If you're working on Lightning-native social — or DVM/agent ideas that need to pay, sign, and stay non-custodial over Nostr — I'd love issues, PRs, or teardowns.

[https://github.com/yysskk/swift-nostr](https://github.com/yysskk/swift-nostr)

Feedback welcome ⚡

I've been building [**swift-nostr**](https://github.com/yysskk/swift-nostr), an open-source Swift library for the Nostr protocol, and the part I think this crowd will care about most is that the Lightning integration is first-class — not a TODO.

The zap loop is actually closed:

* **NIP-57** — sign the zap request (kind 9734), resolve the recipient's LNURL-pay endpoint, fetch the bolt11, decode it, and verify the kind-9735 receipt.
* **NIP-47 (Nostr Wallet Connect)** — pay that invoice through a remote wallet over Nostr. Full command set (`get_balance`, `make_invoice`, `lookup_invoice`, `list_transactions`, keysend, multi-payments, notifications) plus a one-call `payZap`.

So on Apple platforms you can now go from "user taps zap" to "sat paid + receipt verified" entirely in Swift.

Beyond payments:

* **NIP-17 private DMs** — gift wrap (NIP-59) + NIP-44, with kind-10050 DM relay routing
* **NIP-65 outbox model** with gossip routing
* 20+ NIPs total, modern Swift 6 (actor-isolated, `Sendable`, async/await), all Apple OSes, MIT

It's early (v0.5) and I'm building it in the open. If you're thinking about Lightning-native social apps — or DVM/agent ideas that need to pay and get paid over Nostr — I'd love feedback, issues, or PRs.

[https://github.com/yysskk/swift-nostr](https://github.com/yysskk/swift-nostr)

Feedback and teardowns welcome ⚡

swift-nostr v0.5.0 Release: a Swift Nostr library with NIP-57 zaps + NIP-47 NWC

Engineer in BC, Canada

https://github.com/yysskk/swift-nostr