Upgradeability & Modularity

The Particle CS system is built for long-term extensibility with a strong emphasis on upgrade-safe patterns and modular design.

Upgradeable Contracts

All core modules follow proxy-compatible patterns:

• Uses UUPS upgrade mechanism

• Upgrade operations must pass through the multi-phase approval process

• Owner (or Recovery) can initiate upgrades, but final approval is delayed

Upgrade Lifecycle

1. requestUpgrade(address newImpl) → Initiated by authorized role

2. Wait for delay (e.g., 24 hours)

3. approveUpgrade(txId) → New implementation is set

Modularity by Design

Each core feature is encapsulated as an independent module:

Modules

Module	Purpose
SecureOwnable	Ownership + secure upgrade flow
MultiPhaseSecureOperation	Delay + approval framework
GuardianAccountAbstraction	Smart account extensions + guardians

Benefits of Modularity

• Swap or disable features per contract

• Compose minimal viable deployments

• Enable focused audits and testing

Combining Modules

You can compose contracts with only the modules you need:

contract Vault is SecureOwnable, MultiPhaseSecureOperation {
  // add vault logic here
}

This architecture allows for both conservative security setups and lightweight custom deployments—ideal for prototyping in tools like SandBlox or deploying production-grade smart wallets.