Transaction Management
Transaction Management
Lucid provides transaction management tools for monitoring bridge activity, reviewing execution status, resending failed transactions, and recovering transfers that do not appear in the History tab.
These tools help users track and manage cross-chain execution directly within the Lucid platform.
Transaction History
The Bridge History section displays previous bridge transactions and their current execution status.
Each transaction record includes:
| Field | Description |
|---|---|
| Time/Date | When the transaction occurred |
| Chains | Source and destination chains |
| Details | Token type and transfer amount |
| Origin Address | Wallet address that initiated the transfer |
| Bridges | Bridge providers used for the transaction |
| Status | Execution or consensus status |
| Actions | Options to inspect, resend, or review transaction details |
Resend Functionality
Lucid supports transaction resubmission through alternative bridge providers when one or more interoperability providers fail during execution.
This functionality helps maintain transfer completion across multi-bridge execution environments.
Transaction Recovery
Transaction Recovery is used when a completed transfer does not appear in the History tab.
This can occur if a source-chain RPC node becomes temporarily unavailable while the transaction is being indexed.
Recovery operations are read-only and do not:
- move funds
- require gas
- require wallet signatures
Recovery FAQ
| Question | Answer |
|---|---|
| Is recovery safe? | Yes. Recovery only re-indexes already finalised on-chain events. |
| Does recovery cost gas? | No. Recovery operations occur server-side. |
| What if the wrong hash or chain is submitted? | The system returns that no bridge events were found. |
| Can the Lucid team assist with recovery? | Yes. Users can provide the source chain and transaction hash for assistance. |