Who can change what
Some parts of Chop's contracts can be changed. This page lists every power that exists and who holds it.
Warning: The contracts are unaudited. Don't deposit money you can't afford to lose.
| Power | Held by | Limit |
|---|---|---|
| Upgrade the code behind existing logs and control the log factory | Upgrade-key holder | The same holder controls the log factory used for future logs. LockAdmin can move these powers to a multisig or remove them permanently. |
| Verify, hide or remove logs from the app list, add other admins, or change the factory used for creation | IndexManager owner | Affects listing and future creation. |
| Pause reward tokens, add reward tokens, or exempt addresses from the unwrap fee | RewardsWhitelist owner | Paused payouts wait until the token is unpaused. |
| Change slippage settings or rescue stray tokens from the helper | IndexUtils owner | Limited to the helper's settings and tokens it holds. |
| Change the treasury share (0%) or the $CHOP burn share (20%) | Nobody | Both are locked. The fee settings contract and its router have no owner. |
| $CHOP the team provides to seed new log pools | Team | Seeded positions are staked and earn farmer rewards. To fill before launch: lock length. |
What nobody can do#
- Send protocol fees to the team. Any fees routed to the admin address go to a burn address.