The architecture behind the trade.

Execution has one accountable home.

Exchange owns admission, execution validation and liquidity-provider relationships. Hybrid Banking and other ecosystem applications submit delegated requests to Exchange and consume the resulting state.

Identity stays with Hybrid ID. Account permissions, product eligibility and business approvals are evaluated separately. A successful sign-in does not authorize a trade.

Connected funds. One account balance.

MPC wallets manage custody and authorized transfers. Hybrid Core records funded balances and reserves what can be spent. Trading and withdrawal requests draw on that same available balance; funds held for one cannot be spent by the other.

Deposits become available only after the applicable funding checks and issuance steps. Exchange requests execution against Core’s reservation, then Core accounts for the resulting assets and fees.

An uncertain response is not a failed trade.

The Rust foundation retains request identity across duplicate delivery, lost replies and restarts. Reserved assets remain protected while an uncertain command is reconciled.

Partial fills and cancellation races need their own accounting. A cancellation cannot undo an executed fill, and a completed match does not by itself establish settlement or a verified chain record.