getAddressType: surface lq downtime as actionable error

When lq.getAddressInfo throws on a connection error (ECONNREFUSED /
ETIMEDOUT / "Unable to connect"), the generic catch was reporting
"unrecognized address" — misleading for both users (who think their
address is wrong) and operators (who can't tell user error from
infrastructure problems in the logs). Map connection errors to a
specific "liquid temporarily unavailable" message instead.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

1 files changed, 11 insertions, 1 deletions

diff --git a/lib/payments.ts b/lib/payments.ts
index 5984a813..cf6a344f 100644
--- a/lib/payments.ts
+++ b/lib/payments.ts
@@ -1111,7 +1111,17 @@ const getAddressType = async (a) => {
     try {
       await lq.getAddressInfo(a);
       return PaymentType.liquid;
-    } catch (e) {
+    } catch (e: any) {
+      // Distinguish "lq is down" from "address isn't liquid" so users get a
+      // useful message instead of "unrecognized address" when cs/lq is the
+      // actual problem.
+      if (
+        e?.message?.includes("Unable to connect") ||
+        e?.code === "ECONNREFUSED" ||
+        e?.code === "ETIMEDOUT"
+      ) {
+        fail("liquid temporarily unavailable");
+      }
       fail("unrecognized address");
     }
   }