Proposals with structure
A proposal identifies a change and the policy under which it will be considered. Deposits and eligibility rules can limit frivolous or unauthorized submissions.
Sigil records governance proposals and stake-weighted votes, with policy-defined eligibility, timing, and thresholds.
A permission is a condition, not a blank cheque.
Governance makes proposed changes and participating votes visible in a shared record. Sigil separates that decision process from the specific release and activation work needed to make a change effective.
A proposal identifies a change and the policy under which it will be considered. Deposits and eligibility rules can limit frivolous or unauthorized submissions.
Votes are counted under the configured governance rules. Duplicate-vote checks preserve a coherent record of who participated.
Voting windows, quorum, and approval thresholds belong to the network’s governance policy. Applications can show the relevant conditions alongside the proposal.
Proposal and voting records persist across node restarts. Explorers and governance interfaces can read a common history rather than reconstructing decisions from chat.
Do not assume so. A proposal needs a supported execution and activation path. The current direct execute, cancel, and emergency transaction paths remain gated.
Eligibility and voting weight depend on the active network policy and the participant’s stake. Consult the selected network’s governance parameters before submitting.