Skip to main content
Use a redemption at size when a depositor wants more USDC than an instant redemption can pay now. The depositor signs once, and Multiliquid sources the USDC and settles the redemption on Ethereum mainnet.

Before you start

  • The depositor’s wallet, holding the $TSY to redeem and enough Treasury credits.
  • An EIP-712 signer that supports eth_signTypedData_v4.

1. Prepare

Name the depositor and one amount, in whole tokens with at most 6 decimal places: amountOut for the exact USDC to receive, or amountIn for the exact $TSY to redeem. 1,000 USDC is 1000. Prepare fills in the operator, the asset IDs, the depositor’s current nonce, and a signed bound from slippageBps, which defaults to 50 (0.5%).
Preparation answers 200 even when a check fails. The example depositor, 0x1111…1111, holds enough $TSY and Treasury credits but has not approved the Treasury delegate yet, so only checks.allowance fails, and approval covers it. Prepare and sign shows the full response, which has what you need for the next steps: A failing check does not fail the preparation. Fix it before you submit:

2. Approve

When approval is not null, land it and wait until it is confirmed: the redemption’s signature does not grant the allowance. It is an ordinary on-chain $TSY approval to the Treasury delegate, complete with the depositor’s nonce, gas, and fees: the wallet signs its serialized as returned and sets none of them itself. Sign within a few blocks, or prepare again for current fees. Either:
  • the wallet signs its transaction without broadcasting it, and you submit it alone to POST /v1/submissions and wait until it is confirmed; or
  • the wallet sends it itself, as a wallet that can only broadcast, such as a browser wallet or a custody platform, does.
An instant $TSY swap through the Treasury capital provider approves the same spender, the Treasury delegate. An approve replaces the allowance rather than adding to it, so a swap’s approval that lands after this one, before the redemption settles, can leave the redemption short: intake rejects it, or it fails, with INSUFFICIENT_ALLOWANCE. Don’t run an instant redemption and a redemption at size for one depositor at the same time.

3. Sign and submit

The depositor signs typedData as it is.
ethers rejects EIP712Domain in types. With ethers, delete types.EIP712Domain before signing; the signature is the same.
Send the redemption unchanged, with the signature, before expiresAt. Its amounts are the signed ones, in base units: assetOutAmt 1000000000 is the 1,000 USDC you asked for, and assetInAmt the most $TSY the depositor signs to spend.
It answers 201 with the new redemption and its redemptionId. A 201 means the redemption could settle now, not that it will: the depositor can still move $TSY or revoke the approval, and Multiliquid checks again before settling. Posting the same signed body again is safe. It returns the same redemption with replayed: true.

4. Track until settled

Read GET /v1/redemptions/{redemptionId} until state is final: A failed redemption whose failure.resubmittable is true can be restarted: fix the cause, such as approving more $TSY, then post the same signed body again. It needs no new signature. When resubmittable is false, the depositor signs a new redemption, or, for SETTLEMENT_UNVERIFIED, you contact support with the redemptionId. Lifecycle lists every failure code.

When submission is rejected

A rejected redemption is not stored. After fixing the cause, post the same body again before expiresAt, unless the fix below says to prepare again.
Errors lists every code.