7 Deterministic Safeguards
Xecute protects users by enforcing deterministic policy constraints during intent preparation and executing live pre-flight checks before requesting wallet signatures.
Safeguard Architecture: Policy Required vs. Runtime Check Passed
Xecute distinguishes between Policy Required (static rule configuration such as slippage ceilings and address formats) and Runtime Check Passed (live checks evaluated after user confirmation and before wallet signing, including real-time balance queries, gas reserves, and simulation dry-runs).
Native Gas Reserve Buffer (≥ 0.005 OKB)
When swapping or transferring native OKB, Xecute checks that the user retains at least 0.005 OKB in their wallet. This prevents users from accidentally locking their wallet with zero gas to pay for future transactions.
Slippage Tolerance Ceiling (≤ 5.0%)
Xecute strictly enforces a maximum slippage tolerance of 5.0%. Any prompt or manual tuning requesting slippage above 5% is blocked. Slippage limits bound the maximum execution tolerance accepted by the user. They do not eliminate MEV or adverse market movement.
Strict Network Boundary Isolation
Xecute checks the connected wallet chain ID against X Layer Testnet chain ID 1952. State-changing actions are permitted only on X Layer Testnet, while Mainnet (196) is strictly locked to read-only advisory operations.
EVM Address Format Verification & Normalization
Recipient and spender addresses must pass 40-hex EVM formatting. Empty addresses, zero addresses (0x00...00), and malformed strings are blocked immediately, and valid addresses are normalized into canonical format before transaction preparation.
Real-Time Onchain Balance Verification
Xecute queries the token contract directly via eth_call before transaction preparation and wallet signing. If the wallet balance is insufficient, execution is blocked with clear feedback.
Transaction Simulation & Dynamic Gas Estimation
Before requesting wallet signature, Xecute dry-runs the transaction using eth_estimateGas and adds a safety margin to detect execution failures against observed state. If the dry-run reverts, Xecute fails closed rather than proposing a failing transaction.
Human-in-the-Loop Confirmation
Autonomous signing is strictly prohibited. Every state mutation requires an explicit button click on the Action Confirmation Card followed by personal signature approval in the user's Web3 wallet.