feat: seed-driven pairing over the LNbits nostr-transport (#70) #73
1 changed files with 3 additions and 2 deletions
fix(machine): point DEV_DEFAULT_RELAY at the real dev relay
The last-ditch dev fallback (used only when neither env nor the pairing seed supplies a relay) was ws://localhost:7777 — a standalone strfry we no longer run. Align it to the dev stack's LNbits bundled nostrrelay (ws://localhost:5001/nostrrelay/test) so the fallback points at a relay that actually exists. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
commit
06f73b2d76
|
|
@ -100,8 +100,9 @@ async function loadLightningConfig(): Promise<LightningConfig> {
|
|||
// Config is loaded async now - will be set in initializeLightningServices
|
||||
let CONFIG: LightningConfig
|
||||
|
||||
/** Dev-only relay used when neither env nor the pairing supplies one. */
|
||||
const DEV_DEFAULT_RELAY = 'ws://localhost:7777'
|
||||
/** Dev-only relay used when neither env nor the pairing supplies one. Matches
|
||||
* the dev stack — LNbits's bundled nostrrelay (no separate strfry container). */
|
||||
const DEV_DEFAULT_RELAY = 'ws://localhost:5001/nostrrelay/test'
|
||||
|
||||
/** Safety timeout in ms (15 minutes) — absolute maximum LNURL session lifetime.
|
||||
* Sessions are normally cleaned up by the state machine on idle transition.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue