Current Phase and Roadmap

AoraEX is in a read-only infrastructure phase. Product baseline: liveTrading = false. Ledger crediting, signing, broadcasting, live orders, and withdrawals belong to a later phase. Interface entry points, directory status, and design proposals should be read in their own columns.

Capabilities confirmed in the current codebase

• Privy identity verification and a match against an Ethereum wallet linked in the server-side profile.
• Read-only observation of public Hyperliquid account data.
• Funding-intent creation and on-chain observation records.
• Copy-trading previews and paper replay.
• Credits deduction logic for AI requests.
• Composer: after wallet + NFT checks, read public Hyperliquid quotes for chat or strategy drafts.
• Personal Center can mint custom Agent artwork; execution follows Free / Plus / Marketplace, and the last two tool groups are pending.
• Connector-directory status for venues such as Hyperliquid and ASTER.
• Chinese and English documentation sites.

Awaiting separate acceptance

• Live fund crediting and a spendable-balance ledger.
• Real transfers from a funding account to a trading account, withdrawals, or bridge execution.
• Venue authorization flows such as approveAgent and approveBuilderFee.
• Live order placement, cancellation, and fill reconciliation on Hyperliquid or ASTER.
• NFT issuance by an on-chain contract (planned after an MPC wallet is opened and a deposit of at least 50 USDC).
• veAORA staking, and Plus-tier MCP such as prediction markets or copy signals.
• A third-party MCP plugin marketplace.
• Continuous live copy trading, two-venue arbitrage, and DeFi fund deployment.
• Credit purchases and top-ups.

A capability is marked live after implementation, tests, production deployment, and an explicit acceptance record.

Suggested order of work

1. Validate production flows for read-only identity, account observations, funding intents, and audit records.
2. Define authoritative data sources, purchase, and reconciliation rules for the ledger and Credits.
3. If trading execution is approved again, complete the threat model, authorization design, limits, and rejection paths first.
4. Validate preview, approval, submission, fills, and failure recovery for a single venue in an isolated environment.
5. Expand venue or strategy coverage after each capability passes its own acceptance.

This roadmap is a plan. It gives a work order.