Learn
Evergreen guides to how intent-based, MEV-protected trading works, written to answer the question in the title. For dated announcements and walkthroughs, see the blog.
Last updated:
How intent trading works
- What is an intent-based DEX aggregator?
Intents vs routers vs RFQ, what a solver is, and why batch auctions change the trader’s position.
- MEV-protected swaps, explained
What sandwich attacks exploit, which levers batch auctions remove, and the precise boundary of the protection.
- What is a sandwich attack?
A buy before your swap, a sell after it, and your slippage tolerance as the budget. What removes the preconditions.
- What is a solver?
The execution specialist chosen by auction, what it does with your order, and what happens when one fails.
- What is a coincidence of wants?
When two orders mirror each other they settle peer-to-peer: no pool, no LP fee, no price impact.
- Slippage vs a signed limit price
A tolerance pre-authorizes a worse price; a signed limit enforces a floor and returns anything better.
- What is surplus, and who keeps it?
Execution beyond your signed limit: where it comes from and the published per-chain rules for who keeps it.
- MEV blockers vs batch auctions
One defense hides the transaction, the other removes the attack surface. What each trusts, and why they compose.
For agent builders
- AI agent token swaps: the safe pattern
Bounded orders, receiver pinning, per-chain domain resolution, expiry, and the keyless MCP server.
- How should an AI agent hold custody?
A dedicated funded-per-mandate key, signer-enforced policy, on-chain enforcement, and what to log.
- What is an MCP server for trading?
How an assistant goes from talking about a trade to executing one, and what a keyless server never touches.
- Agent trading: API keys vs wallet signatures
Standing authority over custodied funds vs per-trade signatures over your own. Failure modes and revocation.
- What is EIP-712, and why do agents sign typed data?
Typed inspectable fields, the domain separator, and why the signature itself is the audit record.
Reference pages
- Fees and pricing
The canonical fee reference for every path and chain.
- Supported chains
The canonical chain list, with settlement mode per chain.
- Security
Custody model, audits, agent safety, disclosure.
More
The blog carries dated posts (chain launches, walkthroughs, comparisons), the docs carry the full protocol and API reference, and business.ophis.fi covers integrator terms.