Files
bitlogin/packages/core/src/crypto/hkdf.ts
T
Claude 5ee63ae6b0 Implement BitLogin as a modular protocol library, embeddable widget, and demo site
Builds out the v0.3 spec as an npm workspace monorepo any static site can
consume for login and Nostr signing:

- packages/core: framework-free protocol implementation — Argon2id/HKDF/
  ScalarExpand/AES-256-GCM/JCS crypto primitives, NIP-01 event handling and a
  quorum-aware relay pool, credential/recovery capsule construction and
  validation, and the full account lifecycle (registration, any-device
  login with rollback/relay-disagreement detection, phrase recovery with
  recovery-capsule refresh, password rotation with mandatory tombstone +
  NIP-09 deletion, replica repair, recovery export, NIP-19 encoding, a
  NIP-44 v2 implementation, and a NIP-07-shaped signer). 49 tests cover the
  spec's Phase 0 byte-level vectors plus full create/login/recover/rotate
  end-to-end scenarios against an in-memory mock relay.

- packages/widget: a <bitlogin-auth> custom element with a dedicated crypto
  Web Worker (private keys never touch the main thread) and a window.nostr
  NIP-07-compatible provider, so existing Nostr web apps work against it
  with zero code changes. Built with Vite into two relocatable static files.

- packages/demo: a plain static site (no build step of its own) consuming
  the widget — a branding/landing page, an integration guide, and an
  account-manager page covering create/login/recover, password rotation,
  and identity export.

All flows were verified twice: protocol-level tests against a mock relay,
and the actual built widget driven end-to-end in real Chromium (registration,
phrase confirmation, event signing, clean-device login, window.nostr, and
phrase recovery all reproduce the identical everyday pubkey).

Co-Authored-By: Claude Sonnet 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01GWJbXXhvTx9wo59jSz57J6
2026-07-21 03:44:10 +00:00

21 lines
923 B
TypeScript

/** HKDF-SHA256 domain separation (§11.1, §11.4, §11.5). RFC 5869 via @noble/hashes. */
import { sha256 } from "@noble/hashes/sha2";
import { extract, expand } from "@noble/hashes/hkdf";
import { utf8ToBytes } from "./encoding.js";
/** HKDF-Extract(salt, IKM) -> PRK. `salt` is a domain-separation label already hashed by the caller. */
export function hkdfExtract(salt: Uint8Array, ikm: Uint8Array): Uint8Array {
return extract(sha256, ikm, salt);
}
/** HKDF-Expand(PRK, info, length) -> output keying material. */
export function hkdfExpand(prk: Uint8Array, info: string | Uint8Array, length: number): Uint8Array {
const infoBytes = typeof info === "string" ? utf8ToBytes(info) : info;
return expand(sha256, prk, infoBytes, length);
}
/** SHA-256 of a UTF-8 label, used as an HKDF-Extract salt (§11.4, §11.5). */
export function labelSalt(label: string): Uint8Array {
return sha256(utf8ToBytes(label));
}