Claude a76c8484f7 Add nsec import: use an existing Nostr identity as the everyday key (§SF10) ...

core:
- registerAccount gains an optional everydayPrivateKey (validated scalar,
  used instead of generating); result carries an `imported` flag
- importAccount() + decodeEverydayPrivateKey() convenience helpers accept
  nsec (bech32) or 64-char hex, wiring in the existing decodeNsec primitive
- e2e tests: imported nsec round-trips to the same npub through both
  clean-device login and phrase recovery; malformed keys rejected

widget:
- worker gains a `previewImportKey` action (validate + preview npub without
  publishing) and passes importKey through `register`
- <bitlogin-auth> gets an "Import an existing Nostr key" screen: paste
  nsec/hex, check-key preview shows the resulting npub for confirmation,
  then the normal name -> password -> phrase flow, with the pasted key
  dropped from the main thread after registration (§11.10) and a
  risky-paste warning shown up front

docs: mark §SF10 implemented; note backup codes are redundant with the
phrase and unlikely to ship; README implemented-list updated.

Verified end-to-end in real Chromium (preview npub, import, clean-device
login all reproduce the imported identity). 51/51 tests pass.

Co-Authored-By: Claude <[email protected]>
Claude-Session: https://claude.ai/code/session_01GWJbXXhvTx9wo59jSz57J6

2026-07-21 10:59:01 +00:00

..

src

Add nsec import: use an existing Nostr identity as the everyday key (§SF10)

2026-07-21 10:59:01 +00:00

package.json

Implement BitLogin as a modular protocol library, embeddable widget, and demo site

2026-07-21 03:44:10 +00:00

tsconfig.json

Implement BitLogin as a modular protocol library, embeddable widget, and demo site

2026-07-21 03:44:10 +00:00