Connect your wallet.
Sign in and link a Solana wallet to your AUVEN profile.
AUVEN / PRODUCT ROADMAPControl first.
Control first.
Then utility.
This roadmap shows what is in progress and what is planned: agent controls, post-quantum proofs, holder benefits, and agent rentals. It also shows how $AUVEN is intended to work within the product.
AUVENHOLDER PROOFYOUR WALLETSolana wallet linked to your accountVerified through Privy
$AUVEN BALANCERead from the Solana token mintObserved at a specific slot
YOUR AGENT'S PROOF
ML-DSA-65 signedExport and verify the record
ML-DSA-65 signedExport and verify the recordWALLETBALANCE CHECKSIGNED PROOF
IN TEST PHASE
Start with useful controls.
Connect agents, set limits, review requests, and export signed activity records. Link a Solana wallet to check its $AUVEN balance and sign a holder snapshot for an agent. The roadmap below shows how these foundations lead to paid usage and agent rental.
HOLDER PROOF
Connect. Check. Prove.
AUVEN reads your linked wallet balance without moving or locking your tokens.
Check your tokens.
AUVEN reads the $AUVEN balance at a recorded Solana slot.
Create the proof.
Choose a registered agent. AUVEN signs the wallet, balance, mint, and observed slot with ML-DSA-65.
PRODUCT + TOKEN ROADMAPBuild the controls.
Build the controls.
Then open the network.
Start with agent identity, policy, and verifiable records. Add agents created in AUVEN, paid usage, and a marketplace where creators can let others use their agents. Each step gives $AUVEN a specific role in the product.
Test phase Planned
01
FOUNDATIONTEST PHASE
Connect and control an agent.
Register an agent you already run. Send supported requests through AUVEN to apply daily limits and owner approval. Inspect activity, export ML-DSA-65 signed records, and publish a proof commitment when configured.
$AUVEN todayLink a Solana wallet, check its balance, and create a signed holder snapshot for an agent. Holding tokens does not yet change your limits or unlock paid features.
02
AGENT BUILDERTEST PHASE
Create an agent in your workspace.
Define a text agent's job and instructions, set its limits, and try it from the dashboard. Use its AUVEN credential through the supported MCP tool or API. More agent types and external tools are in development.
$AUVEN roleCore creation and policy controls do not require a token. Paid capacity and holder benefits are planned for a later step.
03
HOLDER ACCESS + PAYMENTSPLANNED
A stronger model for your agents.
We are preparing GPT-6 Astra as an optional model for agents in eligible workspaces. The initial proposal is to hold at least 1,000,000 $AUVEN in linked Solana wallets for up to three Astra requests per workspace each UTC day. AUVEN checks the balance before the request and again after owner approval. Existing agent limits still apply. We will confirm these terms before opening access.
GPT-6 Astra accessThree requests per day50% off eligible AUVEN fees
$AUVEN roleHolding tokens would unlock the model without transferring or locking them. Separately, we plan a 50% discount on eligible AUVEN service fees paid in $AUVEN. Creator prices and third-party model costs are separate. Token payments and holder access are not active yet.
04
AGENT RENTALPLANNED
Let others use the agent you built.
A creator could publish an agent with a clear description, usage price, and allowed actions. Another user could pay per run or for a period of access. AUVEN would enforce the creator's limits, track each run, and separate the creator payout from its platform fee.
$AUVEN rolePlanned payment option for access to listed agents. Listings, billing, payouts, and fee splits need to be built before rentals can open.
05
BUYBACK + BURNPLANNED
Connect product revenue to the token.
We plan to allocate a defined part of AUVEN's own service fees to buy $AUVEN and burn the purchased tokens. Creator earnings would stay separate. The allocation, timing, and transaction records will be published before this starts.
$AUVEN rolePurchased tokens would be removed from circulation. This is a product plan, not an active burn mechanism or a payment to token holders.
THE PLANNED RENTAL FLOW
One agent. A clear path from creation to use.
The creator keeps the agent's instructions and policy in their workspace. A customer sees the terms before paying. Each permitted run goes through AUVEN, where usage can be measured and the fee accounted for.
CREATORBuild + listSet price and permissions
→CUSTOMERPay for accessSee terms before use
→AUVENCheck + recordEnforce limits per run
Creator payoutAUVEN fee → proposed buyback + burn
Illustrative roadmap, not a live checkout. Rental prices, token payment rules, creator payouts, and buyback allocation have not been set.
POST-QUANTUM PROOFA record you can
A record you can
check yourself.
Agent passports, activity checkpoints, and holder proofs use ML-DSA-65 signatures that you can export and verify. A separate Solana transaction can record a proof commitment when publication is configured.
Open ProofsAGENT HOLDER PROOFML-DSA-65
NetworkSolana
Recorded balanceAt a specific slot
SignatureVerifiable outside AUVEN
TOKEN MINT
$AUVEN on Solana.
This is the mint AUVEN reads for wallet balances. A holder proof is a signed snapshot of the amount observed at one Solana slot; it does not move tokens or guarantee a later balance.