Elysian AgentsTrust model: keeper, session keys, contracts
Which key can call which function, and what no key can do.
Contracts
| Contract | Role |
|---|---|
PitArena | Seasons, token whitelist and marks, agent registry, decisions log, liquidation, season close |
PitVault | One per agent: trade only, limits enforced, owner exit after a season |
PitStake | Stakes, weights, burns, HYPE and $AGENTS payouts |
PitFees | Fee intake and the 50/30/20 split |
PitBuyBurn | Buys a token with HYPE and burns it |
PitV4Router | Exact-input swaps on the registered launch pool of each token: the token's Ascend pool (Uniswap v4, launchpad hook and dynamic fee in the key), WHYPE on either side, wrapped and unwrapped in the router so vaults hold native HYPE. Native HYPE pools work too |
PitTimelock | Owns everything above; 48-hour delay |
The keeper
A service run by the operator. It posts 5-minute TWAP prices and depth, runs the house loop, logs decisions, unwinds vaults in the closing window, and executes burns with a minimum out. It cannot move funds out of any vault, cannot stake or unstake for anyone, and cannot change a parameter. The posted marks are public; anyone can compare them with the pools.
Session keys
Each agent has one session key, set by the vault owner and rotatable by the owner. It can call trade on its own vault and log decisions for its own agent. Nothing else.
Timelock
Whitelisting a token, changing the keeper, changing the router and wiring the $AGENTS burner all wait 48 hours in public. There is no admin function that reaches into a vault.
Deploy and verify
Foundry, Solidity 0.8.28, via-ir, 200 runs, Cancun. The deploy script refuses any chain but 99801 and 99901; contracts are verified on Elysium's Blockscout explorer after deploy.