Current Boundaries & Limitations
We believe transparency builds trust. This page outlines the exact operational boundaries, intentional restrictions, and non-goals of the current release.
Explicit Boundaries & Constraints
1. Hackathon Release & Demonstration Router
Xecute is an active hackathon-stage release and is not production-audited financial infrastructure. Testnet swaps execute through the deployed XecuteTestnetRouter demonstration contract.
2. Testnet-Only State Execution
State-changing execution (token swaps, approvals, transfers, revocations) is enabled exclusively on X Layer Testnet (1952). Mainnet (196) execution is intentionally disabled to limit financial risk.
3. Configured Token Registry Scope
Execution and approval scans operate against a configured registry of supported X Layer assets (OKB, USDT, USDC, WETH, WBTC). Unsupported long-tail tokens require manual contract interaction.
4. Testnet Asset Valuation
Tokens on X Layer Testnet have no real-world monetary value and exist solely for demonstration, testing, and benchmark verification.
5. Simulation & Pre-Flight Scope
Simulation dry-runs transactions against currently observed state (eth_estimateGas) to detect likely execution failures before signing. It cannot guarantee future block state or eliminate network-level latency.
6. Protect Scan Scope
Wallet Protect audits discoverable onchain ERC-20 allowances against the configured token registry. It does not prove a wallet is globally free from all offchain, permit2, or unindexed risks.
7. Fail-Closed on Unverified State
If an RPC endpoint fails to respond or a token quote is unavailable, Xecute will refuse to prepare a transaction rather than guessing or fabricating numbers.
8. Mainnet Capability Manifest
The Mainnet Capability Manifest is an immutable onchain deployment record of the current release state. It does not constitute production financial infrastructure and does not enable, control, or gate any Mainnet state-changing execution.