# CIP-2: Solver Rewards

**URL:** <https://forum.cow.fi/t/cip-2-solver-rewards/488>\
**Category:** Closed Proposals\
**Tags:** cip, proposal, successful\
**Created:** [February 22, 2022, 12:15am UTC](https://forum.cow.fi/t/cip-2-solver-rewards/488 "2022-02-22T00:15:23Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![bh2smith](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.cow.fi/bh2smith/32/1242_2.png) [@bh2smith](https://forum.cow.fi/u/bh2smith)\
**Post date:** [February 22, 2022, 8:50am UTC](https://forum.cow.fi/t/cip-2-solver-rewards/488/3 "2022-02-22T08:50:00Z")

</div>

I agree that the token list proposed may not be ideal. For example it contains `sEUR` which is very illiquid and thus “risky”. When it comes to narrowing down the tokens in the list, I think careful research should be done and possibly also having a fixed set of rules for a token to be included there. For example:

To be supported for internal balances the token must be:

1. **Sufficiently Paired** : exist within a liquidity source paired directly with a “base token” where base token is a very short fixed list of trusted tokens (say for example { `WETH`, `USDC`, `DAI`, `USDT`, `WBTC`, `GNO`, `CoW` }

2. **Sufficiently Deep** : have at least `T` total USD in a Liquidity source natively supported by the protocol.

3. **Sufficiently Supported** be in the intersection of at least `N` token lists from [tokenlist.org](https://tokenlist.org) (the list suggested by @netrunner.eth)

These are just a few ideas. Without having looked very closely, I can say that `sEUR` likely fails 2/3 of the above.

I might also suggest making the list somewhat dynamic - since some of these conditions above can change from one block to the next.

---

_[View the full topic](https://forum.cow.fi/t/cip-2-solver-rewards/488)._