Docs / Team powers
Safety
Team powers and commitments
Commitments from the team, its remaining powers, and what is still pending.
Commitments
- No owner and no admin function in the pool contract, and no upgradeable proxy.
- No pause on shrouds, private transfers or exits, ever: the contract has no pause function.
- No hidden team allocation; any team or seeded deposit is labeled.
- No promise of yield. Yield is whatever real fees produce, which can be nothing.
- No claim that deposits and withdrawals are hidden. They are public by nature.
Team powers after deployment
| Will be able to | Will not be able to |
|---|---|
| Choose the constructor settings before deployment | Alter a setting once deployed |
| Receive swept ETH fees at the fee address and swap them into $OARKEL (expected, not enforced) | Pause shrouds, transfers, exits or donations |
| Collect the team's portion of each creator fee | Move, freeze or redirect any note |
Not deployed yet
The contracts are written and tested, but nothing is deployed, so none of the above can be checked on chain today. Once it is, the deployments page will list each address, and anyone can run npm run verify-deployment to prove the bytecode matches this code.