# Optimized Solver Network

## Solvers on Symphony

Symphony's hybrid-permissionless execution network fosters incentivized competition for returning optimized execution paths. There are several key features of our execution network:

1. **Solver Compensation**
   * Solvers earn native token fees based on positions they create on behalf of Users
   * esCAD is rewarded to Solvers based on their staked tokens required for becoming a Solver
   * Collateral is securely locked via Proof-of-Lock to ensure Solvers can trustlessly receive payment
2. **DoS/Fraud Prevention**
   * Solvers are required to stake to access the intent-pool.  Solvers can stake RWAs enabling them to earn stable yield on their assets. This ensures that malicious parties do not spam the network with requests to create a DoS attack as they must be whitelisted via their staked position.
3. **MEV Prevention**
   * Staked positions to become a solver are at the risk of being slashed. This means that if Solvers act nefariously (i.e. Provide poorly optimized solutions to seek MEV, DoS attack the IPE, etc.) they can have their staked tokens slashed. This incentivizes Solvers to act in the best interest of Users and provide truly optimized execution paths.
4. **Support for Sharded Positions**
   * Liquidity is fragmented between protocols and chains which limits the size of leveraged positions that can be opened. In order to combat this, Solvers are able to analyze optimal solutions between different blockchain networks and protocols. In the case that the position is too large for a single protocol, our IPE is able to support sharded positions. This means that from a User’s perspective their trade is shown in one simple UI, but their trade is actually occurring on multiple platforms simultaneously.


---

# 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://cadenceprotocol.gitbook.io/cadence-protocol/symphony-full-docs-coming-soon/optimized-solver-network.md?ask=<question>
```

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.