The service worker learns what must stay live: same-origin API paths — esplora, sp, lnurl, well-known — go straight to network, never the cache that froze a refresh on a stale unconfirmed

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

1 files changed, 7 insertions, 1 deletions

diff --git a/build.js b/build.js
index 8abf5fb..0c8cba2 100644
--- a/build.js
+++ b/build.js
@@ -74,7 +74,13 @@ self.addEventListener('activate', (e) => {
 self.addEventListener('fetch', (e) => {
   const req = e.request;
   if (req.method !== 'GET') return;
-  if (new URL(req.url).origin !== self.location.origin) return; // explorer/ws → network
+  const u = new URL(req.url);
+  if (u.origin !== self.location.origin) return; // explorer/ws → network
+  // Live API paths served from OUR origin (esplora, sp indexer, lnurl,
+  // well-known) must never be cached: a chain answer frozen at first sight
+  // wedges every flow that polls it (a refresh once waited forever on a
+  // cached "unconfirmed"). Straight to network, always.
+  if (/^\\/(esplora|sp|lnurlp|electrum)\\//.test(u.pathname) || u.pathname.startsWith('/.well-known/')) return;
 
   if (req.mode === 'navigate') {
     e.respondWith(