LI.FI Documentation
LI.FI WebsiteAPI ReferenceHelp / FAQ / Create support ticketRequest API Key
  • 🏡Getting Started
    • ❓What is LI.FI
    • 🌟Why LI.FI?
    • 🆚LI.FI vs Aggregators/DEXs/Bridges
    • 📖LI.FI Terminology
    • ❓FAQ
    • 💡Use Cases
      • Mobile/Gaming Wallets
    • 🏹LI.FI vs. Other Aggregators
    • 🤝Partnership
    • 🌐Powered by LI.FI
  • 🔐Security First
  • ✅List: Chains, Bridges, DEX Aggregators, Solvers
  • 💲Monetization / Take Fees
  • 🔎Transaction Explorer
  • 🔏Rate Limits & API Key
  • How to get integrated by LI.FI?
    • For Bridges
    • For DEXs/Aggregators/Solvers
  • 🆘Technical FAQ
  • LI.FI PRODUCTS
    • Glacis
    • LI.FI Solver
    • LI.FI Intents System
  • LI.FI API
    • ⚙️LI.FI API
      • Transferring Tokens (Example)
      • Requesting supported Chains
      • Requesting all supported Tools
      • Requesting all known Tokens
      • Getting Token Information
      • Getting all possible Connections
      • Requesting a Quote
        • Token Transfer
        • Optimizing quote response timing
        • Cross-Chain Contract Calls
        • Possible Tool Errors
        • Testing your integration
      • Status of a Transaction
      • Requesting Analytics Data
    • ⚔️TX-Batching aka "Zaps"
    • 🏄Solana
      • Request examples
    • 🪙Bitcoin
      • Request examples
    • ⛽LI.Fuel
  • Integrate LI.FI SDK
    • 🚀LI.FI SDK Overview
    • 📦Install LI.FI SDK
    • ⚙️Configure SDK
    • 🪐Configure SDK Providers
    • 📜Request Routes/Quotes
    • 🎯Execute Routes/Quotes
    • ⛓️Chains and Tools
    • 💰Token Management
    • 🕵️Testing Integration
    • 🚗Migrate from v2 to v3
  • INTEGRATE LI.FI WIDGET
    • 🧩LI.FI Widget Overview
    • 📦Install Widget
    • 🎮Select Widget Variants
    • ⚙️Configure Widget
    • 🎨Customize Widget
    • ⚡Widget Events
    • 👛Wallet Management
    • 🌍Internationalization
    • ⚛️Compatibility with Next.js, Remix, Nuxt, etc.
    • 🛣️React Router Compatibility
    • 📖Widget API Reference
    • 🚗Migrate from v2 to v3
  • Smart Contracts
    • Overview
    • Deployments/Contract Addresses
    • Audits
  • Support & Misc.
    • API Status
    • Technical Help Desk & FAQ
    • Create a Partner Ticket
    • Discord Support
    • Telegram Support
    • Twitter
    • Github
    • Licenses
Powered by GitBook
LogoLogo

Connect with us

  • Github
  • Twitter
  • Discord
  • LinkedIn

More Information

  • Help Desk / FAQ
  • API Reference
  • Website
On this page
  • LI.FI Intents System
  • Why Intents?
  • Core Principles
  • Key Features
  • LI.FI Intents System as the Settlement Layer
  • LI.FI Solver & Glacis Integration
  • Use Cases

Was this helpful?

Export as PDF
  1. LI.FI PRODUCTS

LI.FI Intents System

Coming Soon

LI.FI Intents System

The LI.FI Intents System is a permissionless, modular intents protocol powering next-generation cross-chain execution. It transforms LI.FI from a pure liquidity aggregator into a hybrid system that combines aggregation with a competitive solver marketplace — delivering the best price execution at scale.

Why Intents?

As the crypto ecosystem fragments across hundreds of chains and virtual machines, routing liquidity efficiently becomes increasingly complex. Intents provide a way to express desired outcomes rather than imperative instructions, enabling solvers (third-party executors) to compete in fulfilling them.

The LI.FI Intents System abstracts complexity from users and developers by:

  • Outsourcing execution to permissionless solvers

  • Supporting gasless transactions

  • Enabling chain abstraction through generalized, trust-minimized execution

  • Ensuring fast finality across VMs and ecosystems


Core Principles

The LI.FI Intents System is built around four core architectural principles:

  • Extensible: Works across all VMs and is easy to deploy to new chains.

  • Modular: Every component (e.g., solver, oracle, verification system) is pluggable and upgradable.

  • Permissionless: Anyone can participate as a solver or verifier. No gatekeepers.

  • Trust-minimized: Trust is anchored in the verification system — not in individual solvers.


Key Features

🔁 Competitive Execution

Solvers compete in an open marketplace for LI.FI’s orderflow, tapping into a wide range of liquidity:

  • On-chain DEXs

  • Off-chain sources (e.g., CEXs, OTC desks)

  • Native inventory

💸 Gasless Transactions

Users can pay gas in their input tokens, removing the burden of managing gas tokens on multiple chains.

🧠 Solver-Aware Aggregation

The system enhances traditional aggregation by including solver quotes alongside AMMs and bridges, always selecting the most cost-effective path.

⚡ Rapid Settlement

Solvers are reimbursed within ~30 minutes on average, reducing capital inefficiency and improving order flow reliability.


LI.FI Intents System as the Settlement Layer

The LI.FI Intents System also acts as a generic settlement layer for intents in resource-locked environments (e.g., smart accounts, abstracted wallets). It is compatible with any verification mechanism, including:

  • ZK/storage proofs

  • Interop protocols

  • Off-chain signature servers


LI.FI Solver & Glacis Integration

The Intents System works alongside other components of the LI.FI 2.0 stack:

  • LI.FI Solver: An in-house enterprise solver and fast-bridge for instant chain support and bootstrapping new routes.

  • Glacis: Aggregates interop token standards like OFT, NTT, and CCT to support mint/burn-based token bridging and slippage-free routes.

These tools help solvers rebalance capital efficiently and extend the network’s liquidity coverage.


Use Cases

  • Cross-chain swaps with optimal pricing

  • Gasless onboarding for new users

  • Chain abstraction through smart intent fulfillment

  • Intent-based dApps using generalized execution logic


Last updated 21 days ago

Was this helpful?