Transaction confirmation and recovery

Windup's supported Elysium flow can ask you to approve two stages:

1. Sign the Elysium transaction containing the action, such as a launch or trade.
2. Submit those exact signed bytes through the HyperEVM Inbox for execution on Elysium.

The app switches networks as needed. The parent delivery call carries zero native value. A 5-HYPE launch bond is paid by the child transaction from your Elysium balance, while HyperEVM HYPE pays delivery gas.

The app checks both stages. A queued child hash or a successful HyperEVM receipt alone does not prove the Elysium trade completed.

If a transaction appears stuck#

Use Verify transaction before submitting the action again. The app keeps the original request and looks for its exact hash, nonce and receipt.

A lost response can occur after a transaction was already submitted. Repeating the launch or trade as a new request can create a second action. Do not clear the saved request just to remove a pending message.

If you need help investigating, keep:

• Your public wallet address.
• The action and token address.
• The Elysium transaction hash, if available.
• The HyperEVM delivery hash, if available.
• The time and error message.

Never share your seed phrase or private key. Transaction hashes and public addresses are enough to begin checking the onchain result.

A confirmed revert means the action failed. It can still consume gas. An unknown or pending result needs reconciliation; it is not evidence that nothing happened.