Guides

Resume a saved transaction

The app saves each signed deposit, withdrawal, order and read before sending it, so an interrupted one is resumed, never repeated.

Before the app sends a deposit, withdrawal, order or remaining-size read you signed, it saves the exact signed transaction on this device. If the network drops or the page closes, you resume that same transaction instead of signing a new one. A retry can't move funds twice or place a second order.

If the network refuses the transaction before sending it, for example because a matching round took the book first, nothing was sent: the saved copy is cleared and you can simply try again.

A deposit or withdrawal#

If a transfer was signed but not confirmed, the Vault panel shows it and offers Resume the saved deposit (or withdrawal).

1. Choose Resume.
2. The app checks the transaction's status on Solana and, if it hasn't landed, sends the same signed bytes again.
3. Once it is finalized, either way, the saved record clears and you can make a new transfer.

A new transfer waits until the saved one is resolved.

An order#

If an order transaction was signed but its history record didn't reach the server, Your order offers Record it in history (or Finish the signed order saved on this device). The app confirms the saved transaction and records your encrypted submission, without asking you to sign again.

A remaining-size read#

Choosing Read remaining size again resumes the saved request. See Read your remaining size.