StripChain is an innovative blockchain network that leverages an intent-based architecture that removes the complexity of cross-chain operations. In this technical article, we learn how to create solvers for the StripChain network as we call them StripSolvers. These specialized middleware components are the backbone of StripChain’s ability to turn user intents into actual blockchain transactions across multiple networks. Rather than requiring users to understand the intricacies of different blockchain protocols, gas mechanisms, or contract interactions, StripSolvers handle all the complexity behind the scenes, allowing developers to focus on creating seamless cross-chain experiences. Whether you’re looking to monetize your blockchain expertise, extend your existing protocol’s reach, or contribute to the growing ecosystem of interoperable services, building a StripSolver offers an exciting opportunity to shape the future of blockchain interoperability.
A StripSolver is a specialized service in the StripChain ecosystem that fulfills user intents. Think of it as a middleware that sits between the user’s high-level intent (“I want to swap Token A for Token B”) and the low-level blockchain operations needed to make it happen.
Unlike traditional blockchain development like Ethereum, Solana, etc where users need to know exact contract addresses, gas parameters, and transaction formats, StripChain allows users to simply express what they want to accomplish. StripSolvers then handle all the complex details of executing these operations across various blockchains.
Building a StripSolver offers multiple advantages:
A StripSolver operates within a clear protocol defined by StripChain. When a user submits an intent to StripVM (the unified execution layer), the intent is routed to the appropriate solver based on the operation type.
Let’s break down the flow:
The key innovation here is that solvers can specialize in specific operations while maintaining a standardized interface with StripVM.
Every StripSolver must implement four essential API endpoints that work together to process operations:
POST /construct?operationIndex=<operation_index>
The construct phase is where your solver analyzes the intent and determines the best execution strategy. For example, a DEX aggregator solver would find the optimal route for a token swap across various liquidity sources.
Your solver needs to return data that will be signed by the user:
{ "dataToSign": "0x7a69f0..."}
POST /solve?operationIndex=<operation_index>&signature=<signature>
Once the user signs the data, this endpoint is called to execute the actual blockchain transaction. Your solver broadcasts the transaction and returns a result identifier (usually a transaction hash):
{ "result": "0x8fd92c..."}
POST /status?operationIndex=<operation_index>
StripVM calls this endpoint regularly to check if the operation is complete. Your solver must respond with one of three statuses:
{ "status": "pending|success|failure"}
POST /output?operationIndex=<operation_index>
Once the operation succeeds, this endpoint is called to retrieve the output data that might be needed for subsequent operations:
{ "output": "..."}
Let’s look at some potential real-world solvers:
This solver finds the best swap routes across multiple DEXes to optimize token swaps.
Specializes in cross-chain asset transfers, finding the most efficient bridging path.
Manages deposits, withdrawals, and borrowing operations across various lending platforms.
Handles NFT purchases, listings, and transfers across multiple marketplaces.
StripSolvers are the execution engines that make cross-chain interoperability possible in StripChain. By building specialized solvers, developers can make their own applications interoperable and interconnected to other ecosystems through the help of stripchain. This is part A of the 2 part series of how to build your own StripSolver. StripChain is in private testnet and will begin onboarding new solvers soon to its network.
Follow us on Twitter to know when Stripchain will be in your country
