# Participants in Intent Execution Network
Before diving into the detailed workflow of the DAPPOS intent execution network, it is essential to introduce the three primary participants within the network:
The service provider is the entity responsible for executing the user's intent. Service providers must stake collateral to take on tasks within the network, and the total value of the tasks they accept cannot exceed a certain proportion of their collateral. When a user's task is successfully completed and validated by the network, the reduction in the current total value of the service provider's tasks is acknowledged by other network participants, allowing the service provider to accept new tasks.
**Execution Validator**
Execution validators play a crucial role in verifying whether a user's intent has been successfully executed. These validators must stake a significant amount of tokens as collateral within the network. By continuously participating in verification tasks, execution validators earn token rewards. If they fail to provide timely validation results or if they submit incorrect validation outcomes, they face penalties. Their role is vital to maintaining the integrity and accuracy of the network's operations.
**Matcher**
Matchers are advanced execution validators with additional responsibilities. Besides verifying the execution results, matchers are also tasked with pairing and matching users with suitable service providers. This dual role requires matchers to stake even more assets within the network.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://dappos.gitbook.io/docs/dappos/overview-of-dappos/execution-layer/how-intent-execution-network-works/participants-in-intent-execution-network.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.