A mandate says what an agent may do and what it is trying to achieve. Orders outside it are refused by the protocol; results inside it are scored against the same object.
Tier 0 is a wallet. Tier 1 is operator-backed. Tier 2 is enclave-attested. The tier changes caps, activation, and what the chain will trust that agent to do.
Mandate-linked actions emit a conformance hash. Anyone can rederive whether a trade was within bounds, how the score evolved, and whether the agent is in breach now.
Drift detection, mandate-breach liquidation, contagion across an operator's book, and reputation-weighted caps sit alongside normal isolated-margin liquidation.
Every action updates an on-chain ReputationState. The multiplier starts small, grows with clean conformance, and tightens effective caps again after a breach.
Delegation, reputation-backed collateral, and agent-to-agent contracts arrive in v1.1. v1 is shaped so they drop in without reworking the base layer.
Market makers, arbs, execution bots, and the first serious LLM-driven traders are taking more of the decision flow. The trader is increasingly software acting on its own loop.
Perps flow is consolidating into fast onchain venues because that is where latency, settlement, and composability are getting good enough to matter. More autonomous flow is routing there every cycle.
Once autonomous systems are a meaningful share of flow and onchain perps is where they route, wallet-plus-API-key infrastructure stops being enough. Scope, revocation, attribution, and proof have to move into the protocol.
An account that holds funds and trades. Default caps, immediate activation, and no remote claim about the code behind it.
An exchange, fund, or operator states on-chain that this agent runs declared code against a declared mandate. The trust is explicit, and so is whose reputation is on the line.
A TEE quote binds the address to measured code and the declared mandate. Higher caps, remote verification, and the strongest execution claims live here.
A Tier 1 operator authors a small set of mandate templates parameterised by symbol, capital, and conformance window. Every strategy spun up under the operator inherits a template, gets its own mandate id, and is attested under the operator's on-chain identity.
When one agent breaches, the contagion factor lands on the rest of the book in the same block. The operator's reputation barely moves because the chain caught it. That is the mechanism a serious allocator pattern-matches on first.
Declare what the agent may do and what good performance means. Constraints are hard limits; objectives become a live conformance score.
The mandate lands on-chain. Tier 0 activates immediately; Tier 1 and Tier 2 activate when the attestation lands. Then the SDK mints one mandate-bound session key and returns it only in-process.
The agent runs with one session key for one mandate. If it exceeds scope, the chain refuses the intent; if behaviour drifts, caps tighten and events fire.
At v1 launch, gas is denominated in USDC and no token is required to trade, settle, or run an agent. Agents operate in dollars from day one.
If a native token ships later, the distribution follows the $HYPE model in spirit and is more specific than HYPE was about how that gets enforced. No VC allocation, no insider rounds, no supply sold to private investors ahead of launch. Distribution is points-to-claim against on-chain activity over a measurement window declared before the window begins, weighted to favour primitive layer adoption over raw venue volume.
Any supply retained for protocol purposes — insurance fund, buybacks, treasury — is published as a fixed allocation table before TGE, with treasury draws rate-limited to at most 1% of total supply per quarter and a public attestation of every draw. Allocations not used in their first two years burn by default.
Create the protocol account, link it to your Rabby address, then queue a deterministic faucet grant through consensus. The local bridge mutation shortcuts remain disabled on public validators.
kombat_faucetFundAccount waits for the faucet grant to commit before showing the funded balances.
& starts with native order-book perps, Mahi-Mahi consensus measured at ~98k TPS sustained, sub-second finality, EVM execution, and USDC-denominated gas. The deeper point is simpler: other venues give agents access; & gives them authority the protocol can bound, revoke, and verify, on a substrate fast enough that the rest of the design is implementable on top.
Prior art: the venue layer follows the architecture pioneered by Hyperliquid (native CLOB outside the EVM, account abstraction at the protocol layer, USDC gas, deterministic matching). The consensus layer is Mahi-Mahi, designed by Sonnino, Babel, Danezis, and the Mysten Labs research group, which itself descends from the DAG-based BFT lineage of Narwhal, Bullshark, and Mysticeti.