Open Intents Framework primary sources
Reviewed: 2026-05-10 UTC
Core protocol framing
- https://docs.openintents.xyz/
- Main documentation entrypoint.
- Used to confirm OIF’s high-level framing as a full-stack framework for permissionless cross-chain intents with contracts, solvers, and aggregators.
- https://raw.githubusercontent.com/BootNodeDev/intents-framework/main/README.md
- Canonical repository README for the contracts / framework repo.
- Used to confirm the project’s self-description as an open-source framework with ERC-7683 support, reference solver, and customizable stack components.
Contract architecture and settlement design
- https://docs.openintents.xyz/docs/smart-contracts/overview
- Most useful single page for OIF’s architecture.
- Used to confirm the InputSettler / OutputSettler / Oracle split, output-input separation, support for Resource Locks and escrow, multi-output-order ownership rules, and underwriting / purchasing support.
Integration and routing surfaces
- https://docs.openintents.xyz/docs/integration/overview
- Best source for aggregator-mediated flows and app-integration patterns.
- Used to confirm that integrators can use an aggregator, talk directly to a preferred solver, or run their own aggregator instance; also used for EIP-7930 address encoding, lock kinds, quote/order API shapes, and quote-integrity-check guidance.
Solver operation and implementation reality
- https://docs.openintents.xyz/docs/solvers/quickstart
- Used to confirm the solver setup path, local and testnet workflows, contract deployment steps, and current operational dependence on real infrastructure.
- https://raw.githubusercontent.com/openintentsframework/oif-solver/main/README.md
- Canonical solver repository README.
- Used to confirm the solver’s modular service breakdown, order-state lifecycle, alpha status, current EIP-7683 focus, and operational components such as discovery, pricing, delivery, settlement, Redis-backed config, and optional KMS signing.
Main takeaways from this pass
- OIF’s distinctive mechanism is not ERC-7683 alone, but the full stack around it: settler contracts, oracle/proof choice, solver operations, and optional aggregator routing.
- The most important control surfaces are which oracle path is accepted, which lock mechanism is used, who controls quote aggregation, and how solver admission or selection really happens in production.
- The first-solver-owns-the-order rule in multi-output flows is especially worth keeping mentally hot because it exposes hidden residual-control and completion-risk dynamics inside “best execution” rhetoric.
- OIF belongs in the active corpus because it gives a cleaner decomposition of the intents stack than many branded cross-chain products that flatten standards, solving, routing, and settlement into one label.