Documentation
How VEX works.
The model proposes. Your rules decide what executes. The chain records what happened. This is the reference for those three layers.
01 · Overview
It never holds the pen.
VEX runs AI-driven trading from your own machine. An agent can read markets and propose trades, but it never holds authority to act. Every proposed action clears a fail-closed safety gate before it can be signed, and every outcome, executed or blocked, is written to the same local log.
The result is two guarantees a cloud agent can't give you: enforcement you control, and a track record you can check yourself.
The model proposes. The runtime enforces. The log records.
02 · The Runtime
A desktop app, not a cloud.
VEX is a native desktop app, not a chatbot and not a cloud service. The runtime, memory, audit log, and custody all live locally. The agent proposes intents; the runtime is the only component that can sign and submit them.
03 · Enforcement
One gate, no exceptions.
The model can propose. The runtime decides what is allowed to execute. Every swap and bridge clears the same fail-closed safety check before it signs, whether the session is restricted or running full autonomy. The gate is never relaxed for autonomy level.
A mission does not run forever unchecked. It ends and reports why:
04 · Proof
A record you can check.
No screenshots. No cherry-picked wins. Every decision, executed or blocked, is written to the same log, hashed for deduplication, without exposing how you trade.
05 · Missions
Goals that outlive the chat.
A mission is a long-running goal with your rules attached. You describe it in plain English, "Short gold in this range, stop at 4170", and it runs for days, not messages, surviving restarts.
A mission with nothing to do parks itself and makes zero model calls until its scheduled wake; a sleeping mission costs nothing.
06 · Venues & Chains
One runtime, every venue.
VEX operates across EVM and Solana, up to three wallets each per session, with address reads kept separate from signing at every step.
07 · $VEX
The token behind the runtime.
The app is the product. The token powers the network around it. $VEX is live on Robinhood Chain via Virtuals Protocol, and trading fees buy back $VEX. Verified copy trading follows, with every follower running inside their own limits.
0x8Ff92566f2e81BDd68EDfAa8cde73942A723796b · verify against the address posted by @ProjectVEXai08 · Security & Custody
Your keys never travel.
09 · FAQ
The questions that decide trust.
01Can VEX move funds without me?
No. The model can only propose. Every state-changing action clears a fail-closed safety gate before it executes, and in restricted mode nothing signs until you approve it. An unanswered approval expires in an hour and the mission moves on without it.
02Where do my private keys live?
On your machine, never transmitted to VEX. Keys are encrypted at rest with AES-256-GCM and used only at the signing boundary, after an action clears the safety gate. No cloud relay, no custodial server, no remote key escrow; backup and restore never touch the network.
03Is any of this cloud-dependent?
No. VEX is a native desktop app. Runtime, memory, audit logs, and custody all live locally. The only outbound calls are the protocol and model endpoints you explicitly enable; your strategy and keys are never sent to us.
04Where do I buy $VEX?
Through Virtuals Protocol on Robinhood Chain: the Buy button on this page goes to the official listing. Verify the contract address against the one posted by @ProjectVEXai before you trade. If a link did not come from this site or that account, treat it as fake.
05What is the token for?
$VEX powers the network around the runtime: trading fees buy back $VEX, and verified track records are becoming a followable network: humans and agents copying strategies inside their own limits. The app itself stays the product.