Roadmap
This roadmap outlines the journey of Mimic Protocol from a developer-oriented release to a fully decentralized, incentive-driven automation network. Each phase is designed to gradually introduce key components, test their robustness, and improve the user experience before broadening participation and enabling economic incentives.
Phase 0 — Developer environment MVP
Goal
Establish a solid, developer-friendly foundation for Mimic Protocol. This initial phase focuses on delivering essential tooling and infrastructure so developers can experiment, build confidence, and shape the product through feedback. Minimal decentralization and no economic incentives will keep complexity low and foster rapid iteration.
Key deliverables
Lib & CLI
Provide a software development kit and a compiler toolchain that let developers write tasks in a high-level language, compile them to WASM, and easily integrate with Mimic’s logic.
Off-chain Registry
Host task definitions, manifests, and configurations will be stored in a private repository. This avoids prematurely introducing on-chain registries.
Off-chain Verifier
Implement a solid verification process for relayers off-chain, following the same scope and interface without relying on on-chain implementations for now.
Explorer App
A web-based explorer that lets developers monitor, debug, and visualize their tasks’ execution, inputs, and outputs in real-time.
Private Mimic Relayer
Initially, Mimic will run a single trusted relayer to handle task execution in a free-tier mode. This streamlines early development and iteration without complexity.
Trusted Mimic Oracle
Initially, Mimic will provide a single trusted oracle to handle task inputs without full decentralization in a free-tier mode. Developers can rely on these data feeds to test their tasks.
Private Solvers
Integrate the Axia module to handle intent execution with a whitelisted solvers set. No open competition at this stage.
Settler for Swap-Type Intents
Implement a baseline settler contract to finalize swap-related intents, ensuring a straightforward demo use case for automated operations.
Rationale
Phase 0 ensures developers can quickly see that Mimic’s technology works. By avoiding premature complexity (like on-chain registries or open participation), we can refine UX, improve tooling, and learn from feedback.
Phase 1 — Cross-chain swap intents
Goal
Build on the successes of Phase 0 by expanding Mimic’s features to support cross-chain operations and accommodate non-EVM environments. This broader functionality paves the way for increased adoption and demonstrates Mimic’s ability to handle more diverse and complex scenarios.
Key deliverables
Cross-Chain Swap-Type Intents
Extend the baseline settler contract to handle swaps across multiple chains. Developers can define cross-chain swap intents that lock assets on one chain and execute corresponding operations on another, showcasing Mimic’s multi-chain capabilities.
Support for Non-EVM Chains
Implement new security layers and private solver solution for non-EVM chains. This means expanding the off-chain processes, and ensuring oracles/relayers can interact seamlessly with different consensus rules, block times, or transaction formats.
Rationale
By offering cross-chain swap functionality and supporting diverse chain environments, Mimic becomes far more versatile. Teams can test advanced workflows and develop automation use cases that span multiple ecosystems—a critical step toward broader market adoption. This iterative approach also provides valuable insights into how Mimic’s architecture handles the additional complexity of multi-chain interactions, helping the team refine the system before opening it up to full decentralization and incentives.
Phase 2 — Decentralizing the solvers network
Goal
Expand from private to semi-open participation by introducing decentralized solvers. This lays the groundwork for competition, better pricing, and an early taste of open-network dynamics.
Key deliverables
KYC Process for Solvers
Implement a simple vetting process to ensure reliable solvers join the network, maintaining a controlled environment during the transition.
Solvers Queues API
Provide an interface for solvers to queue up, receive intents, and submit proposals to Axia.
Open Solvers Network
Gradually open solver participation beyond the private set. Solvers can compete for intents, improving efficiency and pricing while still operating in a partially controlled ecosystem.
Rationale
By introducing a competitive solver environment early, we’ll test assumptions about solver behavior, pricing mechanisms, and user satisfaction in a constrained scenario. Feedback here will guide the full decentralization and incentive design in later phases.
Phase 3 — Expanding the oracles network
Goal
Broaden data sourcing capabilities by onboarding more oracles while maintaining a controlled environment. Although still no direct incentives or penalties, adding diversity improves the resilience and reliability of data feeds.
Key deliverables
KYC Process for Oracles
Introduce a vetting process to ensure data quality. Onboard a small set (5-10) of reputable oracles to test how multiple data sources combine in consensus mechanisms.
Oracles Queues API
Allow oracles to register their data availability and respond to queries through a standardized API.
Open Oracles Network
Expand beyond the initial trusted oracle set. While still capped and vetted, this step gives us insight into how multiple oracles affect data accuracy, latency, and consensus.
Rationale
With multiple oracles in place, tasks can rely on more diverse data. This phase primes the network for a more fully decentralized data layer, and lets us analyze how oracle variety impacts tasks, consensus, and performance.
Phase 4 — Expanding the relayers network
Goal
Decentralize task execution by inviting external relayers. Until now, relayers were controlled or singular; this phase democratizes the execution environment, bringing it closer to the final vision.
Key deliverables
KYC Process for Relayers
Screen new relayers to ensure reliability and honesty. This maintains quality as we open the gates.
On-Chain Tasks Registry
Move from off-chain registries to an on-chain registry backed by smart contracts and IPFS, enabling trustless discovery and verification of tasks.
Verifier Contract
Move from off-chain to an on-chain verifier contract that allows proving correctness of executions. No rewards or penalties yet; just a way to submit and verify proofs.
Tasks Broadcast Mechanism
Provide a reliable, permissionless means for tasks to be discovered and claimed by any relayer.
Open Relayers Network
Allow multiple relayers to pick tasks, execute them, and submit proofs. This finalizes the primary infrastructure for a fully decentralized execution pipeline.
Rationale
Decentralizing relayers ensures no single point of failure and brings us closer to the true trustless environment. Testing this with a vetted set first allows adjustments before enabling rewards and penalties.
Phase 5 — Enabling economic incentives
Goal
Introduce a utility token, staking mechanisms, rewards, and penalties. This is the final piece that transforms the network from a controlled testing ground into a fully open, self-sustaining, and economically driven system.
Key deliverables
Utility Token & Staking Contracts
Introduce a governance and utility token that participants stake to provide security and signal reliability.
Governance Tooling
Empower the community to guide the protocol’s evolution, adjust parameters, and propose improvements.
Protocol Fees & Rewards
Enable fees for task execution, reward honest participants, and penalize malicious actors through slashing. This creates an incentive-aligned ecosystem where participants compete and collaborate for mutual benefit.
Fully Open Participation
Now anyone can become an oracle, relayer, or solver, backed by economic incentives that drive network health and performance.
Rationale
Bringing in token-based incentives and governance cements Mimic as a fully decentralized and economically sound protocol. Participants are now motivated to maintain high standards, and the protocol can scale autonomously.
Summary
Phase 0: Developer-focused MVP with minimal complexity.
Phase 1: Cross-chain intents.
Phase 2: Introduce decentralized solvers and competition.
Phase 3: Expand the oracles network while maintaining controlled environment.
Phase 4: Expand the relayer network preparing for full trustlessness.
Phase 5: Enable economic incentives and governance for a fully decentralized ecosystem.
By gradually rolling out features, ensuring quality and security at each step, and gathering feedback before expanding, Mimic Protocol sets the stage for a robust, trustless, and incentivized automation framework that evolves hand-in-hand with its community.
Last updated