PIP-65 - Enhancing Predictability in VeloraDAO Governance

Abstract

We propose a simple set of guidelines to make Snapshot votes in VeloraDAO more predictable and easier for delegates by creating a clear, regular voting schedule. By agreeing as a community to start all votes on Thursdays, extend the voting window to seven days, and pause new votes during the holiday break from December 24 to January 6, this approach delivers a consistent schedule without requiring formal Charter changes. If approved by Snapshot, these changes can take effect as early as June 19, 2025, at no additional cost to the DAO.

Goals & review

Over the past four years, VeloraDAO has completed 89 off-chain proposals and built a strong, incentivized delegate program. Delegates still operate within a five-day Snapshot window that sometimes overlaps the weekend, limiting the time available for thorough review and feedback. Our timestamp data (Velora voting period) show participation climbing from Monday through Thursday, peaking on Tuesday, then dropping roughly 40 percent over the weekend. We propose extending the voting window to seven days and having every window start on Thursday.This change keeps both the opening and closing of each vote within peak-engagement period, removes weekend deadlines entirely, and grants delegates a full week to evaluate proposals. It also creates a clear, predictable weekly cadence, inspired by ArbitrumDAO’s proven model.

*This voting data is from Jan 2025 - May 2025

Check out the full data: Velora voting period

---

Rationale

Means

Current Process and Proposed Adjustment The Proposal Improvement Process consists of five stages:

• Stages one, two, four and five remain unchanged.
• Stage three is revised as follows:
  • Snapshot drafts must be queued by Wednesday 23:59 UTC.
  • Voting opens automatically at 00:00 UTC on Thursday and closes at 23:59 UTC the following Thursday.

This adjustment delivers three practical benefits:

• Delegates enjoy a uniform seven‑day review period that always spans a complete working week.
• Weekend participation becomes optional, reducing demand on personal time.
• Authors who miss the queue deadline wait only seven days for the next window, easing pressure to rush unfinished work.

Key Factors Behind the Thursday Selection Behind the Thursday Selection

1. Delegate turnout is highest mid‑week with Tuesday recording the single largest share of voting interactions in the dataset. Weekend participation is correspondingly weak, averaging roughly forty per cent lower than weekday engagement.

2. Thursday openings ensure both the start and the finish of every vote land on weekdays when delegates are most responsive. art and the finish of every vote land on weekdays when delegates are most responsive.

3. The Monday‑to‑Wednesday gap between queuing and opening offers a seventy‑two‑hour preview period so delegates can skim the upcoming ballot in advance.

4. A Thursday rhythm already operates effectively in other large DAOs such as Arbitrum, providing a field‑tested model.

Holiday Break: December 24 – January 6

Each year, VeloraDAO will observe a winter holiday hiatus from December 24 through January 6. During this period, delegates are encouraged to rest and return refreshed for the new year. No new proposals should be posted to the forum or Snapshot, except for urgent security that demand immediate attention.

Emergency Proposals

Proposals addressing critical security vulnerabilities or urgent constitutional matters may bypass the above rules and proceed directly to Snapshot if time-sensitive, ensuring that the DAO can respond swiftly when necessary.

Reward & Refunds Distrubtion Proposals

Distribution proposals for rewards and refunds are likewise exempt, as they should be posted immediately after each epoch ends to ensure users receive their payouts without delay.This exemption therefore remains in the current version of the proposal.

Timeline

We propose a feedback period from May 28 to June 4, 2025, followed by a Snapshot vote.

The vote will offer options to

1. Adopt all three (changing window from 5 to 7 days, Thursday Voting and Holiday break)
2. Maintain a 5-day voting window starting Monday–Friday and include a holiday break
3. Adopt only Holiday break
4. Abstain
5. Against

Implementation Overview

Implementation requires only updates to forum documentation and the calendar.

Time of Implementation:

The proposal will be implemented immediately after its passing.

Budget

There are no additional financial costs associated with these changes.

Risk Assessment

Pros

• Easier planning: A consistent weekly schedule helps delegates and authors organize their time better.
• Less noise: Reduces random or rushed submissions, leading to higher-quality proposals.
• Weekend flexibility: Delegates aren’t expected to review or vote on weekends unless they choose to.

Cons

• Less flexibility: Authors need to work around a fixed schedule, which might slow things down in some cases.
• Can feel strict for newcomers: Those less familiar with the process might find the structure a bit limiting at first.
• May slow submission timing: If a proposal is ready late in the week, it might have to wait until the next cycle, slightly delaying momentum.