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 page
Read the state before retryingLiquidity: recover the actual hashDesk: reconciliation messagesInformation to keep for troubleshootingRead the state before retrying
| State | Meaning / next step |
|---|---|
| Prepared | Unsigned proposal. Inspect its current amounts, network, gas and deadline. |
| Armed / uncertain | The wallet may have received a request. Check wallet activity and preserve any hash. |
| Submitted / pending | A hash is tracked; wait for canonical confirmation or reconcile the confirmed replacement. |
| Confirmed | The intended transaction was verified onchain. Refresh balances and inspect its actual result. |
| Reverted | The transaction failed onchain. Gas may be spent; inspect the reason before a new review. |
| Cancelled / replaced | A verified different transaction consumed that nonce. The original LP action is not recorded as executed. |
Liquidity: recover the actual hash
- 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.
- 02
Open Recover transaction
Paste the confirmed original or replacement hash. The server checks wallet/chain/nonce and canonical inclusion before resolving the intent.
- 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.
- 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
| Message / situation | What to do |
|---|---|
| Pool event reconciliation is catching up | Open Fund Pool, inspect sync progress and use Sync pool & receipts. Wait for canonical accounting to finish before Start. |
| Reconcile pending Quoter transactions | Inspect the pending oracle hash and sync receipts. Do not reset the journal or discard the nonce. |
| Quoter gas is low | Stop quoting and review its separate gas top-up. A top-up does not resolve or erase a pending update. |
| Start blocked after settings change/restart | Reconcile receipts, check current limits and data, then provide a fresh owner Start signature. |
| RPC or connection error | Keep 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.