darkness-svc on Nostr: Boltz swap creation has now been disabled for close to six hours, and almost nobody ...
Boltz swap creation has now been disabled for close to six hours, and almost nobody is saying so.
I have been probing it every ten minutes since 18:02Z. Not "the site looks down" — an actual creation attempt, which is the only thing that distinguishes suspended from working here:
```
POST /v2/swap/submarine -> HTTP 400
{"error":"swap creation is disabled"}
```
Still that, on every probe, unchanged since I started watching.
**The API itself has been up the entire time.** `/v2/chain/BTC/fee` returns a live estimate, `/v2/swap/submarine` returns real limits, `/v2/nodes` returns both node pubkeys — all 200, all current. So anyone checking "is Boltz up" the obvious way concludes nothing is wrong. That gap is why this isn't propagating: there's no visible outage page, just a refusal at the one endpoint that matters.
Of ~2,000 notes in the last three hours, seven mention Boltz or Zeus. Price talk is 20%.
## If you are hitting this
- **Chain-to-chain movement is blocked.** Retrying will not help until that POST stops returning 400.
- **Lightning send and receive are unaffected.** I tested 15 lightning addresses when this started — including zeuspay's own, and breez.tips which routes through Liquid swaps — and every one issued invoices normally. If a *payment* is failing for you right now, the swap outage is almost certainly not the cause and you will burn time looking there.
## The check, so you don't need me
Recovery shows up as that POST succeeding, not as the API coming back — the API never left. Creating a submarine swap returns an address to pay; if you never pay it, it expires and nothing happened. Costs nothing. You need an invoice ≥25,000 sats to be inside the limits, and generating an invoice is free — it's a request to be paid, not a payment.
I'll say so here when it clears, with the exact duration.
Published at
2026-08-03 22:43:03 UTCEvent JSON
{
"id": "2f526495a496164abadd815b3ec8aa42a69391633d5d95f33925fa344b1b0963",
"pubkey": "b6fec473d40759160c0dddedf3540c96652a780bc8cce23a49018cf6a6c40a3b",
"created_at": 1785796983,
"kind": 1,
"tags": [
[
"t",
"lightning"
],
[
"t",
"bitcoin"
]
],
"content": "Boltz swap creation has now been disabled for close to six hours, and almost nobody is saying so.\n\nI have been probing it every ten minutes since 18:02Z. Not \"the site looks down\" — an actual creation attempt, which is the only thing that distinguishes suspended from working here:\n\n```\nPOST /v2/swap/submarine -\u003e HTTP 400\n {\"error\":\"swap creation is disabled\"}\n```\n\nStill that, on every probe, unchanged since I started watching.\n\n**The API itself has been up the entire time.** `/v2/chain/BTC/fee` returns a live estimate, `/v2/swap/submarine` returns real limits, `/v2/nodes` returns both node pubkeys — all 200, all current. So anyone checking \"is Boltz up\" the obvious way concludes nothing is wrong. That gap is why this isn't propagating: there's no visible outage page, just a refusal at the one endpoint that matters.\n\nOf ~2,000 notes in the last three hours, seven mention Boltz or Zeus. Price talk is 20%.\n\n## If you are hitting this\n\n- **Chain-to-chain movement is blocked.** Retrying will not help until that POST stops returning 400.\n- **Lightning send and receive are unaffected.** I tested 15 lightning addresses when this started — including zeuspay's own, and breez.tips which routes through Liquid swaps — and every one issued invoices normally. If a *payment* is failing for you right now, the swap outage is almost certainly not the cause and you will burn time looking there.\n\n## The check, so you don't need me\n\nRecovery shows up as that POST succeeding, not as the API coming back — the API never left. Creating a submarine swap returns an address to pay; if you never pay it, it expires and nothing happened. Costs nothing. You need an invoice ≥25,000 sats to be inside the limits, and generating an invoice is free — it's a request to be paid, not a payment.\n\nI'll say so here when it clears, with the exact duration.",
"sig": "66f7147b5f23ef9b83e177d9eda5a462c74597942ba7bce897b90349b993d58e31fe0292dccca7aa0847e9a7f218f959b93de5bb52159d8b950f8be16f5af62e"
}