Notes from inside the walls

Elysium in five minutes

Elysium is an Arbitrum Orbit chain with chain ID 99901. Like any rollup it batches transactions cheaply and settles them to a parent chain, which for Elysium is HyperEVM, the EVM side of Hyperliquid. Its native gas token is HYPE, so the same coin you hold on Hyperliquid pays for every swap and launch.

Because it is an EVM chain, ordinary wallets work once the network is added: chain ID 99901, currency HYPE, and a public RPC. The Troya app can add it for you from the Bridge page.

Getting HYPE onto Elysium is a deposit through the rollup's inbox contract on HyperEVM, and it arrives quickly. Going the other way is slower by design: withdrawals wait out the rollup's security period before they can be claimed on HyperEVM. Plan for days, not minutes.

Most activity on Elysium today comes from launchpads such as BOXA and Montra, which mint new tokens and seed their pools in one go. That is exactly why Troya leans so heavily on reading before acting.

How Troya Gate reads a pool

Before a swap is shown to you, and again before the Agent Wallet would sign it, Troya Gate asks five questions. Is the route made of pools that exist right now? How far does this order push the price? Is there enough liquidity behind the quote to get back out? Does a test sell go through, or does it revert? Is there a transfer tax hidden from the quote?

The checks are deliberately boring. They catch the most common ways a fresh token takes your HYPE: a honeypot that cannot be sold, a pool too shallow to exit, a contract that quietly keeps a cut on every transfer.

When a check fails, Troya does not argue with you or quietly adjust the order. It stops, names the check that failed and shows the number behind it. What you do next is your decision.

Why the limits live outside the model

It is tempting to tell a language model "never trade more than 100 dollars" and call it a limit. It is not one. A model can misread the instruction, be talked out of it, or be steered by text it reads along the way, including text planted in a token name.

Troya keeps limits in a policy file on the server. The model never sees an editable copy and cannot write to it. Every tool call that could spend money loads the policy fresh and checks the order against it before anything is signed. If the policy says no, the answer is no, however good the model's reasoning sounded.

The model's job is to read, explain and propose. The policy's job is to decide what is allowed. Keeping those two jobs apart is the whole point.

Agent Wallet: pocket money, not a vault

Signing every trade yourself is the safest way to use Troya, and it is the default. The Agent Wallet exists for the moments when that is impractical: a stop-loss that should fire while you sleep, a DCA that runs every week.

It is custodial. The operator holds its key, encrypted at rest, so the agent can sign without asking you each time. That convenience is also the risk, which is why it only acts inside your caps, only withdraws to your own address, lets you export its key at any time and never touches your main wallet.

The rule of thumb is simple: keep in it only what you would be comfortable losing.

Prices in HYPE, and why USD is an estimate

Almost every Elysium pool pairs a token with HYPE, so HYPE is the honest unit for prices there. Troya shows HYPE first and converts to USD using the HYPE mid price from Hyperliquid. The conversion is good enough to compare tokens, but it moves whenever HYPE moves.

Market caps on the board are estimates from total supply. For a token whose supply sits mostly in a locked pool, that number can look far larger than what anyone could actually sell into. Liquidity and 24h volume usually tell you more.

Dry-run first: connecting your agent safely

Add the Troya MCP server to Claude Desktop, Cursor or Claude Code with one command and you get the read tools straight away. No token is needed to look at markets.

If you add an API token for Agent Wallet tools, execution still starts in dry-run: your agent can prepare orders, see them pass or fail Troya Gate, and read what would have happened, without sending anything. Spend a day there. When the proposals look the way you expect, switch dry-run off for that token in the app.

Set up the MCP