Identity · How to

Link Nostr to your ACCESS identity

This is not a one-click social login like “Sign in with X.” You prove control of a Nostr public key with a browser key app. ACCESS stores only that public key and gives you a verifiable name: you@getaccess.world (NIP-05).

What you need

• An ACCESS account with a claimed handle (e.g. you.access)
• A NIP-07 browser extension that holds your Nostr key — common options: nos2x or Alby (desktop browser)
• About five minutes the first time

Step 1 — Install and load your key app

1. Install a NIP-07 extension (nos2x or Alby) in Chrome / Brave / Edge.
2. Open the extension options.
3. Put your personal Nostr nsec in the extension — or click generate for a new key. Then save.
4. If the extension says “no private key found,” the key was not saved in the extension. ACCESS cannot fix that from the server.

Important: a key in a server .env file (agent keys) is not the same as the key in your browser extension. The Identity link only talks to the extension.

Step 2 — Sign in to ACCESS

1. Go to getaccess.world/sign-in
2. Open Identity → Nostr

Step 3 — Connect and approve prompts

1. On the Identity page, click Connect Nostr key app.
2. When the extension asks, allow getPublicKey for getaccess.world.
3. When it asks again, allow signEvent (this is the NIP-98 proof that you control the key — not a post to the network).

Step 4 — Confirm success

You should see all of these:

• NIP-05 — yourhandle@getaccess.world
• npub — your public key (starts with npub1…)
• An Unlink Nostr button (proof the write path worked)

Anyone can later resolve your NIP-05 via getaccess.world/.well-known/nostr.json?name=yourhandle — that returns the public key only.

What ACCESS stores

• Your public hex / npub
• Your NIP-05 name tied to your ACCESS handle
• Never your nsec, seed, or recovery phrase

Common problems

• “no private key found” — save a key inside the extension options, reload the Identity page, try again.
• Connect stays disabled — install a NIP-07 extension; mobile in-app browsers often have no window.nostr.
• “Claim an ACCESS username first” — finish onboarding / claim your handle, then link Nostr.
• Prompt blocked — check the extension’s permissions table for getaccess.world; revoke and reconnect if needed.