# Proposal Process All proposals in SZNS Collections move through a governance process with similar components. Under the hood, the Gnosis safesnap module allows for these communities to vote offchain and execute onchain. If you'd like more details on the proposal criteria see the Governance Rules. ## Proposal States ### State 0: Submission Token holders of a particular Collection are able to submit proposals via the "Proposals" button on the Collection Page. See [custom proposals](/collection-governance/arbitrary-contract-calls.md) or [standard proposals](/collection-governance/standard-proposals.md) for more information! ### State 1: Voting Active SZNS provides standard interfaces for various actions Collections need to perform to succeed. Each proposal type requires different inputs for the specific purpose. Proposals submitted to a Collection begin as either [Standard Proposals](/collection-governance/standard-proposals.md) or [Custom Proposals](/collection-governance/arbitrary-contract-calls.md). The subsequent verification and execution steps remain the same. ### State 2: Double-checking This process lets you verify results for on-chain execution using [reality.eth](https://reality.eth.link/app/). Step 1: Request execution of the transaction Step 2: Set the condition of the outcome and submit your bond Step 3: Wait for the oracle to verify which will take 1 week on Mainnet {% embed url="" %} ### State 3: Needs Execution Finally, proposals that pass the reality.eth process successfully allow anyone to execute the transactions to complete the proposal. This stage also allows the bond set in the double-checking state to be re-claimed by their owner. {% embed url="" %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.szns.io/collection-governance/proposal-process.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.