Get started
What is zuvie?
zuvie is an autonomous AI trading agent being built for Solana. It is designed to form its own view, trade inside hard risk limits, and settle every trade onchain where anyone can verify it.
From signal to settled trade
The agent runs one loop with no human in it: strategy decides what to trade, execution checks the order against risk limits and sends it, and settlement leaves a public record on Solana. The table below is the source of truth for what exists today. Only the site, these docs and the waitlist are live.
| Component | What it is | Status |
|---|---|---|
| Waitlist & docs | This site, the design docs, and the waitlist. | Live |
| Strategy engine | Model-driven signals and position sizing for Solana spot markets. | Waitlist |
| Risk limits | Hard caps on position size, drawdown and slippage, plus a kill switch. Enforced before any trade is signed. | Waitlist |
| Onchain execution | Orders routed through Jupiter's meta-aggregator and sent via Jito, as Solana transactions against onchain liquidity. | Waitlist |
| Public trade ledger | Every agent transaction listed with its signature, linkable to any explorer. | Waitlist |
| Performance from chain data | Returns computed only from onchain balances and fills, with the method published. | Waitlist |
| Enclave signing (planned: Turnkey) | Agent key held in a hardware enclave; the agent can request signatures but never holds the key. Policy enforced inside the enclave. | Waitlist |
| Treasury multisig (planned: Squads) | Treasury separated from trading funds; any movement needs a team signature. | Waitlist |
| Attested agent logic | Decision loop running in a TEE with a remote attestation quote per trade, so the running build can be verified. | Roadmap |
| Token & governance | Token launch on Meteora's bonding curve into a DAMM v2 pool; governance model TBD. Published here before anything exists. | Roadmap |
Custody model
The intended model is non-custodial at the key level: the agent signs with keys it cannot export, under a signing policy it cannot change, and every movement of funds is an onchain transaction. Two things are not decided or built yet, and are labelled that way:
- How capital enters the agent: no deposit mechanism exists, and deposits are not open.
- Where keys live: the planned design is enclave signing (Turnkey) with a policy engine, and it is not built yet.
See Custody & security for the full design and its status.
Why onchain
A trading agent’s record is only worth what you can check. Settling every trade onchain from a public address makes the record a matter of public data, not of trust in us. See Transparency.
What zuvie is not
It is not live, and it has no track record yet. It does not promise returns: an agent that trades can lose money, and a verifiable loss is still a loss. It is not a token: none exists. And it will not label a part live before it ships.
Everything on this page except the site, the docs and the waitlist is in development. Waitlist parts open to the waitlist first; roadmap parts have no date.