Nostr — how to connect

Before you start

• A Nostr identity (private key) already generated by a Nostr client or key tool (e.g. Damus, Amethyst, nos2x) — an `nsec1…` key (NIP-19 bech32) or raw 64-char hex private key. There is no OAuth/app-registration step; the key itself IS the account, so it must exist before connecting here.
• Treat the nsec as a dedicated key for this integration if you don't want this tool's publishes tied to your main personal Nostr identity — there's no 'switch account' flow, only 'paste a different key.'
• At least one reachable `wss://` relay URL. The default set (relay.damus.io, nos.lol, relay.nostr.band, relay.primal.net) works out of the box, but if you want the note to reach your existing followers, it must include the same relays your regular Nostr client publishes to/reads from.
• Text-only content ready to post — this adapter only signs and sends Kind-1 text notes; it does not upload or attach media, so strip images/video before publishing.

Step by step

1. 1
   Generate a Nostr keypair

   Use a signer extension (e.g. Alby or nos2x) or a dedicated key-generation tool to create a new keypair; this is your Nostr identity, derived per NIP-06.

   Open
2. 2
   Export the private key in nsec format

   Have the signer/tool export the private key as its bech32-encoded 'nsec1…' string (NIP-19) — this is the exact value the app's 'Private key (nsec…)' field expects.

   Open
3. 3
   Store the nsec securely before pasting it in

   Treat the nsec like a password — anyone with it can post as you and there is no password-reset mechanism on a decentralized protocol, so keep an offline backup.

4. 4
   Pick the relays to publish to

   Choose one or more public relay WebSocket URLs (wss://…) such as relay.damus.io, nos.lol, relay.nostr.band, or relay.primal.net, per the relay model in NIP-01.

   Open
5. 5
   Paste both values into the app

   In the app's Nostr connect form, paste the nsec into 'Private key (nsec…)' and the relay URLs (comma- or newline-separated) into 'Relays (wss://, comma or newline separated)', leaving the field blank to fall back to the app's default relay set.

Paste when you connect

• Private key (nsec…)secret
• Relays (wss://, comma or newline separated)

Troubleshooting

Connect fails immediately with "nsec private key is required" or "expected an nsec key, got …"

Paste the full nsec1… string exactly (or a raw 64-character hex private key) — not an npub (public key), not a truncated/partial copy, and no extra whitespace. The field only accepts NIP-19 nsec or 64-char hex.

Publish fails with "No relay accepted the note" and a reason like `blocked: please register your pubkey…` or `restricted`

That relay requires pre-registration/allowlisting (invite-only or paid relay). Remove it from the account's relay list and rely on open public relays (the defaults are open) or register the pubkey with that relay first.

Publish fails with `rate-limited: slow down there chief`

Too many notes sent to that relay in a short window. Wait a bit before retrying and avoid rapid-fire scheduled posts to the same relay; adding more relays reduces the chance one rate-limited relay blocks the whole publish.

Publish fails with `pow: difficulty N is less than M`

That relay requires Proof-of-Work (NIP-13) mining on every event, which this adapter does not compute. Drop that relay from the account's relay list — the built-in defaults don't require PoW.

Note reports as published here but never shows up in your usual Nostr client/feed

The relay list this account publishes to differs from the relays your regular client reads from. Edit the account's relay list to match (or add) the relays your Nostr client actually subscribes to.