The idea of setting a cap on the number of signers is interesting. However, it’s worth noting that the only anticipated expansion would occur if new service providers join to the DAO and express interest in taking on the role—while ensuring they are added in even numbers. Therefore, we don’t expect a significant increase in the number of signers.
Regarding this topic, we’re not proposing fixed-term mandates. Instead, the Top 3 Delegates will serve as signers as long as they continue to meet the established criteria: being among the top 3 in VP, maintaining active participation in votes and on the forum, and signing within the expected timeframe. And a quarterly review will be conducted only to replace any signer who no longer meets these requirements.
This is a very good idea regarding the multisig signers, and if the proposal is approved, we’ll consider opening a post to inform the community of the current multisig signers and keep it updated in case of any changes.
But as for those responsible for determining whether a proposal qualifies as a PEP, we don’t believe a similar post is necessary, since the mechanism already accounts for evaluating who the Top 5 Delegates are at the time such a proposal is submitted on the forum. Of course, if this mechanism is activated, it will be properly informed who are the Top 5 Delegates at that time who are in a position to approve or not if a proposal qualifies as a PEP, and what has been the sense of their vote.
Thanks to the @SEEDGov team for presenting a clear and well-structured proposal. The shift toward a more decentralized and streamlined multisig process is well aligned with the DAO’s goals, and it is encouraging to see strong community engagement around this topic. We would like to echo several important points raised by other delegates and also contribute a few additional suggestions to help strengthen the proposal, especially in terms of transparency, operational clarity, and resilience.
We agree with this point and would add that making the rotation process externally visible could further improve transparency. A public-facing rotation log, whether hosted on the forum, GitHub, or integrated into Den, would allow anyone in the DAO to see when a signer is added or removed, along with the reason and timeline. This adds accountability without increasing operational burden.
We fully support this and recommend documenting a Signer Responsibility Checklist that outlines basic expectations. This could include reviewing transaction simulations, checking metadata before signing, and notifying the group of any extended absence. While simple, this shared standard would help ensure consistency and onboarding readiness for new signers.
While we respect the current no-compensation model, we believe signing duties should be acknowledged as a governance function that could qualify for future inclusion in the Delegate Incentive Program. In addition, we suggest allocating a small budget to cover basic signer-related expenses, such as hardware wallets and gas fees. These costs may be minimal but they are necessary for fulfilling the role securely and consistently.
Beyond these points, we would like to offer a few additional suggestions for consideration:
It may be useful to publish a summary of multisig activity at the end of each epoch or quarter. This could include how many transactions were signed, any delays, and any signer changes. Even a brief summary helps promote transparency and allows the community to identify issues early.
We recommend establishing a lightweight signer policy that outlines security standards and operational expectations. As a reference, the Optimism Collective has published a Multisig Security Policy that covers areas such as signer setup, hardware wallet standards, and communication protocols. A simplified version tailored to Velora’s needs would help promote safe practices without introducing unnecessary complexity.
Finally, we suggest including a basic emergency fallback mechanism. In cases where the multisig is unresponsive due to signer unavailability or coordination failures, a Snapshot vote could be used to authorize time-sensitive transactions. This would ensure the DAO can continue operating even in exceptional circumstances.
Overall, the proposal is very strong. With a few additional safeguards and clarifications, it can serve as a robust and flexible foundation for managing Velora’s governance and treasury operations. Thank you again to the @SEEDGov team for leading this initiative and incorporating community feedback throughout the process.
Given the 7-day debate period for this proposal has concluded, the last comment is from a couple of days ago and a fruitful debate has taken place, during which we made a few editions to the original proposal, we communicate that, in accordance with the PIP Lifecycle approved by PIP-57, we are ending the debate stage and initiating the 2-day frozen period. After this period we will submit the proposal to snapshot.
As the proposal has been approved, we hereby initiate the process for selecting the signers of the multisig wallets, previously managed by the now-deprecated GovCo structure.
Five of the eight signers have already been designated in the approved proposal due to their roles in VeloraDAO: the Foundation and the four current service providers (Mimic, Laita, SEEDGov, and WakeUp Labs).
The remaining three members will be selected as the Top 3 Delegates, excluding us, according to the following approved criteria:
Active participation in voting and the forum: This includes not only consistency in Snapshot voting, but also their voting rationale providing in the forum and involvement in ongoing discussions, which together qualify a delegate as active.
As a result, the multisig will consist of 8 members and require 5 of 8 signatures (5/8) to approve and execute transactions. The designated signers are:
@citizen42, meeting all requirements with 17.747M VP
Regarding the Top 3 Delegate seats, as outlined in the proposal, the VP and active participation of all delegates will be reviewed again in three months (early October) to determine whether any replacements are needed. Any signer who resigns, shows disinterest, or fails to fulfill signing duties may be replaced earlier.
All designated signers are kindly requested to confirm their intent to join the multisig as a signers and provide the wallet address they will use for this responsibility.
SEEDGov hereby confirms its participation and provides the following wallet address: 0x1a20c5106c11de13FE62ddE12BAdf5A04605A4b7
Thank you @SEEDGov - we hereby confirm our intention to join the multisig as one of the signers via the following address: 0xb49f8b8613be240213c1827e2e576044ffec7948
