Skip to main content

Documentation Index

Fetch the complete documentation index at: https://eco.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

Programmable Transactions is in beta and available to Eco partners for early access. The protocol (Sauce) is functional and audited; the developer-facing interfaces (high-level languages, recipe libraries) are still landing. Contact us to integrate.
A Programmable Transaction is a single onchain transaction with embedded decision logic. It can read state from multiple contracts, pick between paths based on the result, and execute the optimal one — atomically, without deploying a contract. This turns “best execution” from a marketing claim into a runtime property: the transaction itself picks the best path at execution time, not at signing time.

​
What it enables

PatternToday (without programmable tx)With programmable tx
Multi-DEX best priceThree quote calls + one swap, prices drift between callsQuote three DEXes, decide, swap on the winner — one tx
Conditional executionOff-chain logic + manual triggering”Only swap if price < X” inline in the tx
Cross-protocol compositionCustom contract per integrationCompose any two contracts at tx-time
MEV-resistant routingDifficult; multi-tx leaks intentSingle atomic tx, no inter-tx window for front-running
AI agent executionAgent must deploy contracts or send many txsAgent emits one programmable tx

​
How Sauce works

Standard transaction:  user → contract A → contract B → done   (no decision-making)

Programmable tx:       user → orchestration layer (Sauce)
                              ├── reads contract A
                              ├── reads contract B
                              ├── reads contract C
                              ├── compares results
                              └── executes optimal path (A, B, or C)
The “orchestration layer” lives in the calldata itself. A magic header (0x5A00CE) signals that the transaction contains embedded operation bytecode — a Turing-complete sequence of opcodes that handles decision-making between calls. External contracts see normal calldata; they don’t know they’re part of an orchestrated transaction. Sauce ships 50+ opcodes covering data extraction, cross-call memory, control flow (if/else, loops), boolean logic, arithmetic, and crypto operations.

​
Use cases

WhoWhat they build
DEX aggregatorsReal best-price routing without separate quoter calls
Liquidation servicesAtomic check-and-repay across positions
Yield optimizersRead N vault APYs, switch position into the winner
AI agentsSingle-tx multi-step strategies, no contracts to deploy
MEV-resistant appsOne atomic tx eliminates the inter-tx front-running window

​
Status

CapabilityStatus
Sauce protocol (operation bytecode + multicall extension)GA, audited
High-level Sauce-DSL languageIn development
Recipe library for common patternsIn development
AI-powered tx generationFuture

Orchestration

How Programmable Transactions compose with Routes + Permit3.