MandatePackage_Static
MandatePackage_Static is a reform mandate that installs a fully pre-configured bundle of mandates into a Powers organisation. Unlike MandatePackage, the complete MandateInitData for each mandate is defined at constructor time and stored in the contract — there is no dynamic generation at execution time.
Overview
Section titled “Overview”This mandate is the static counterpart to MandatePackage. It is deployed with a complete, fixed set of mandate configurations, adopted by a Powers organisation, and executed once to install the bundle. After installation it revokes itself.
It is useful when the full governance configuration is known at deploy time and no customisation is needed at execution.
Configuration
Section titled “Configuration”This mandate takes no configuration at adoption time. All mandate configurations are passed to the constructor at deployment as an array of MandateInitData structs.
Proposing an Action
Section titled “Proposing an Action”This mandate requires no input parameters. The caller simply executes it to trigger the bundle installation.
Execution Flow
Section titled “Execution Flow”-
Adoption
- Iterates through the stored
MandateInitDataarray. - Generates an
adoptMandatecall for each entry.
- Iterates through the stored
-
Self-Revocation
- Appends a final
revokeMandatecall targeting itself, removing the package from the Powers contract after use.
- Appends a final
Technical Specifications
Section titled “Technical Specifications”Functions
Section titled “Functions”handleRequest
Section titled “handleRequest”function handleRequest(...) public view override returns (...)- Returns the pre-configured adoption calls plus a final self-revocation call.
Current Deployments
Section titled “Current Deployments”| Chain ID | Chain Name | Address |
|---|---|---|