Security

See it first.
Sign it yourself.

AUVA Protocol reads the chain, previews transactions and prepares deployments. It never holds keys, and nothing is sent unless you sign it in your own wallet.

01 · No keys

The server
cannot sign or send.

The safest way to protect a key is never to hold it. AUVA Protocol is built so that it cannot move funds even if an agent asked it to.

By design

No wallet on the server

The server has no private key, no seed phrase and no signing code. It never asks for yours.

By design

Tools that cannot send

The tools read the chain, compile code and estimate fees. None of them signs or submits a transaction to the network. Every tool is marked read-only in tools/list.

By design

You sign in your own wallet

When you deploy a contract or trade in the Terminal, you see a preview first: the source or the amounts, the fee and the minimum you accept. Your browser wallet signs and sends it; the transaction never passes through our server.

02 · Simulation

What a dry-run
tells you.

Before you sign anything, your agent can run the transaction against the chain as it is right now with simulate_transaction.

You learn

Will it go through?

Success, or the exact revert reason the contract gives — for example an insufficient balance or a blocked address.

You learn

What will it cost?

A gas estimate and the fee at the current gas price, in the network’s native currency.

Keep in mind

A snapshot, not a promise

The chain keeps moving. Prices, balances and gas can change between the dry-run and your signature, so check the details in your wallet too.

03 · Your data

What is stored:
nothing.

Stateless

No accounts, no sessions

There is no sign-up and no login. Each request is answered and forgotten; the application keeps no database. Short-lived caches (seconds to minutes) only hold public chain data.

Transparent

Where requests go

Your question is turned into a standard RPC call to a public node for the network you named, or to DexScreener, GeckoTerminal, Sourcify, Blockscout and LI.FI for market, source and route data. Those operators can see the addresses being queried — as with any block explorer.

Public data

Only what is already on-chain

Everything returned is public blockchain data. Nothing private about you is needed to use it.

04 · Known limits

Read this
before relying on it.

AUVA Protocol is new. These are the honest edges of what it does today.

It has not been audited. Treat results as a helpful first look, and confirm anything important on a block explorer.

AI can misread data. The numbers come from the chain, but the explanation comes from your AI model. Check amounts, addresses and decimals yourself before signing.

Deployments are final. A deployed contract cannot be edited or removed. Read the source in the review panel before you sign.

The safety scan is a heuristic. It looks for known admin function selectors in the bytecode. A clean result does not prove a token is safe, and a flag does not prove it is malicious.

Public nodes can be slow or rate-limited. If a network stalls, AUVA Protocol tries a fallback node, but answers can still time out. Check the status page.

Nothing here is financial advice. Market data is shown as it comes from the pools. Make your own decisions.