Who can change what after launch. The short version: you manage the underlying vault, you choose who manages the premium, and we manage protocol-wide fees.
After launch, you have authority over:
You're not gated on any of these. You move when you decide to move.
We don't have authority over:
A few decisions at deploy time can never be reversed:
Everything else (premium rate, fee, fee recipient, who holds which role) can change over time.
| What | Address you should use |
|---|---|
| Curator (day-to-day vault management) | A Safe multisig you control |
| Premium lever (if you keep it) | The same Safe, or a timelock contract owned by that Safe if you want a built-in delay |
| Premium lever (if you hand it over) | The LayerCover protocol Safe (we set this automatically) |
| Performance fee recipient | The LayerCover protocol Safe (default) |
The curator app shows a one-time acknowledgement banner the first time you sign in. It reminds you that you're operating from a Safe. Confirm it before you sign your first deploy.
Curator key compromised. Pause deposits on the underlying vault from a sentinel address, transfer ownership to a fresh Safe, then resume.
Premium-lever key compromised. Premium can be set as high as 100% / yr by a malicious holder, which would heavily favour junior over senior. Mitigation: use a Safe with multiple signers, or put a timelock in front of the lever so there's a notice window for any change.
Lenders concerned about a single point of failure. Curators should run all critical roles from multisigs. If your strategy targets risk-averse senior lenders, this matters.