nostr-bunker-integration

NIP-46 remote signing connects a client and a bunker signer over Nostr relays, keeping private keys secure on the signer while clients request signatures through NIP-44 encrypted 24133 events.

To connect a client to a bunker signer, initialize the connection flow using a bunker:// or nostrconnect:// URI, which handles auth challenges, relay switching, and signer discovery automatically.

Yes, NIP-46 remote signing workflows support multiple SDKs across JS/TS, Rust, and Dart, allowing you to implement both client and signer behaviors with proper get_public_key semantics.

The best way to discover a remote Nostr signer is using NIP-89 discovery and NIP-05 metadata, which facilitate finding available bunkers and retrieving signer information before establishing a connection.

Permission enforcement is required for remote signing to ensure the bunker signer validates and authorizes specific sign_event requests from the client, preventing unauthorized actions while the private key remains protected.

Yes, NIP-46 bunker signing supports retrieving the user's actual public key through the get_public_key request after establishing the connection, allowing the client to confirm the signer identity securely.