Cancel

Cancel stops an open XvP exchange before it executes and returns locked assets to senders. The settlement state determines whether DALP cancels immediately, records an HTLC cancel vote, allows cancel-vote withdrawal, or requires expired withdrawal instead.

Cancellation model

Cancel is final. After the settlement contract cancels the exchange, it cannot execute. The contract releases the escrowed local assets back to the senders that locked them.

The cancel endpoint always targets the settlement contract and calls proposeCancel. The contract decides whether that call cancels immediately or records a vote from the caller.

How the endpoint behaves

You call the cancel endpoint with the settlement contract address and wallet verification. The legacy PUT /xvp/cancel endpoint returns the transaction hash for the submitted on-chain call.

PUT /xvp/cancel
Content-Type: application/json

{
  "settlementAddress": "0x71C7656EC7ab88b098defB751B7401B5f6d8976F",
  "walletVerification": {
    "secretVerificationCode": "YOUR_PINCODE"
  }
}

{
  "transactionHash": "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef"
}

The POST /api/v2/addons/xvp-cancellation-requests route can complete synchronously or return an asynchronous acceptance. Send Prefer: respond-async when you want DALP to accept the request and return a polling URL instead of waiting for the transaction result.

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

{
  "settlementAddress": "0x71C7656EC7ab88b098defB751B7401B5f6d8976F",
  "walletVerification": {
    "secretVerificationCode": "YOUR_PINCODE"
  }
}

{
  "transactionId": "01934567-89ab-7def-8123-456789abcdef",
  "status": "QUEUED",
  "statusUrl": "/api/v2/transaction-requests/01934567-89ab-7def-8123-456789abcdef"
}

Poll the status URL until the queued transaction reaches a terminal state. The completed transaction status contains the final transaction hash.

For local settlements and unarmed HTLC settlements, the transaction cancels the exchange immediately. No second participant approval is part of that path.

For armed HTLC settlements, the same call records the caller's cancel vote. The exchange stays open until all required local participants have voted. The final vote completes the cancellation and returns the locked assets.

Rules and limits

Check these conditions before you submit a cancel request:

• The caller must be a local participant in the settlement.
• The settlement must still be open. It cannot be executed, already cancelled, or past the cutoff.
• A revealed HTLC secret closes the cancel path. Continue execution instead.
• A participant that has voted to cancel an armed HTLC settlement can use the withdraw-cancel route only while the settlement is still open and the secret remains hidden.
• Expired settlements use expired withdrawal, not cancel, to release locked assets.

Choose your next step

Use this overview to decide which operational page fits the current settlement state:

• To stop a local or same-chain settlement before execution, read Cancel a local settlement.
• To coordinate cancel votes for an armed HTLC settlement, read Cancel an HTLC settlement.
• To understand why a revealed secret changes the cancel path, read HTLC explained.
• To recover funds after the cutoff, read Withdraw expired.