Lifecycle of bridging session

Overview

• User fetches a quote to transfer Token A from Chain Y to Token B on Chain Y, selects a preferred route, and initiates bridging.
• The user then requests transaction data for the route's initial step. If a prior approval transaction for Bungee contracts is required, it is indicated in the response.
• Upon executing the transaction, the UI tracks its progress. The initial transaction in the route, aside from any necessary approval transactions, encompasses the Swap and Bridge operation. Bridging is conducted in a single step for Single Transaction Bridging, while Multi Transaction Bridging spans across multiple steps.
• For Multi Transaction bridging, the user, after starting a bridging transaction, obtains transaction data for the subsequent transaction (usually a swap or claim on the destination chain) and consults the status API. The transaction proceeds when the status API indicates a “READY” status.
• Upon completing the final transaction, the status API marks the route as “COMPLETED,” signifying the recipient has received the funds on the destination chain.