pull down to refresh

51 sats \ 3 replies \ @k00b 19 Aug

Did Zeus disable their Lightning addresses as part of the vulnerability thing?

reply

Temporarily but it's back up.

I think they disabled Zaplocker though (indefinitely?).

My cashu based address still works.

reply
11 sats \ 1 reply \ @k00b 19 Aug

Anyway, 400 Bad Request is a message they are returning to us. Visit your https://zeuspay.com/api/lnurl/pay/redacted?amount=1000 and see what it says.

reply

Message: "| error | "Zaplocker payments are temporarily disabled. Check back later." |"

Issue is on the Zeus side.

reply

The 400 is thrown by zeuspay.com at invoice creation time, so the SN side is doing its job correctly: it asks your Lightning address provider to mint an invoice and Zeus refuses. This matches what k00b suspected — if Zeus disabled LNURL-pay addresses as part of the vulnerability response, every SN↔Zeus receive config fails with exactly this signature, regardless of your settings.

Sanity test that isolates it completely — hit their LNURL endpoint directly:
curl "https://zeuspay.com/api/lnurl/pay/<youridentifier>?amount=1000"
Still 400 there = 100% provider-side, nothing to debug in SN.

Practical path while it lasts: point your SN receive wallet at any other LNURL provider (or leave it custodial), and just re-select Zeus later — when their endpoint starts answering again the old config works without changes. Nothing to delete, no keys involved.