TESERASecurity
Tesera lets an AI read Elysium, simulate what a transaction will do and prepare it for you to sign. This page explains the layers that sit around that, what always stays under your control, and what to do if something looks wrong.
Your keys stay with you
The rule everything else is built on
Layers of protection
From the outside in, ending at your own signature
Rate limits
Each connection can make 120 requests a minute, and 10 of the heavier ones, such as compiling or starting a new index or watch. An optional access key raises that to 600 and 60, counted per key. This stops a looping agent or a misconfigured client from flooding the gateway. Connections are counted by a salted one-way fingerprint of the IP address, so no IP address is ever stored.
Clean data
Token names, agent cards, event data and documentation are written by other people, so the gateway strips hidden and direction-flipping characters from them and caps their length before your AI sees them. Your AI is also told to treat that text as data and never follow instructions found in it. Oversized requests and oversized replies from outside services are refused.
Simulation and preview
Before anything that changes state reaches you, Tesera runs it against live Elysium state. You get the result in plain words: whether it succeeds or the exact reason it would revert, which balances change, which events fire and what it costs in HYPE. If the simulation fails, nothing is offered for signing.
Plain warnings
Every prepared transaction is checked for the common ways people lose funds: unlimited approvals, approvals to a plain wallet instead of an app, copycat tokens using a well-known name, recipients that look like an address you have used before but are not, sends to a burn address or to a token contract, unverified contracts, and moving most of a balance at once. Your AI is told to show you every warning before you sign.
Nothing to steal
There are no accounts, no passwords and no stored IP addresses. The gateway never holds private keys, so even a full breach of our servers could not move your funds. Watches and indexes are tied to random IDs, not to people, and deleting a watch wipes what it held straight away.
Your own signature
Tesera only prepares unsigned transactions. Nothing is sent until you review the transaction and sign it in your own wallet. This is the innermost layer, and nothing the AI is asked to do can get around it.
Reading needs no wallet at all. Balances, blocks, contracts and docs can be checked without connecting anything that can spend.
Tesera Shield
One verdict before every signature. Live
Turnkey
Agent keys can live in a Turnkey policy wallet, where every signing request is checked against your rules inside a secure enclave before a signature exists.
GoPlus Security
Every token and contract a transaction touches is checked for honeypots, hidden mint or blacklist functions and malicious approvals.
Chainalysis
Every recipient and spender is checked against sanctions lists from the United States, the European Union and the United Nations.
Chainstack
Simulation runs on Chainstack infrastructure, so the outcome is known before anything is offered for signing.
Tesera integrates these services through their public APIs. Naming them does not mean they endorse Tesera, and Tesera is not affiliated with any of them.
If something looks wrong
Three steps, in this order
Revoke approvals
If you approved a contract or address you no longer trust, set that approval back to zero straight away. Your AI can prepare the revoke for you with Tesera, and you sign it in your wallet. Nothing else can be sent without your signature.
Check what happened
Look up your address on the Elysium explorer, or ask your AI to read your recent transactions through Tesera, and compare them with what you meant to sign.
Report it
Tell us what happened through the contact page. Include the time, your address and any transaction hashes, and never include a private key or seed phrase.
What these protections cover
The limits worth knowing
Reads need no wallet
Checking balances, blocks, contracts and docs needs no wallet. You can use Tesera for reading alone and never connect anything that can spend.
An AI can misread a request
The model in your client can get things wrong. Read each preview and every warning before you sign.
Confirmed transactions are final
Once a signed transaction is confirmed on Elysium, Tesera cannot reverse it or recover funds. The layers above exist to stop mistakes before that point.
Reporting a vulnerability
If you find a security issue in Tesera, please report it privately through the contact page and give us time to fix it before sharing details publicly.