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

Was this helpful?

Export as PDF
  1. Getting Started

Use Cases

Seamless User-Onboarding from anywhere!

Without LI.FI: For users to start using a new dApp, they often need to go to DEX & bridge interfaces in order to get the right asset, which involves a lot of decision-making.

With LI.FI: Implemented in your dApp interface in any custom way, users can pick any asset on any chain and bridge, swap and move it on the spot, into the desired asset or vault on your dApp.

Cross-chain Swaps

Without LI.FI: DApps are offering asset swaps on one chain and are about loose users as they have to go to other bridges & DEXes.

With LI.FI: DApps can implement our SDK and offer cross-chain bridging & swaps whereby they can always use our "prefer" setting to prefer their own LPs/AMMs whenever possible to avoid losing revenue by doing so.

Cross-Chain Yield Farming Strategies

Without LI.FI: Yield aggregators are primarily acting within one ecosystem. Cross-chain strategies offer much higher yields and are widely untapped.

With LI.FI: Vault contracts keep track of yields across multiple chains, deposit their funds in the best way, and then find the most trustless and cheapest bridge with enough liquidity to deposit into the highest yield generating protocols.

Multi-Chain Money Markets

Without LI.FI: Users can't borrow on chain A without moving funds across chains first.

With LI.FI: DApps can communicate across chains and let users collateralize, borrow and repay their loans on different chains.

Last updated 8 months ago

Was this helpful?

🏡
💡