Retired: Christopher.conforti.eth

[glenn]

Essentially, to give the community time to review the proposal and provide feedback. FYI, this is part of our guidelines:

@mbr

Mandatory Community Review Time

Before the proposal can be moved to Snapshot for voting, the proposal must be available for review by the community for at least 2 days; however, 3 days is standard. Therefore, the proposal should include a planned time and date for the vote to begin, and cannot be sooner than 2 days from the time of its publication. This is mandated by DAO policy, introduced by BIP3 :

BIP documentation must be available with sufficient time for consideration by a reasonable and intelligent person. Time sufficiency is commensurate with the complexity of proposal. Minor adjustments to the protocol parameters, required for maintaining the health of the system, are prioritized over time for community deliberation. Similarly, urgent matters requiring immediate action can expedite the sufficient time requirement. Any other proposal that is not of imminent importance to the continuity of the project is not exempted. Low-to-moderate levels of complexity must allow 2-3 days for community engagement before voting commences; moderate-to-high levels of complexity must allow 3-5 days for community engagement before voting commences.