mirror of
https://github.com/PR0M3TH3AN/bitlogin.git
synced 2026-10-27 08:31:21 +00:00
thePR0M3TH3ANandClaude Sonnet 5
863f035990
Vendoring sites had no documented way to learn a fix landed here or how to pull it in. Adds a changelog (integrator-relevant entries only, each noting whether it applies to a site's config) and a README section explaining why vendoring is manual by design -- a shared auto-updating script would make a bad deploy here an instant multi-site incident for a widget that handles private key crypto. Co-Authored-By: Claude Sonnet 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01DY9UMTuF43Ekc2U4E1eDwX
1.1 KiB
1.1 KiB
Changelog
Tracks changes to @bitlogin/core and @bitlogin/widget that matter to a
site with its own vendored copy (see "Updating your integration" in
README.md). Not every commit needs an entry — only ones where a site
sitting on an older vendored copy is missing a fix or behavior change it
would plausibly want. Newest first.
2026-07-21
- Fix: registration/login could fail quorum if a single built-in relay was
down.
BUILTIN_VAULT_RELAYShad only 3 relays andBUILTIN_DISCOVERY_RELAYSonly 2, sharingrelay.nostr.bandbetween both lists.publishAndVerify()requires a fixedminAcks/minReadbacksof 2 regardless of relay count, so losing that one relay left zero margin — surfacing as "Registration did not reach the required relay acknowledgement and readback quorum." Addednostr.wineandrelay.snort.socialto the vault list, andnostr-pub.wellorder.netto discovery. (681f622) Re-vendor if: your site uses the default built-in relay list (i.e. you don't pass your ownvault-relays/discovery-relaysattributes). If you already pass your own relay list, this doesn't affect you.