> ## Documentation Index
> Fetch the complete documentation index at: https://docs.perpsagent.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# On-chain execution

> Executing Perps Agent strategies fully on-chain.

Bybit is the first venue, but Perps Agent's exchange-abstraction layer also targets **fully on-chain perp DEXs**.

## Why add on-chain venues

* Wallets, not API keys.
* Self-custody all the way down — no centralized exchange in the loop.
* Settlement and the proof layer live on the same kind of infrastructure.

## How it fits the architecture

From the grid engine's perspective, an on-chain perp DEX is just another adapter behind the exchange-abstraction interface. The engine asks for:

* Order placement / cancellation
* Fill events
* Position and PnL state
* Risk-cap enforcement

The adapter implements those against whatever venue is plugged in — CEX REST/WebSocket today, on-chain RPC + contract calls tomorrow.

## What stays the same

* The AI loop and risk-adjusted objective.
* The commit → attest → recall lifecycle on Mantle.
* The Telegram UX.

## What changes

* Order placement goes through signed transactions instead of HTTP keys.
* Funding lives in a wallet instead of an exchange account.
* Fees, slippage models, and latency profiles are venue-specific and get re-tuned by the AI loop based on attested results.

<Note>
  Specific on-chain venues are planned alongside [Roadmap](/execution/roadmap).
</Note>