# Workflow of DAPPOS Network

The DAPPOS intent execution network operates through a structured workflow, consisting of three main phases: Counterparty matching, execution, and verification.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXchmQhJ-WzYSWS-oczKS-5DpEs6JQbhrbi0Vtp2tiFbY3VQL1Ra3_ZKVsX2FtHo9Fmt8ACfE4-oHU3b4g00KiZSywhY3M4ZSLbANVoMxb7P8O32LuizV8G4z6wgWVA-4551gkfBWWHfYKTeYdqwvtyAkO3w?key=iV_GlUt1Czad1rTvQUwgrA" alt=""><figcaption></figcaption></figure>

**Phase One: Counterparty Matching**

When a user defines their intent, they can query any matcher within the network. The matcher will return execution quotes from the connected service providers for the specified intent. Once the user selects the most optimal quote, the intent deal is finalized. The user then only needs to monitor the success of their task; if it fails, they will receive compensation.&#x20;

For convenience, DAPPOS has developed a series of intent task frameworks. When users interact with partner infrastructure or dApps of DAPPOS, their intents are automatically generated by the intent task frameworks. Users can then view quotes from various service providers within the dApp and select the most appealing option.&#x20;

**Phase Two: Execution**

After the intent deal is finalized, the service provider will receive C(what user provides for the intent), and take responsibility for fulfilling the X(what user wants in the intent).

DAPPOS Intent Execution Network does not care about how the service provider completes the intent task; it only cares about whether the result is successfully achieved. Unlike many other intent-related projects where intent solvers are limited to on-chain solutions, DAPPOS allows service providers to choose from a broader range of solutions. This flexibility may offer users better options.

**Phase Three: Verification**

Service providers can proactively report the completion of their tasks. If they do not, execution validators will verify the success of the intent after the specified time within the intent.

If the task is detected as failed, execution validators can issue a challenge to the network. All execution validators will then vote according to a Delegated Proof of Stake (DPOS) mechanism to reach a consensus. If the consensus determines that the intent task has failed, the service provider's collateral will be used to compensate the user and reward the challenger. If the consensus confirms that the intent task was successfully executed, the challenger will be penalized.

If the task is successful, which means that nobody issues any challenge about the success, the corresponding task value for the service provider will be released.&#x20;

Through these phases, DAPPOS ensures a seamless, efficient, and user-centric process for executing intents. The structured workflow not only simplifies user interactions but also maintains the network's integrity and reliability.

\
