Connect Nostr
Nostr has no accounts to authorize, so NioConnect needs a private key that can sign your posts; use a dedicated key made for publishing.
Last updated- In the Nostr client or signer you already use, find your secret key. It starts with
nsec1, or it is 64 hex characters. - Better still, generate a new identity in any client and use that key for publishing.
- In NioConnect, open Channels, choose Add a channel, then Nostr.
- Paste the key into Private key (nsec or hex) and connect.
Read this before you paste a key
A Nostr private key is not a scoped credential. It is not an app password and not a token you can narrow. Whoever holds it is that identity: they can post, delete and change the profile, and there is no server to revoke it at. The only remedy for a leaked key is to abandon the identity.
NioConnect encrypts the key at rest with a key specific to your workspace, never returns it through the API, never writes it to a log and never shows it to you again. That is the strongest handling we can offer, and it does not change the paragraph above.
Nostr identities are free and take seconds to make. A publishing identity built for this purpose has nothing to lose if you ever walk away from it. Do not hand over your main identity unless you accept that risk.
Where to find the key
In Damus on iOS, open Settings, then Keys. In Amethyst on Android, use the profile menu and Backup keys. Most web clients put it under Settings, then Keys or Export. If your value starts with npub1, that is the public half and it cannot sign anything.
Connecting does not touch the network. NioConnect derives the public key from what you pasted, which proves the key is real and gives the channel its identity.
If it did not work
If you see "That is a public key", you pasted the npub; export the secret key instead, because the two sit side by side in most clients. A key refused as malformed is usually a truncated paste, so copy the whole value again.
If Nostr is not offered at all, your deployment has no relays configured. That is an operator setting rather than something in your account. To cut access later, replace the identity: there is no revoke button anywhere in the protocol.