Skip to content

Cross-chain safeguards

  • Signature binding: cross-chain redemption data includes the Vault, asset, amount, destination chain, expiration, and signature domain. The contract verifies the signer against the Vault owner.
  • Expiration management: contracts only accept signatures within their validity period.
  • Replay protection: used signature hashes are recorded on-chain so each authorization is executed once according to the rules.
  • Asset scope controls: bridged assets must be on the platform’s allowlist.
  • Destination account validation: applicable paths verify the destination Vault’s registration and owner relationship.
  • Amount controls: the actual bridge amount is constrained by the amount authorized in the user’s signature.
  • Daily withdrawal limit: the system tracks daily on-chain withdrawals and valid pending signed amounts by Vault and asset and exposes the remaining allowance.
  • On-chain confirmation: after the AA Bundler submits a transaction, the system continues to query the UserOperation receipt and transaction receipt. Standard receipt queries continue confirmation after a connection switch.

The source chain currently configured in the client is Base (chain ID 8453), and the Jasper Vault chain ID is 55531.

Status What the user can do
Base transaction is pending confirmation Look up the transaction hash on BaseScan and wait for block confirmation
Base is confirmed and the Jasper Vault balance is updating Keep the transaction hash and check Warp Router events and the destination AA Vault balance
Arrival takes longer than the estimate shown in the UI Provide support with the wallet address, source-chain transaction hash, asset, and amount
RPC or Bundler connection switches The system continues tracking through connection recovery, bounded retries, and transaction receipt queries
The same authorization is submitted again The system returns the original transaction status or ends the request based on the on-chain usage record