Proposal: PIP-65 - Enhancing Predictability in VeloraDAO Governance
Vote: ADOPT ONLY HOLIDAY BREAK
Rationale: We support and vote in favor only of establishing the Holiday break, as activity within the DAO significantly decreases between December 24 and January 6 due to Christmas and New Year celebrations. During this time, many people are either spending time with their families or traveling for the holidays, so we see value in formally recognizing this period as a break for the DAO, consistent with practices in other governances. If an urgent matter arises that requires prompt action even during this timeframe, the PEP mechanism remains in place and is explicitly exempt from this restriction.
But we are voting against the rest of the options, and below we explain our rationale:
- Extension of the voting period to 7 days: We do not support this change, as extending the current voting window by two days lacks solid justification. The DAO has never encountered issues related to voting duration — especially now, when participation levels have increased significantly. For this reason, we believe the current 5-day voting period is appropriate and sufficient for both tokenholders and delegates to cast their votes.
- Maintain a Monday–Friday voting window and implement a holiday break: We also disagree with the idea of setting a fixed day for submitting proposals to Snapshot:
- Initially, the previous PIP framework approved by PSP-IPΔ33 required proposals to go live on Thursdays. However, this rigid rule proved problematic and was more harmful than helpful. That’s why in our approved proposal in January 2025 ‘PIP Lifecycle Improvements’, we explicitly removed this requirement and allowed proposals to be submitted on any day of the week. We remain consistent with that decision, which was made by the DAO less than six months ago. We do not believe it is healthy to change this again and return to a system similar to the previous one six months after approval when there are no solid reasons to justify it.
- Establishing a fixed date for submitting proposals to snapshot generates a rigidity that may lead to undesired results, such as if a proposal is debated in the forum for the necessary time, ending the debate on a Monday or Tuesday for example, it will have to wait all week until next Monday to be submitted to snapshot, which generates an unjustified delay in a proposal that is ready to be voted on and prolongs the decision making process for several days more.
- We agree with other delegates that it’s preferable to avoid voting periods that fall over weekends, but we believe this can be encouraged through informal community consensus, not enforced as a rigid rule. Some proponents may have valid reasons for starting a vote on any given day, and we should retain that flexibility.