DocsReference

Reference 6 MIN READ

Transactions & recovery

What to do when a request is pending, a wallet replaces a transaction, or the UI is catching up.

On this pageRead the state before retryingLiquidity: recover the actual hashDesk: reconciliation messagesInformation to keep for troubleshooting

Read the state before retrying

Read the state before retrying
StateMeaning / next step
PreparedUnsigned proposal. Inspect its current amounts, network, gas and deadline.
Armed / uncertainThe wallet may have received a request. Check wallet activity and preserve any hash.
Submitted / pendingA hash is tracked; wait for canonical confirmation or reconcile the confirmed replacement.
ConfirmedThe intended transaction was verified onchain. Refresh balances and inspect its actual result.
RevertedThe transaction failed onchain. Gas may be spent; inspect the reason before a new review.
Cancelled / replacedA verified different transaction consumed that nonce. The original LP action is not recorded as executed.

Liquidity: recover the actual hash

  1. 01

    Check wallet activity

    Find the original transaction, speed-up or cancel on its original chain: Elysium 99901 or HyperEVM 999. Compare wallet, nonce and manager. Keep its hash.

  2. 02

    Open Recover transaction

    Paste the confirmed original or replacement hash. The server checks wallet/chain/nonce and canonical inclusion before resolving the intent.

  3. 03

    Distinguish a speed-up from a cancel

    The same target/calldata/value can reconcile as the original action with reported gas changes. A different confirmed action at the same nonce resolves the original as cancelled/replaced.

  4. 04

    Use never sent carefully

    Only the actual owner who checked wallet activity should declare never sent, and both latest/pending nonces must still match. If the nonce was consumed, use its transaction proof instead.

Desk: reconciliation messages

Desk: reconciliation messages
Message / situationWhat to do
Pool event reconciliation is catching upOpen Fund Pool, inspect sync progress and use Sync pool & receipts. Wait for canonical accounting to finish before Start.
Reconcile pending Quoter transactionsInspect the pending oracle hash and sync receipts. Do not reset the journal or discard the nonce.
Quoter gas is lowStop quoting and review its separate gas top-up. A top-up does not resolve or erase a pending update.
Start blocked after settings change/restartReconcile receipts, check current limits and data, then provide a fresh owner Start signature.
RPC or connection errorKeep transaction hashes and the last known state. Refresh after connectivity returns; do not infer that a timed-out request never reached the chain.

Information to keep for troubleshooting

  • Application URL, wallet public address and chain ID.
  • The transaction hash, nonce and action, plus its time and exact visible error.
  • For Liquidity, the protocol and v3:tokenId / v4:tokenId; for Desk, the public pool/provider identity.
  • Never send a seed/private key, login/session cookie, signed launch message, remote-access password or unredacted secret configuration.

Jellysium's public X account is linked below. Verify any support claim independently; these docs do not authorize anyone to ask for wallet secrets or unsolicited transfers.