Breaking down the Router’s Cross-chain Intent Framework (CCIF) Architecture
Part One: Intent Adapters, the execution players!
In our past blogs, we have covered the issue of the complex Web3 journey and the need for a streamlined approach to increase user adoption. We also discussed existing intent-based solutions like Anoma and SUAVE and what sets Router’s CCIF apart.
Our intent framework introduces a versatile intent layer that can work seamlessly on top of the application layer of any blockchain network. This offers developers the tools to build user-focused applications on well-known L1 and L2 platforms. Router’s CCIF also simplifies the user experience in the DeFi space, enabling complex cross-chain operations to be performed effortlessly with just a few clicks.
And now that the Whitepaper of the same is already out, it’s time for us to understand the framework in detail. The framework is primarily composed of three components -
- Intent Adapters
- Adapter Registry Module (ARM)
- Intent Solvers
We will be covering the first component, the Intent Adapters, in this blog. We will try to simplify this concept, making it accessible and understandable to everyone. After all, the framework is designed to be inclusive and innovative.
A little introduction to what the framework supports as of now!
In the current version, the Router CCIF supports the actualisation of semi-deterministic and deterministic user intents.
- Semi-deterministic Intents: The final result is known, but how it’s achieved varies. For instance, if you want to convert 100 USDC to stETH using a specific process, the CCIF ensures you get stETH, but the specific route (like which exchange or bridge is used) isn’t fixed.
- Deterministic Intents: Both the process and outcome are precisely defined. For example, if you want to move USDC from Polygon to Ethereum, swap it for ETH using a particular service, and then stake it, every step of this process is pre-planned and executed as specified.
So, what are Intent Adapters?
In simple terms, Intent Adapters are smart contracts responsible for executing blockchain actions like swapping, bridging, or staking. Let’s use an analogy to go deeper into it!
What would you do if you wanted to escape from the buzzing city of New York to live a slow life in a place like Da Nang, Vietnam? You would probably take connecting flights and public transport like trains, buses, or cabs to reach finally.
Drawing parallels with our intent frameworks, these flights, trains, buses, and cabs are like Intent Adapters, each responsible for taking you from an arbitrary place A to an arbitrary place B. And when these adapters work in tandem, they take you to your final destination.
Intent Adapters abstract complex actions and enable fluid interactions, thereby serving as building blocks for constructing workflows that are both intuitive and efficient.
Intent Adapters help devs and users by making DeFi simple and uncluttered.
By breaking down complex tasks into smaller, manageable parts, developers can concentrate on creating specific adapters for unique features of their dApps. At the same time, they can use general adapters for more common tasks.
This method cuts down on repetitive work, encourages the reuse of existing components, and speeds up the launch of new services and features.
For users, this translates to a smoother and more intuitive experience.
And there’s a bonus: because it’s easier for developers to use these adapters, more of them can build cool things in the blockchain world. This means more cool dApps for users to explore and a richer, more diverse blockchain world for everyone.
Intent Adapter classifications: Stateless and Stateful!
Think of Stateless Adapters as one-time helpers. They’re like a taxi driver who takes you from point A to B without needing to know your travel history. These adapters do tasks on the blockchain that don’t require remembering anything about the user’s past actions.
On the other hand, Stateful Adapters keep track of your preferences and history. They remember user-specific details and use this information to manage more complex tasks. In essence, they manage ongoing, cumulative actions on the blockchain, remembering your previous interactions and using that information for future operations.
For example, they’re like managing your investment in a farming project: they help you put your assets into a pool, and there’s no proof given for the same; they maintain data to calculate the share of the rewards.
In the next, we will cover the different Intent Adapter Components.
Intent Adapter Components: Head Registry, Tail Registry, Inbound Asset Registry, Inbound Asset Registry, and Fee Handler Module
Let’s use your New York to Da Nang, Vietnam, via Dubai analogy to explain the components of Intent Adapters in a fun and understandable way.
- Head Registry–governing the initiation of the Adapter.
The Head Registry represents the list of origin points that an airline or service can handle. For example, if we consider an airline like Emirates operating the first leg of our journey, its Head Registry includes New York City, - Tail Registry–dictating the potential succeeding actions:
The Tail Registry is akin to the list of destinations that the airline can reach. In our journey example, Emirates would have Dubai (layover) in its Tail Registry, signifying that it can complete its service in Dubai.
As the next adapter in the journey, this airline takes over in Dubai (which is in its Head Registry) and completes the journey in Hanoi (in its Tail Registry).
Let’s see this entire process with the help of Sketch -
- Inbound Asset Registry–keeping track of all acceptable assets:
Imagine this as customs at each stopover, checking what you’re bringing into the country. It makes sure that the adapter only accepts specific types of assets (‘luggage’) that are allowed or planned for in the journey. - Outbound Asset Registry–managing assets allowed to output:
This is like the security check or baggage check at the airport. It controls what types of assets (‘bags’) the adapter can send out, ensuring that what goes out is consistent and as expected. - Fee Handler Module–managing the fee for the adapter:
Think of this as all the fees and charges you pay along the way. This module manages all the costs associated with using the adapter. It’s like making sure you pay the right amounts for tickets, transfers, and other services, keeping the financial aspect of your journey clear and fair.
So, in summary, travelling from New York to Da Nang, Vietnam, with various transport modes is akin to executing actions with different Intent Adapters. Each component of the adapter ensures your ‘travel’ (or transaction) is smooth, secure, and goes exactly as planned!
A recent article–Breaking down Intents, by Bankles, talks about Router Protocol’s Cross-Chain Intent Framework (CCIF) and its Intent Adapters, highlighting their significance in the blockchain and DeFi space.
Read the whitepaper for further details of the framework here: https://www.routerprotocol.com/router-ccif-whitepaper.pdf
Explore. Engage. Empower!
Website | Twitter | Telegram | Discord | Reddit | Youtube | Instagram
