UTXO Swap Is Offline, and by Design Its Liquidity Providers Cannot Get Out Alone

By Telmo · August 30, 2026

The site now shows a maintenance page and the team has gone quiet. On chain the funds are intact but unreachable, because the protocol requires an operator signature to withdraw. Here is the proof, and the accountability question it raises.

Update (31 August 2026): After this piece was published, a direct message to the UTXO Swap team drew a prompt reply: the server is mid-upgrade and coming back online, but the service is being shut down. This corrects the claim below that outreach went unanswered and unacknowledged: on direct contact, it was answered, and the liquidity issue was acknowledged. It does not change the underlying point. Withdrawal is still gated on the operator's server coming back up on their own timeline, which is exactly the dependency this piece and its follow-up describe. UTXO Swap, the intent-based DEX launched on Nervos CKB and RGB++ Layer in July 2024, is offline. Its site now shows a maintenance screen ("系统正在维护中 / We'll be back soon") and a "Maintenance in progress" badge; its public API returns errors on every route. For most users of a DEX that is an inconvenience. For its liquidity providers it is more serious: right now they cannot withdraw the funds they deposited, and the reason is written into the protocol's on-chain rules, not only its servers. This is worth understanding in detail, because it is a failure mode any CKB user can check for before they deposit, and one a different design avoids entirely. The timeline UTXO Swap launched its mainnet in mid-July 2024, promoted as the first DEX on RGB++ Layer and a flagship of the "BTCFi" push. On chain, it worked: from July 2024 onward its sequencer settled more than 10,000 pool operations. The last of those settlements landed on 20 August 2026. Nothing has settled since. That is the moment the exchange effectively stopped. The human side had gone quiet earlier. The project's X account has not posted in about a year, and its Telegram goes unanswered. There has been no announcement explaining the outage, no timeline, no acknowledgement that user liquidity is affected. In practice the team stopped communicating roughly a year ago while the sequencer kept running on autopilot, and when the sequencer finally stopped ten days ago,…