System Lifecycle

The Multyr system progresses through a series of well-defined stages, from initial deployment to production operation.

Each stage is governed by on-chain controls and predefined constraints, ensuring that system behavior evolves in a controlled and auditable way.

This lifecycle describes how the system moves from testing to production, and how its security posture changes over time.

1. Deployment

A CoreVault instance is deployed via the VaultFactory.

Deployment initializes:

• the core vault contract
• module wiring
• initial configuration

This process is executed atomically, ensuring that no partially configured system is exposed.

2. Configuration

After deployment, the system is configured through governance-controlled actions.

This includes:

• registering strategies and adapters
• setting allocation parameters and constraints
• configuring buffer targets and operational limits
• assigning roles (governance, guardian, keeper, operator)

All configuration changes are subject to access control and timelock constraints.

3. Shadow Testing

Before accepting external user deposits at scale, the system enters a shadow testing phase.

During this phase:

• the full system runs on mainnet
• strategies interact with live DeFi protocols
• capital allocation and rebalancing logic are exercised
• oracle checks, guardrails, and safety mechanisms are validated

Exposure is limited or controlled, allowing the system to be validated under real market conditions.

4. Sealing

Before entering full production, the system may be sealed.

Sealing is a one-way operation that:

• disables upgrades to core vault logic
• locks fundamental accounting behavior
• preserves system invariants

After sealing:

• core logic becomes immutable
• upgrade paths are permanently disabled
• only predefined operational controls remain active

Sealing is performed prior to full production in order to reduce upgrade-related risk.

This design prioritizes immutability of core logic before user capital is exposed at scale.

5. Production

After sealing, the system transitions to production.

In production:

• deposits are open to users
• capital is actively allocated according to predefined rules
• rebalancing operates under defined constraints and guardrails
• monitoring systems track system health and behavior

The system operates with immutable core logic, while maintaining controlled operational flexibility through predefined mechanisms.

6. Emergency Controls

At any point during production, the system supports emergency actions.

Action	Effect	Scope
Pause	Halts deposits and/or withdrawals	System-wide
Degrade	Stops new capital allocation to a specific strategy	Per strategy
Recall	Withdraws capital from a specific strategy back to the vault	Per strategy

Emergency actions are:

• governed by dedicated roles (e.g. guardian)
• executable under predefined rules
• recorded on-chain

These mechanisms are designed to improve system responsiveness under abnormal conditions.

Lifecycle and Risk

Each stage of the system lifecycle introduces different risk considerations:

• early stages (deployment, testing) involve higher uncertainty
• shadow testing reduces unknowns through real-world validation
• sealed systems reduce upgrade risk but limit flexibility
• production introduces full exposure to market conditions

Users should consider the current lifecycle stage when evaluating system behavior and risk exposure.

Current Status

Multyr is currently deployed on mainnet with limited functionality, undergoing controlled validation.

This corresponds to the shadow testing phase of the system lifecycle.

As a result:

• not all features may be active
• system behavior is still being validated
• parameters and strategies may evolve