HTLC settlements

Cancelling an HTLC settlement stops the exchange and refunds escrowed local assets to the senders that locked them. Before the settlement is armed, one local participant can cancel it. After every local sender has approved, each local participant must cast a cancel vote.

Use this page when you need to stop an HTLC settlement before execution. If the cutoff date has already passed, use Withdraw expired instead.

Before you cancel

Check the settlement state before you choose what to do:

The contract treats local participants as the unique local sender and recipient addresses in the settlement flows. A sender who is also a recipient counts once. Users outside the local flows cannot cancel the settlement or vote to cancel it.

Cancel before the settlement is armed

When an HTLC settlement does not yet have every local sender approval, any local participant can stop it without collecting votes from the other participants.

Propose cancellation after the settlement is armed

An armed HTLC settlement has every required local sender approval. At that point, DALP requires unanimous votes from the local participants before it refunds escrow. This prevents one participant from cancelling after the other side has already coordinated external chain commitments.

Withdraw your cancel vote

A local participant can withdraw their own cancel vote while the armed settlement is still open and before the final required vote is cast. Use this only when the settlement should remain armed.

1. Open the armed settlement.
2. Click Withdraw Cancel Proposal.
3. Submit the wallet verification.

The vote is removed. The settlement remains armed and cannot cancel until the participant proposes cancellation again.

You cannot withdraw a cancel vote after the settlement has already cancelled, executed, expired, or had its HTLC secret revealed.

What cancellation changes

• DALP clears active cancel votes when the settlement cancels.
• DALP returns escrowed local assets to the sender addresses that locked them.
• DALP marks the settlement as Cancelled. The settlement cannot execute after that.
• DALP blocks cancel and withdraw-cancel requests after the HTLC secret is revealed.

API behavior

The public cancel endpoint queues a transaction against the settlement contract:

POST /api/v2/addons/xvp-cancellation-requests
Content-Type: application/json

{
  "settlementAddress": "0x...",
  "walletVerification": {
    "secretVerificationCode": "123456",
    "verificationType": "PINCODE"
  }
}

When the platform processes the transaction synchronously, the response wraps the contract output in the standard blockchain mutation envelope:

{
  "data": {
    "transactionHash": "0x..."
  },
  "meta": {
    "txHashes": ["0x..."]
  },
  "links": {
    "self": "/v2/addons/xvp-cancellation-requests"
  }
}

If you send Prefer: respond-async and the transaction is accepted for asynchronous processing, the response gives you a transaction status URL instead:

{
  "transactionId": "018f2f6e-7c6a-7c64-9a5a-4f5e6a3c2b10",
  "status": "QUEUED",
  "statusUrl": "/api/v2/transaction-requests/018f2f6e-7c6a-7c64-9a5a-4f5e6a3c2b10"
}

For pending settlements, the contract cancels immediately. For armed HTLC settlements, the same cancel request records the caller's cancel vote. A second cancel request from the same participant while that vote is still active is not a safe retry. Check the settlement state before retrying a submitted request.

Use the withdraw-cancel action only when the participant intentionally wants to remove an active cancel vote before the final required vote is cast.

Production checks

Before cancelling an HTLC settlement, confirm these points:

Troubleshooting

Next steps