Router Intents
  • Router Intents
    • What is an Intent?
    • Why is Intent-driven DeFi a Requirement?
    • Intro to Router's CCIF
  • How to Create an Intent Adapter using Router's CCIF
  • How to Generate Calldata for Invoking an Intent Adapter
  • API Reference
    • StakeStone API Reference
    • StakeStone (X Layer) API Reference
    • Lido API Reference
    • Kim API Reference
    • SwapMode API Reference
    • Lynex API Reference
    • Scribe API Reference
    • Ring Exchange API Reference
    • xFai API Reference
    • BaseSwap API Reference
    • Thirdfy API Reference
    • Parifi API Reference
    • Wen API Reference
  • Chains Supported
  • Contract Addresses
    • Mainnet Contracts
    • Testnet Contracts
  • Audit Reports
  • Router CCIF Whitepaper
Powered by GitBook
On this page
  1. Router Intents

Why is Intent-driven DeFi a Requirement?

The intricate nature of blockchain interactions necessitates users to have a nuanced understanding of underlying protocols and procedures. This complexity is a deterrent to mainstream adoption. Furthermore, new developers often find it challenging to build applications due to the complexities involved. There is a dire need for a high-level abstraction to simplify user interactions and provide a conducive environment for developers to build applications seamlessly. To this end, the concept of intent-based DeFi abstracts the intricate technical procedures underpinning dApp interactions and focuses on achieving the user’s desired end result.

PreviousWhat is an Intent?NextIntro to Router's CCIF

Last updated 1 year ago