[RFC-1] Time Management in ArbitrumDAO Governance

Request For Comments: Time Management in ArbitrumDAO Governance


On April 2, the governance of Arbitrum submitted its first proposal for discussion. Since then, the forum has received nearly 40 proposals covering various topics and motivations. Although most of these discussions have been managed orderly, an increase in the daily volume of proposals could lead to the DAO’s disorganization.

According to the Arbitrum DAO constitution, a constitutional Arbitrum Improvement Proposal (AIP) requires approximately 37 days to be implemented, while a non-constitutional AIP requires around 27 days. In short, although the lifecycle of a proposal is well defined, the overall governance organization needs greater clarity.

Towards a More Efficient Organization

Bearing these challenges in mind and intending to optimize governance in ArbitrumDAO, we propose to discuss the implementation of seasons or defined periods.

We aim to establish periods of structured activity within the DAO, allowing a more systematic measurement of metrics related to proposals, discussions, and delegates in the forum. To facilitate this, we urge forum members to share their ideas to determine the appropriate season duration or proposal period in Arbitrum DAO.

This measure doesn’t require a constitutional amendment, as it could be an organizational layer implemented over the current system. Below, we present a first draft of a proposal to discuss with the community.

Improvement Proposal (Draft)

To optimize timings and organization, we propose that Phase 1 begins on the first Monday of each month, as shown in the following chart:

The central idea is that all proposals published in the forum can also be posted in Snapshot (by an address with a weighted vote of 0.01%), all on the first Monday of each month. This way, at the end of the month, we will have the results of all the voted proposals. This simple change minimizes the randomness of the proposals and allows delegates to have a more organized calendar.

Furthermore, proponents can seek community feedback before the voting cycle begins. Proposals published before the first Monday of each month should carry the [RFC] tag. If a proponent publishes their proposal in the forum mid-month, they can foresee that it will be included on the first Monday of the following month, and delegates know that during that first week, they will have to vote. In this way, we maintain an orderly calendar for all ArbitrumDAO.


We consider it necessary to establish the basic infrastructure of ArbitrumDAO. Therefore, we propose an improvement in the scheduling of proposals.

Next Steps

This RFC aims to gather feedback and opinions from the community. We appreciate comments, suggestions, and possible improvements that may arise from this proposal. In case of positive consensus and relevant adjustment suggestions, we commit to presenting a more refined and complete version of the proposal in the forum.

In addition, we invite community members to share their ideas, experiences, and knowledge related to implementing seasons or proposal periods in other DAOs or similar systems. This exchange of information can further enrich our proposal and help find the best solution to strengthen Arbitrum’s governance.

Our goal is to foster more efficient, transparent, and participatory governance. Implementing an organized proposal structure can be a significant step towards this goal, and we appreciate the collaboration of all community members in this continuous improvement process.

Check the other RFCs here.


Starting the work week on Monday is logical, but don’t you think the point of decentralization is to have multiple approaches to unification? I mean, yes, decentralization does not eliminate unification, but is it necessary to regulate the process of proposals and their consideration so rigidly? These questions are not tricky, I just want to understand the motivation, because so far I have seen only one explanation: it will simplify the work of the DAO. Yes, but at the same time it will make the work of the DAO less “alive”.


Hi @menaskop!

Our goal is not to diminish the dynamism of the DAO, but to establish a calendar with specific dates for voting. With this approach, we aim to offer delegates predictability, allowing them to organize their time more efficiently and ensure their commitment during the Arbitrum DAO votes. To illustrate my point, let’s review how the latest votes were conducted:

  • Arbitrum DAO Grants - Delegated Domain Allocation by Questbook: From Thursday, June 29th to Thursday, July 6th
  • [Non-Constitutional] Fund the Arbitrum Grants Framework Proposal Milestone 1: From Thursday, July 6th to Thursday, July 13th.
  • Accelerating Arbitrum - leveraging Camelot as an ecosystem hub to support native builders: From Friday, July 14th to Friday, July 21st.
  • Proposal: Update Security Council Election Start Date to Ensure Time for Security Audit: From Friday, July 21st to Friday, July 28th.

Although currently, the votes are held consecutively, as the number of proposals increases, it’s likely that the start dates for snapshot votes become more unpredictable, and the same could happen with the tally.

At this stage, we are open to feedback and suggestions. One option could be to start the votes twice a month, such as the first Monday of the first and third week of the month.


Yeah, I get the message. Thank you for your detailed response. I will think, like other DAO members, I hope.