Comet Configurator

To upgrade a Comet V3 proxy, deploy a new implementation using the factory, then execute the upgrade through the configurator after the required timelock period expires. This preserves proxy state while applying the new logic.

The Comet V3 configurator handles governance workflows by allowing governors or market admins to initialize proxies, set configurations, deploy implementations, and manage assets through explicit role-based permissions enforced per proxy.

Setting a new configuration for a Comet proxy involves using the configurator to apply per-proxy settings via governance actions. Immutable parameters are enforced, while configurable assets and parameters are updated based on admin permissions.

Yes, you can manage assets for a Comet V3 deployment using the configurator. It provides controlled asset management through explicit role-based permissions, ensuring governors or market admins can only modify permitted configurations.

A Comet V3 upgrade requires a timelock to enforce controlled governance and upgrade paths. This delay ensures that configuration changes and proxy upgrades are scheduled transparently, preventing unauthorized or immediate modifications to the protocol.

Deploying and upgrading Comet V3 configurations requires explicit role-based permissions, specifically governor or market admin rights. These roles are necessary to initialize governance, deploy implementations with the factory, and execute proxy upgrades.