Multi-Phase Security Model

Critical operations in the Particle system follow a structured, delay-based lifecycle. This design adds transparency and response time, preventing instant execution and reducing the risk of malicious or accidental actions.

Lifecycle Stages

1

Request

• A designated role (e.g., Owner or Recovery) initiates an operation.

• Operation details are logged on-chain with a unique transaction ID.

2

Delay (Timelock)

• The request enters a mandatory holding period.

• Timelock duration is action-specific and enforced by the contract.

• During this period, the action cannot be executed.

3

Approve

• After the delay has elapsed, the Owner may finalize the operation.

• Early execution is disallowed unless using a meta-transaction flow, which requires an off-chain signature and a Broadcaster to relay.

Key Benefits

• Time to Detect: On-chain visibility gives observers a chance to notice unauthorized or unexpected actions.

• Chance to React: Pending operations can be reviewed and canceled before execution.

• Structured Governance: Aligns with enterprise and DAO-style workflows, encouraging process-based control.

Cancellation

• Any active request can be canceled by the Owner before execution.

• Canceled operations are permanently recorded and cannot be reused.

This multi-phase model enforces deliberate action and reduces the attack surface of autonomous contracts, promoting higher trust and resilience across the Particle system.