Cross-Chain Execution

Once you confirm a route, 7.Exchange ensures the transaction you sign matches the route you approved. This page explains how the execution pipeline protects your trade.

The execution flow

1. You select a route After reviewing available routes, you choose one and click Swap.
2. Quote is locked The system locks the selected quote, assigning it a unique identifier. This quote is now reserved for your session.
3. Execution payload is built The routing engine constructs a transaction payload through the selected provider. This payload contains all the instructions for the swap.
4. You sign The payload is sent to your wallet. You review and sign the transaction.
5. Transaction is broadcast Your signed transaction is submitted to the blockchain.
6. Execution is tracked The execution tracker monitors progress across chains until delivery.

Quote authentication

Every quote generated by 7.Exchange has built-in protections:

Unique ID Each quote is assigned an identifier that ties it to your specific request. No two quotes share the same ID.

Single-use A quote can only be executed once. After execution (or expiration), the ID is invalidated. This prevents replay attacks where a stale transaction could be resubmitted.

Time-bound Quotes expire after a short window. If you don't execute within that window, the quote is discarded and a fresh one is generated with current market data.

Session-bound The quote is tied to your wallet session. It cannot be intercepted and executed by a different address.

What happens during a cross-chain swap

Cross-chain swaps are not instant. After you sign the transaction, the execution involves multiple stages depending on the route:

1. Source chain transaction Your tokens leave your wallet on the source chain.
2. Bridge transfer The bridge provider handles the cross-chain message and asset transfer. This is typically the longest step and depends on the bridge protocol's finality requirements.
3. Destination chain delivery Tokens arrive at your destination address on the target chain.

Throughout this process, the execution tracker in the 7.Exchange interface shows real-time status updates.

Transaction finality

What if something goes wrong

In rare cases, a cross-chain transaction may become stuck or fail mid-execution. Common causes include:

• Network congestion High traffic on source or destination chain delays confirmation
• Bridge delays Some bridge protocols require multiple block confirmations before releasing funds
• Insufficient gas The destination chain transaction may require gas that wasn't fully covered

If your transaction appears stuck:

1. Check the execution tracker for the latest status updates.
2. Wait most delayed transactions resolve within minutes to hours depending on the chains involved.
3. If the transaction remains unresolved, contact support with your Transaction ID or Quote ID.

Resolution of stuck cross-chain transactions may depend on the underlying provider's recovery mechanisms, which are outside 7.Exchange's control. See FAQ for more troubleshooting guidance.