The problem MOVA solves

The Problem: Fragmentation & Trust Friction in Digital Money Movement

• Both small merchants (SMEs) and retail users face heavy friction when moving money across disconnected financial ecosystems. From payment methods and compliance to AI-generated reports and on-chain execution, four key barriers limit seamless and trusted money movement.

• First, funds and payment options are fragmented across multiple platforms, making everyday retail checkouts, QR payments, and SME asset transfers slow and inefficient.

• In addition, traditional compliance checks remain manual and cumbersome, creating operational bottlenecks when enforcing strict AML/CFT regulatory standards before payment execution.

• Also, businesses relying on AI-generated financial audit reports lack cryptographic verification, leaving them uncertain about the accuracy and legal authenticity of their records.

• Finally, navigating cross-chain and off-chain execution introduces technical risks, latency, and security vulnerabilities during final settlement. Web3 still lacks smart financial systems that can understand what users want and automatically complete transactions. This makes it difficult to connect digital assets smoothly with the existing Web2 economy.

To address these challenges, MOVA was created as a unified, compliant payment gateway. By combining instant QR scanning, natural language processing (NLP), real-time option vault yield, MLS-based compliance, and TEE-verified audit reports, MOVA connects digital assets directly to real-world commerce in a secure, seamless environment.

Challenges we ran into

1. Verifying AI Audits inside TEE Enclaves
   Bridging off-chain LLM inference with on-chain cryptographic proofs proved complex. Ensuring that the Trusted Execution Environment (TEE) could securely log execution traces, sign the audit reports, and output verifiable proofs directly to user channels presented significant cryptographic overhead and enclave memory isolation issues during multi-matrix testing.

2. Intent Resolution for Complex Treasury Commands
   Building an AI parser that reliably converts multi-step prompts into deterministic financial calls required extensive fine-tuning. We had to design strict fallback verification steps and context-aware UI pruning to ensure users always preview exact mathematical routing and cost comparisons before approving execution.

3. Yield-Generating Vaults Work for Instant Payments
   Embedding the Thetanuts OptionBook SDK into a daily merchant settlement flow required managing capital lockups against real-time float needs. Dynamic option vaults are inherently designed for yield rather than immediate liquidity
   Also, building an automated rebalancing engine that harvests yield while maintaining an optimal liquidity buffer for instant QR settlements was technically demanding.

4. Sui RPC migration (JSON-RPC → gRPC)
   Public Sui fullnodes deprecated plain JSON-RPC, forcing a move to SuiGrpcClient (@mysten/sui/grpc). The gRPC API differs sharply from JSON-RPC, results are discriminated unions ({ $kind: "Transaction" | "FailedTransaction", … }).
   Options use include: instead of options:, and dry-run/submit/confirm each need different calls.

5. Fail-closed compliance & hedging with limited integrations
   The compliance gate must fail closed (provider error → REVIEW/BLOCK, never ALLOW), and Thetanuts V4 only supports ETH/BTC underlyings — so SUI/USDC/MOV genuinely return INTEGRATION_UNAVAILABLE instead of faking a live hedge.