Skip to main content
The vault always runs on HyperEVM. Non-HyperEVM receive chains are handled by using a Relay deposit address as the receiver for the Signalite instant redeem or claim transaction. Queued redeem requests do not have a Relay deposit address yet; they get one later when the claim action is created.
  1. User chooses withdrawal amount.
  2. App explains whether the exit is instant or queued.
  3. If the receive chain is HyperEVM, no Relay metadata is required.
  4. If the receive chain is not HyperEVM and the action is instant redeem or claim, Signalite quotes a Relay deposit address and uses it as the tx receiver.
  5. If the action is queued redeem, Signalite returns postSettlementBridge.mode="post-claim-quote" and relay=null; persist the destination and create the claim later with the same receiveChainId.
  6. Partner UI tracks the Relay requestId from claim or instant metadata until destination USDC arrives.

​
Read supported destinations

Partner Actions accept an optional receiveChainId on withdrawal actions:
  • POST /api/v1/partner/actions/redeem-instant
  • POST /api/v1/partner/actions/redeem-async
  • POST /api/v1/partner/actions/claim
If omitted, receiveChainId defaults to HyperEVM 999. If provided, it must match an enabled entry in config.withdraw.supportedDestinations. For a non-HyperEVM destination, Signalite returns withdrawal metadata showing:
  • the requested destination chain
  • the HyperEVM settlement chain
  • whether Relay is required now or later
  • for instant redeem and claim: the Relay deposit address used as the receiver
  • for queued redeem: mode="post-claim-quote" with relay=null
  • for instant redeem and claim: the Relay requestId and status URL
Submit only the HyperEVM Signalite redeem or claim transaction hash to Signalite. Do not execute a second Relay bridge transaction, and do not submit Relay or destination-chain hashes. For queued withdrawals, persist the user’s selected destination when the queued redeem is created and pass the same receiveChainId again when creating the claim action. Do not treat missing Relay deposit-address metadata as an error for redeem_async. It is only an error for a non-HyperEVM redeem_instant or claim_redeem action whose metadata claims mode="deposit-address". Queued withdrawals are fulfilled FIFO. A later smaller withdrawal must not jump an earlier larger withdrawal just because the current buffer can cover it.

​
Copy

Use:
USDC routes to your selected network after the Signalite withdrawal confirms.
Do not imply that the user must manually claim HyperEVM USDC and then bridge it.