A remote NostrConnect signer that keeps your keys on Android

What Is a Remote Signer for Nostr?

Nostr is a decentralized social protocol in which your identity is a cryptographic key pair rather than an account on a company's server. The public key is the address other people see, and the private key is what proves that a post or message really came from you. Whoever holds the private key can act as you, which is why its handling matters so much.

A remote signer sits between the key and the application. The website builds an event, such as a short note or a reaction, and asks the signer to produce a signature. The signer holds the key, checks the request, and returns the signed result. The website never needs to see the key itself.

That separation is the core idea behind BlazeJump.NostrConnect. It treats an Android device as the place where your identity lives, and it lets your browser sessions borrow that identity for signing. The model is familiar to anyone who has used a phone authenticator for logins, even though the job here is signing Nostr events rather than generating one-time codes.

Who Is BlazeJump.NostrConnect For?

The most natural user is someone who already uses Nostr and spends time in a browser on a Windows PC. Reading and posting from a desktop is comfortable, but typing a private key into each new site is risky. A phone-based signer lets you keep one identity while working on a larger screen.

Consider a common scenario. You open a Nostr web client on your Windows laptop to publish a long-form note. Instead of logging in with a key, you scan the pairing code with your Android phone. When you press publish, a request appears on the phone, and you approve it there. Your key never has to appear in the browser tab.

Developers form a second group. Because the project is MIT-licensed and written in C#/.NET, a .NET developer can study how the pairing and encryption layers fit together, adapt the approach, or contribute fixes. It is also useful as a reference for understanding how remote signing differs from storing a key locally.

The tool is less suited to people who want a single app that does everything. It covers identity and signing, so you will still need a Nostr client for reading and posting.

Why Keep Nostr Keys Out of the Browser?

Browsers run a lot of code, from page scripts to extensions, and any of them can be a weak point. If a private key is stored in a browser profile or pasted into a web form, anything that reads that storage or captures that input can take it. Once a key leaks, it cannot be reset the way a password can, because the key itself is the identity.

A signer reduces that exposure. The key stays on a separate device, and the browser only receives signatures. Even if a site behaves badly, it cannot copy a key it never received. Approving each request on the phone adds a human check, because you see what is being signed before it goes out.

This does not make you immune to every risk. A phone can be lost or unlocked by someone else, and a careless approval can still publish something you did not intend. Treat the phone as the most important part of your setup, use a lock screen, and read each request before you tap approve.

The design also suits people who switch between several Nostr apps. Your identity stays in one place, and each app receives signatures only when it asks for them.

Supported coins

The program is built around Nostr, the decentralized social protocol, and that is the only network named in its documentation. BlazeJump.NostrConnect is an identity signer rather than a coin wallet, so it signs Nostr events and does not hold cryptocurrency balances or send coins.