Proposal Lifecycle
Every protocol change follows a structured seven-day minimum process ensuring thorough review and community consensus. Only active P-Reps can create proposals, which must include clear descriptions, rationale, and implementation details. Proposals enter a two-day review period where the Security Council examines them for potential risks, vulnerabilities, or destabilizing factors. The Council may veto proposals that pose clear security threats, preventing malicious changes from proceeding.
Approved proposals advance to a three-day voting period where delegated BOUND determines outcomes. Passage requires both a simple majority and participation from at least two distinct P-Reps, ensuring broad support rather than concentrated power. Successful proposals enter a two-day timelock before execution, providing a final opportunity for security review. After this cooling-off period, changes execute automatically through smart contracts, completing the transparent governance process.
Last updated