Security Model & Boundaries
Xecute is engineered around a strict boundary between AI intent interpretation and onchain financial execution to enforce security controls.
Key Security Principles
1. Non-Custodial Architecture
Xecute never custodies, touches, or holds user funds. Assets move only through transactions explicitly authorized and signed in the user's Web3 wallet.
2. Zero Private Key Access
Xecute never prompts for, reads, transmits, or stores private keys, seed phrases, or wallet credentials. All signing occurs locally within standard Web3 wallet software (MetaMask, OKX Wallet).
3. No Arbitrary AI Calldata Generation
The AI model is never allowed to directly output raw hex bytecode or arbitrary contract calls. Executable transactions are exclusively assembled by deterministic TypeScript adapters.
4. Mandatory Human-in-the-Loop Confirmation
Autonomous or automated transaction broadcast is strictly prohibited. Every single state-changing action requires the user to review the pre-flight balance deltas and manually confirm the transaction.
5. Fail-Closed Policy Enforcement
If an onchain state query fails, a gas estimate reverts, or a parameter fails validation, Xecute fails closed—meaning it returns an explicit error rather than guessing or fabricating placeholder data.