Setting up a reduced bonding pool
Solvers that are currently vouched under the CoW DAO Bonding pool may decide to set up a reduced bonding pool according to CIP-44, where the main benefit is that then they can fully control their calldata and the onchain submission process. Note that the interested solver team first needs to coordinate with the core team, that is currently managing the CoW DAO bonding pool, and the core team maintains the right to reject such a reduced pool setup. Assuming that the core team approves the creation of a reduced bonding pool, the first step for setting up a reduced bonding pool is to deploy a Gnosis safe on Mainnet that has only one signer (the CoW DAO Solver Payouts safe, that is, eth:0xA03be496e67Ec29bC62F01a428683D7F9c204930). After this is done and has been confirmed by the CoW DAO team, the solver needs to deposit 100,000 in (yield-bearing) stable coins or ETH, and 1,000,000 COW tokens. We stress that the reduced bonding pool setup is just an arrangement within the CoW DAO bonding pool; meaning that a solver with a reduced bonding pool is still formally vouched for under the CoW DAO bonding pool.How to join a bonding pool
This is done by vouching for a solver’s submission address and rewards address with the bonding pool address. This is done by calling theVouch method on the VouchRegister contract using the address that created the bonding pool.
Vouching contracts:
The Vouch method receives a list as an argument and can vouch for multiple submission addresses in a single transaction. The transaction must contain: the submission address for the solver, the bonding pool that is vouching for the solver, and the rewards address that the solver would like to use to receive their rewards.
How to leave a bonding pool
Leaving a bonding pool involves the same process as joining a bonding pool, except that the owner of the bonding pool will call theinvalidateVouching method instead with the solver’s submission address and the bonding pool that vouched for the solver as arguments.