The quote selects the Solana execution mechanism. Preserve its protocol identifiers and transaction bytes. Engine-operated transactions use the protocol’s SIMD-0385 message format. Explicit wallet-paid plans use Solana v0 transactions with compute-budget instructions. These format identifiers are part of the protocol.

Wallet plans

Register the unchanged plan before sending its transactions. Validate lookup tables and mint data through trusted RPC access. Sign and broadcast the steps in their declared order. Wait for the swap result before sending the dependent open. The two-step plan is not atomic. A successful swap followed by a failed open can leave CTM in the user’s wallet. Reconcile the original open before creating a CTM-only replacement order.

Native SOL

Native SOL uses the 32-byte zero asset identifier under the swap-token mechanism. The execution wraps SOL where the swap requires wrapped SOL. A request naming the wrapped-SOL mint spends existing tokens instead. wrap-native is reserved for native CTM on c8ntinuum. Sponsored execution uses durable nonce ownership managed by the engine. A signed transaction with an unknown outcome must not release its nonce for unrelated reuse. Wallet plans use recent blockhashes and require expiry-aware recovery. See Solana refunds for refund construction.