Skip to main content

Transaction Lifecycle

The easiest way to understand the full system is to follow transactions that touch settlement, the gate app, and application execution environments.

Deposits​

Deposits go through the bridge first. The bridge records the asset movement, the gate app receives the deposit event, and the gate routes the asset to the target app.

UserBridgeRelayerGate01 Deposit funds02 Monitors deposits03 Deposit event04 Credit user account05 Funds available

Withdrawals​

Withdrawals start in the target app. The app sends the withdrawal to the gate, and the gate forwards it to settlement during the next settlement update.

UserAppGateOperatorsBridgeApps01 Request withdrawal02 Send withdrawal funds03 Accumulate withdrawals04 Request state snapshots05 Send state hashes06 Submit aggregated state hash07 Validate and sign08 Submit signatures and state update09 Withdrawal enabled

Cross-app transfers​

Cross-app transfers are composed of app-level messages. The source app sends a transfer to the gate or destination app, and the destination app credits the user once the ordered message is processed.

UserGateSource appTarget app01 Request transfer02 Send funds03 Route funds04 Funds received

The important property is that most work stays inside the execution network. Settlement is used for security, data availability, and bridge effects rather than every internal app action.

These materials are provided for informational purposes only and do not constitute financial, investment, legal, or tax advice, or an offer or solicitation to buy or sell any asset. Trading digital assets and derivatives involves substantial risk, including the possible loss of some or all capital. Products may not be available in all jurisdictions. Users are responsible for evaluating suitability and complying with applicable laws.