[#2] Temperature Checks Process and Requirements

Forum post: https://gov.0x.org/t/temperature-checks-process-and-requirements/1079

Goal of the vote

Establish policies and guidelines on Temperature Check Votes held on snapshot for 0x DAO. This is a second iteration after a first vote on this matter, removing one of the requirements (minimum addresses).

Scope

The purpose of snapshot proposals is to gauge community sentiment on serious topics under consideration for onchain governance votes that impact 0x protocol.

Temperature checks are non-binding. For example, while a temperature check might indicate community support to introduce a change in smart contracts, a team will have to submit a complete ZEIP vote to come into effect. The same applies to Treasury proposals, which always require an onchain-binding vote.

The domain upon which the community of ZRX holders has decision-making power includes:

• 0x protocol (smart contracts and their deployments)
• 0x Treasury
• ZRX Portal UI
• ZRX token

Posts regarding airdrops and frontend integrators (such as Matcha) do not meet these criteria and will be deleted.

Process and requirements

• Temperature checks can be initiated by any ZRX holder or delegate with a voting power of at least 10k (ten thousand) ZRX.
• A link to an existing discussion on gov.0x.org must be provided in the description of the vote.
• The vote is considered valid once it reaches a quorum of 1M (one million) ZRX with at least 50 addresses voting. The quorum is intended to be set on the winning option (not on the sum of votes on all options).
• A temperature check vote must last at least 5 days. In case of tighter deadlines, a 3 days (72 hours) duration could be accepted. Any proposal that does not meet the criteria will be either ignored or deleted from the space.

Do you support the proposed policies?