I. Executive Summary II. Background of the ADPC III. Achievements & Progress IV. Key Learnings & Improvements from Phase I V. Phase II Mandate VI. Budget & Methodology VII. Methodology for Shortlisting Verticals for Phase II VIII. Transparency & Community Engagement IX. Checks & Balances X. Multi-Sig XI. ARB Conversion Strategy
The Arbitrum DAO Procurement Committee (”ADPC”), composed of Axis Advisory, Areta, and Daimon Legal, is coming to the end of its first phase on August 20, 2024. As such, this proposal aims to extend the ADPC’s tenure into Phase II for a 6-month period, which will commence on the date on which the Tally vote for this proposal is executed on-chain.
The ADPC’s pilot phase proceeded successfully, with significant outcomes to Arbitrum DAO and a range of key learnings for the committee. Creating a comprehensive procurement process from the ground up to ensure that Arbitrum is seen as a leader not only in the technical sphere but also within decentralized governance has been a great opportunity.
We laid the foundation for the ADPC to be an effective set-up bringing the benefits of well-structured procurement to Arbitrum DAO. Cost savings will result from the creation and use of procurement frameworks and marketplaces developed by the ADPC uniquely for Arbitrum DAO as well as the necessary legal and operational infrastructure and strategic sourcing methodology.
The ADPC's initial phase was conducted as a proof of concept demonstrating the capability of the team and the benefits arising from the strategic use of advanced sourcing methodology. The ADPC proposes to build on these successes into Phase II of the ADPC's engagement. In this Phase II, the ADPC, after careful alignment with key stakeholders in the DAO, proposes to work on all of the following work packages:
Vertical 1 will be focused on procuring RPC providers for projects building in the Arbitrum ecosystem. This decision is based on engagement with delegates and stakeholders as well as an understanding of the core services required by all projects looking to build in the Arbitrum ecosystem.
Vertical 2 will be focused on providing the procurement services for events identified within the DAO Events Strategy for 2025. This event strategy is prepared by the ADPC, Entropy Advisors and Disruption Joe pursuant to a separate proposal. Please note that the ADPC will not request any funding for its events services procurement in that separate proposal.
The scope within the 6-month term is to develop evaluation criteria, draft and publish the Approach to Market (RFP/tender), evaluate responses to Approach to Market and whitelist supplier/s. Contract negotiations with whitelisted suppliers are not in the scope as the counter-party may be the Arbitrum Foundation or third parties utilizing their own counsel, and the ADPC has no influence on those internal legal processes.
Further details on our process for arriving at these shortlisted verticals can be found below in the section on Methodology for Shortlisting Verticals for Phase II.
Work Package 2: Continued management of the Subsidy Fund for Security Services and, based on the success of the first cohort, publishing the proposal for an extension of the fund.
Work Package 3
Definition and creation of an Operational Expense (OpEx) budget for the Arbitrum DAO, to be custodied by the Multi-Signature Safe (MSS), and allocated towards the utilisation of service providers as whitelisted by the ADPC. This creates a utilisation rail for the DAO to be able to utilise the services of the whitelisted service providers procured by the ADPC. Without this in place, the DAO is unable to utilise these service providers without the full proposal process (Forum, Snapshot, On-Chain).
The ADPC will draft and propose the OpEx proposal to the DAO; further details, including the process and procedure for utilization of the OpEx budget by the DAO, will be outlined in this separate proposal to the DAO. This seperate proposal will contain multiple options for the size of the OpEx budget for the community to vote on.
Creating a Phase II Outcome Report, similar to the one we have published for Phase I, and submitting it to the DAO.
Continued alignment with key stakeholders in the DAO on the evolution of the Arbitrum DAO’s structure, and ensuring that the ADPC fits into any structure that is defined (e.g., OpCo).
Ad-hoc tasks, e.g., aligning and connecting whitelisted service providers with existing and incoming projects on Arbitrum, existing and incoming DAO proposals, etc.
The overall budget for the 6-month term will be USD 414,000 including OpEx, details on which can be found below in the Budget & Methodology section. The Funding Request from the on-chain vote will be 954,608 ARB based on the time weighted average ARB price of $0.5204/ARB as further outlined below. A buffer has been added so that, in the case of ARB depreciation, the ADPC multi-sig under the Multi-Sig Service (MSS) is still able to satisfy payments to the ADPC's members. Unutilized ARB will be returned to the Arbitrum DAO treasury.
The multi-sig requested to manage the funds is within the Multi-Sig Support Service (MSS) established by Entropy Advisors. The Multi-Sig that has been created by the MSS is the following address:
arb1:0x13d4Ff2A83fBCB8F5fc73cE66CF5928eD0943cB0
After receipt of the ARB, the ADPC will convert as much of the requested amount as is required to obtain 414,000 USDC and will return the unutilized ARB to the DAO treasury. This is intended to avoid fluctuations in ARB price and ensures that the ADPC avoids using the buffer as much as possible.
The ADPC will utilize a Protocol-Owned Execution strategy on Gauntlet's Aera solution to convert the program’s ARB into USDC for operational purposes. The Protocol-Owned Execution strategy utilizes off-chain logic to monitor on-chain liquidity and model the price impact of trading. The ADPC will use an Aera Vault, with Gauntlet as the guardian, to execute the conversion. Trade execution is scheduled and sized according to impact modelling and executed on Odos, or Bebop. Based on current market conditions, it would take approximately one week to trade out of 414K USD worth of ARB with minimal impact.
Once the ARB is converted into USDC, the Aera vault will utilize LlamaPay to stream the total payment due to the ADPC member wallet addresses over the course of the 6-month period (120k USDC per member, 360k USDC in total). The remainder of the converted funds (54k USDC) will remain in the MSS as the OpEx budget. This process will be coordinated with the MSS chairs and members.
Further details about the ARB conversion strategy and about Aera can be found below in the 'ARB Conversion Strategy' section below.
Note: The proposal includes the re-election of the current members of the ADPC. For any future extension terms of the ADPC, the process outlined in the original Tally vote will stand unless automatic renewal of the then-current members is proposed. Of course, this will be subject to the potential OpCo that gets formed and any implications that may have on the structure of the ADPC.
We would like to acknowledge the consistent participation and deep input from the Arbitrum community, delegates, and stakeholders, without whom our progress would not have been possible. We would especially like to thank the security service providers who deeply engaged with the program from the very beginning. We would also like to thank all respondents to the ADPC’s outreach in determining the procurement frameworks to tackle in Phase II, including @bobbay, @JoJo, @Frisson, @realdumbird, @IronBoots, and @krst, among others.
The ADPC was established as a crucial component of the Arbitrum ecosystem's governance structure, following a successful proposal and subsequent community vote in early 2024. The formation of the ADPC was driven by the growing need for a structured, transparent, and efficient approach to procurement within the Arbitrum ecosystem, ultimately contributing to the ecosystem's growth, security, and sustainability.
The inception of the ADPC can be traced back to discussions within the Arbitrum community about the challenges faced by projects building on the protocol, particularly in securing high-quality service providers. These discussions highlighted the need for a pre-emptive quality assurance mechanism that could benefit the entire ecosystem. Against the background that a dedicated procurement framework has, to our knowledge, not been established in any DAO prior, the committee's formation marked a pivotal moment not only in Arbitrum's governance evolution, but set a precedent for DAOs in general. We designed the ADPC to address immediate needs and to create a foundation for future growth and efficiency in the ecosystem.
Phase I of the ADPC ran for a duration of 182 days from February 21, 2024 (i.e., the day that the KYB for the ADPC members was completed) until August 20, 2024.
The ADPC’s mandate in Phase I consisted of the following:
Oversee and facilitate the Procurement Framework for security-oriented service providers within the Arbitrum Ecosystem.
Research and draft a proposal to set up a subsidy fund for security-oriented services to subsidize the costs for security services for smaller projects within the Arbitrum Ecosystem.
Research and implement a framework that will establish a set of qualitative & quantitative metrics that will be utilized to assess a project's eligibility for the subsidy fund referred to in paragraph [B] above.
Establish procurement frameworks for a myriad of verticals/service types that the Arbitrum DAO could need in the foreseeable future.
Create and communicate guidance notes & circulars that will substantiate & provide additional detail in relation to any procurement framework that is ratified by the ArbitrumDAO from time to time.
The ADPC made significant progress against its mandates:
The development of the RFP documentation was an intensive, multi-stage process that involved various stakeholders and multiple rounds of refinement. The key stages included: This procurement framework, being the first of its kind, set a new standard for procurement processes in the crypto space. The RFP received responses from 12 security service providers and the whitelisting of these providers is still in progress. We expect to execute the agreements necessary for enabling engagement in September 2024.
A. Oversight of Security-Oriented Service Providers Framework
The ADPC finalized and published extensive RFP documentation for whitelisting security service providers on June 19, 2024. This comprehensive framework is designed to establish a marketplace for whitelisted service providers to offer services pursuant to pre-agreed terms, conditions, and pricing to projects that have been granted subsidies under the Security Services Subsidy Fund Proposal.
The initial Subsidy Fund proposal incorporated: Following the publication of the initial proposal, the ADPC engaged in extensive community discussions. Key points of feedback included concerns about the large fund size and potential for inefficient capital allocation and questions about the capacity to manage such a large fund. In response to community feedback, the ADPC revised the proposal. In particular, the subsidy fund was reduced to $2.5 million worth of ARB (75% reduction) to potentially fund up to 12 projects for one cohort of 8 weeks and with a maximum subsidy per project of $250K (10% of the total fund). The ADPC also listened to and incorporated community feedback about the ADPC managing the initial subsidy fund itself. As a consequence, the ADPC translated raised community concerns into a concrete governance proposal to create a separate “Security Services Subsidy Fund Sub-Committee”, consisting of five members elected through a weighted voting system with a proposed compensation of 60,000 ARB in total. However, after thorough discussion, the community voted against the creation of the sub-committee, leaving the disbursement of funds under the subsidy fund to the ADPC.
B. Subsidy Fund Research & Proposal
The ADPC researched, drafted, and passed a proposal to set up a subsidy fund for security-oriented services; the development of the proposal was strongly influenced by community engagement, while the terms and conditions for the receipt of the subsidy (’Means Test’) were mainly based on our experience from traditional procurement processes.
For this assessment, we:
C. Development of Eligibility Framework (’Means Test’)
The Means Test and the related Grant Application T&Cs were uniquely developed for Arbitrum DAO as a structured approach to evaluate applications for financial assistance. The primary goal of the Means Test is to identify applicants who would benefit most from support with the potential for significant positive impact on the Arbitrum ecosystem while (i) ensuring equitable access to subsidies within the Arbitrum Ecosystem and (ii) preventing exploitation by larger players.
More detail about our exploration into future procurement frameworks can be found in the section on Methodology for Shortlisting Verticals for Phase II below.
D. Establishment of Future Procurement Frameworks
While our primary efforts were focused, due to the complexity of the undertaking and the high level of community engagement and input, on the oversight of the security-oriented service providers framework, the research and proposal of the subsidy fund, the development of the eligibility framework ('Means Test') and the creation and communication of guidance, we did conduct work to identify and prioritize potential verticals for future procurement frameworks. Our approach was to create a comprehensive and adaptable methodology that could be applied to various service categories, ensuring that future frameworks would be developed with a robust approach.
E. Creation and Communication of Guidance
The ADPC achieved its goal of keeping the community abreast of its activities and progress during the entirety of its first phase by:
A comprehensive set of learnings and recommendations can be found in the ADPC’s Phase I Outcome Report. A subset of the most important of these learnings that we will implement in Phase II are:
Financial Management & Budgeting
Given the nature of this initial phase being a pilot, the budget for Phase I was more ‘experimental’, and thus did not fully account for all necessary resources. As such, this proposal will include a comprehensive budget plan and management that:
Clear Alignment with Arbitrum Foundation
To improve effective coordination with the Arbitrum Foundation, in Phase II we will:
In Phase II, we will further outline the ADPC’s role in the continued growth of Arbitrum and ensure that it forms an important part of the DAO’s structure going forward, including as a key component of the OpCo.
Create a Long-Term Vision for the ADPC’s Role in Supporting Arbitrum
As can be seen in the Methodology for Shortlisting Verticals for Phase II section below, we have already begun to identify a list of selected procurement frameworks the ADPC can tackle over its next and future phases. To compile this list, we used a comprehensive methodology, involving community feedback and engagement, and took into account current market conditions and need for Arbitrum.
Community Engagement & Transparency
While we spent significant time and resources on community engagement and providing regular, detailed updates, this part of our mandate was more time-consuming than anticipated but crucial for the success of initiatives. Key learnings that we will implement in Phase II are to:
The ADPC proposes the following work packages in Phase II:
We have chosen this vertical based on discussions with key delegates and stakeholders, given that a key focus for Arbitrum is to grow the Orbit ecosystem, while RPC costs are relatively high and RPCs are critical for projects to deploy, similar to security audits. Moreover, the technical due diligence around infrastructure providers is a huge time suck for projects. Pre-vetting RPC providers would make it much more attractive for projects to build on Arbitrum. In case there is any major opposition to the selection of this vertical, the ADPC will in the first month of Phase II engage with key delegates and stakeholders to arrive at a final decision on the vertical to tackle. The stakeholders we have engaged with have demonstrated an interest in each of the verticals listed below. To find such a substitute vertical, we will: Shortlist key stakeholders to schedule calls with; Liaise with the Arbitrum Foundation to identify relevant legal and regulatory considerations associated with these frameworks; Create engagement surveys to be shared with key delegates and projects building on Arbitrum to identify their one prioritized vertical from the below four verticals: For further information on the methodology we used to shortlist these frameworks, see the Methodology for Shortlisting Verticals for Phase II section below.
Vertical 1. Procuring RPC Providers
Vertical 1 will be focused on creating a whitelisted panel of RPC providers that can be procured by projects currently building or looking to build on Arbitrum. This panel of RPC providers will enable streamlined access and transparent pricing during the project’s build phase or post-launch, adding to the ecosystem of support services for Arbitrum projects and Orbit chains.
Vertical Description Need DevRel Firms The procurement of DevRel firms consists of two categories: (1) procuring online content producers that can get Arbitrum mentioned in developer resources, and (2) procuring consultancy shops and dedicated teams for Arbitrum to educate developers and projects about Arbitrum technology and help them build on Arbitrum. After discussions with the Arbitrum Foundation, we realized that there is a lack of concentrated DevRel support from the DAO to disseminate the benefits of Arbitrum tech like Stylus to existing and potential new projects. Improving Arbitrum’s reach in developer resources can help onboard more developers into the ecosystem, while dedicated teams can better help projects looking to build on Arbitrum (e.g., game developers funded via GCP). OTC Services Creating a whitelisted panel of OTC desks via which projects and contributors on Arbitrum (incl. the AF) can safely liquidate their ARB or other assets without causing an impact on the price. Users can submit quotes via a front-end, which can then be routed to all OTC desks, with the best price being chosen. The current ARB liquidation process leads to many projects and grant recipients liquidating ARB themselves which leads to dilutive effects on ARB price, and there is no set way of liquidating ARB. The price impact of swapping ARB is high, and having a panel of whitelisted OTC desks and a streamlined method of liquidating ARB across the DAO is critical. Tokenomics & Token Launch Teams Creating a whitelisted panel of tokenomics and token launch teams that projects building on Arbitrum can tap into, enabling streamlined access and transparent pricing during the project’s build phase or post-launch, adding to the ecosystem of support services for Arbitrum projects and Orbit chains. Tokenomics and token launches are extremely nuanced and difficult aspects for crypto projects to get right, and there are not a lot of ‘top’ teams that can help projects create fit-for-purpose, sustainable tokenomics. Having a whitelisted set of service providers would incentivize projects to build on Arbitrum. Moreover, existing initiatives like GCP will be able to make it more attractive to build on Arbitrum with such a service and any initiatives focused on enabling building on Arbitrum benefit from tokenomics and token launch support. Risk Service Providers Creating a whitelisted panel of risk service providers that projects building on Arbitrum and DAO proposals and initiatives can tap into, enabling streamlined access and transparent pricing for both sets of stakeholders (Arbitrum projects and the DAO). As Arbitrum is the Home of DeFi and a lot of protocols will require access to risk service providers to assess asset and other types of risks, having a panel of whitelisted risk providers is a net benefit for projects. Moreover, in its role in the ARDC, Chaos Labs did a lot of work to assess the base fee increase and other risk assessments for DAO proposals that proved very informative for the DAO to make a decision. Procuring from a panel of providers ensures a better deal for the DAO and is important for a myriad of proposals.
The selection of event provider(s) will follow a two-step process: Together with the ADPC, Entropy Advisors will first create an events & sponsorships strategy while, in parallel, event providers will be whitelisted. Second, individual RFP processes will be conducted to procure event services for specific events defined in the event strategy from the whitelisted panel. Please refer to the “RFP - Establishing a DAO Events Strategy for 2025” proposal for granular detail on how this procurement process will be constructed when it is published in the coming weeks.
Vertical 2. Procuring Events Providers
Vertical 2 will be focused on providing the procurement services for events identified within the DAO Events Strategy for 2025. This event strategy is prepared by the ADPC, Entropy Advisors and Disruption Joe pursuant to a separate proposal.
Note:
Scope for Work Package 1
The scope within the 6-month term is to:
Scope for Work Package 2
To address these inefficiencies and better equip the DAO for future needs, we will propose the establishment of an Operational Expense (OpEx) budget. This budget is designed to streamline the DAO’s interaction with ADPC-whitelisted service providers by creating a direct utilization rail. This rail will allow DAO initiatives and contributors to access and utilize these pre-approved service providers without undergoing the cumbersome proposal process for each engagement. The OpEx budget essentially bypasses the bureaucratic hurdles that currently plague the DAO’s procurement process, enabling a more agile and responsive operational framework. The OpEx budget will be initially administered by the Multi-Signature Service (MSS), ensuring that funds are allocated specifically for the utilization of ADPC-whitelisted service providers. The ADPC will draft the initial proposal for the OpEx budget, which will include detailed guidelines on its usage. Importantly, while the ADPC will establish the budget, it will not have control over its management or the approval of expenditures, thus maintaining a clear separation of duties and preserving DAO oversight.
Objective
The Arbitrum DAO currently faces significant inefficiencies in its ability to engage with service providers, particularly those whitelisted by the ADPC. Presently, any effort to solicit services, such as a security audit, requires the DAO to navigate the entire governance proposal life cycle — a process that can extend over a month for just a single deliverable. This protracted timeline not only delays critical operations but also impedes the DAO's ability to respond swiftly to emerging needs, creating a bottleneck that hinders operational efficiency.
Moreover, the OpEx budget is not just a temporary fix; it is a strategic initiative designed to future-proof the DAO’s operations. As the DAO evolves, the OpEx budget can be seamlessly integrated into future organizational structures, such as the prospective OpCo, which has been under discussion. By establishing this budget now, the DAO ensures it has a ready-made, adaptable infrastructure in place to meet its future operational needs. This forward-thinking approach not only addresses current inefficiencies but also lays the foundation for a more resilient and responsive organizational framework.
Why is an OpEx Budget Needed?
Currently, the DAO’s engagement with service providers is hampered by a rigid and time-consuming process that involves submitting a governance proposal, conducting a Snapshot temperature check, and finally, holding an on-chain vote. This multi-step process is not only inefficient but also stifles the DAO’s ability to procure services in a timely manner, particularly in scenarios requiring quick action. By introducing an OpEx budget, we aim to eliminate these bureaucratic barriers, creating a streamlined pathway for the DAO to access necessary services from ADPC-whitelisted providers.
Key Aspects of the Proposal
In summary, the introduction of an OpEx budget addresses the current inefficiencies in the DAO’s procurement process by providing a streamlined mechanism for engaging with service providers. It also future-proofs the DAO by laying the groundwork for its evolving operational needs, ensuring that the DAO can continue to operate efficiently and effectively as it grows and adapts.
Benefits of the Proposal
Scope for Work Package 4
We are leaving some flexibility in this Work Package given the pace of change in the DAO and the broader crypto market, and recognize that the DAO’s needs and wants will likely change over time. Note: This work package will likely be subject to the ADPC requiring additional funding since this Phase II proposal is based on conducting procurement for two verticals. If the need for additional funding to conduct procurement for these further verticalsarises, the ADPC will approach the DAO with further details about budget and scope.
Scope of Optional Additional Verticals
On completion of Work Package 1 and subject to (i) DAO demand and (ii) capacity of the ADPC at that point, procurement for up to [2] additional verticals on request from the DAO after approval and approved by the DAO governance process. Where the procurement for such additional verticals is likely to require an extension to the ADPC term, this Work Package will be contingent on that renewal being granted by the DAO to avoid partial completion of tasks.
The ADPC is budgeting USD 360,000 for the work in Phase II as outlined in the Phase II Mandate section above. In Phase II, the ADPC will continue with producing the agreed outputs together with a continuation of management of all legacy programs including the management of the Subsidy Fund for Security Service Providers. Management of the Subsidy Fund for Security Services [Work Package 2] Regarding the Management of the Subsidy Fund for Security Services [Work Package 2], given the operational effort to set up and run such a fund, as described in Work Package 2 above, we would usually charge a management fee including Operational Expenses as a percentage fee of the value of the fund. In this case, however, given that this is the pilot phase for the fund and that all the pre-work to set the fund up including the passing of the Tally vote and liaising with the Arbitrum Foundation has already been completed, we will waive all fees to run the fund in the pilot phase as a sign of our commitment and in order to make it as seamless as possible to prove the success of the fund in this first iteration. This fee waiver only applies to the current proposal. If there is an extension to the Subsidy Fund in the future, management fees will be included in the respective proposal.
Phase II Budget
As outlined in the Phase I Outcome Report and the section on Key Learnings & Improvements from Phase I above, the actual work in the ADPC was significantly more time intensive than priced-in, but taken on by the committee as goodwill in the pilot phase. Since we have now left the pilot phase and will provide procurement services for two verticals in Work Package 1, the budget naturally reflects this.
To take this into account, we propose an additional budget of 15% Operational Expenses which will be allocated for the engagement of SMEs and for other operational expenses and running costs. The Operational Expenses budget includes (non-exhaustive): The remaining unused funds of this sub-budget will be returned to Arbitrum’s treasury after Phase II has been concluded. The Operational Expenses Budget for Phase II will total USD 54,000.
Operational Expenses Budget
Phase I highlighted the importance of including operational expenses in the budget: This is necessary to engage external subject matter experts - as we did with DeDaub in Phase I - and cover operational expenses such as third party communication tools and collaboration infrastructure.
ARB Token Calculation
To determine the ARB token amount, we used the 14-day Time-Weighted Average Price (TWAP) of ARB/USD, each as listed EOD UTC, until EOD on Thu Sep 19 on CoinGecko (https://www.coingecko.com/en/coins/arbitrum/historical_data), prior to the proposal being posted on Tally. This method ensures a fair and current valuation while mitigating short-term price volatility. We'll add a 20% buffer to this amount to account for potential price fluctuations between proposal submission and execution. The remaining unused funds of this buffer will be returned to Arbitrum’s treasury after Phase II has been concluded.
| Item | USD Amount | TWAP ARB Amount |
|---|---|---|
| Baseline for Phase II Procurement Deliverables | $360,000 | ARB 691,745 |
| Operational Expenses for external parties and services (15%) | $54,000 | ARB 103,762 |
| Sub-Total | $414,000 | ARB 795,507 |
| ARB Buffer (20%) | $82,800 | ARB 159,101 |
| Total | $496,800 | ARB 954,608 |
The total budget requested is 954,608 ARB. Please find the Google sheet with the corresponding calculation of the TWAP ARB Amount here.
A detailed breakdown of the budget can be found in the Google sheet here.
Importance to Projects on Arbitrum
This factor takes into account the importance of the vertical with respect to the following criteria: - Frequency of use of the vertical by Projects; Higher ratings indicate higher levels of importance. Importance to DAO Proposals & Initiatives
The extent to which the PF solves issues faced by existing DAO proposals and initiatives, helps operationalize them, and increases their chances of success. Higher ratings indicate higher levels of importance. Solving Existing DAO Needs
The extent to which the PF solves issues faced by the DAO in general, and how significantly the PF will help professionalize and operationalize the DAO further. Higher ratings indicate higher levels of utility to the DAO. Overlap with Existing DAO Initiatives / Structure
There are initiatives in the DAO or from the Foundation that are already tackling the problem solved by the PF. The ranking will take into account how well the PF vertical avoids overlap/duplication. Higher scores indicate PF is better at avoiding overlap/duplication. Procurement Complexity / Cost
The complexity of constructing the procurement framework and the cost to do so. Higher ratings indicate lower complexity. Monetary Savings for Projects on Arbitrum
This criterion evaluates cost savings for projects on Arbitrum resulting from an implementation of the respective PF. Higher ratings indicate greater cost savings. Monetary Savings for DAO
This criterion evaluates cost savings for the DAO resulting from an implementation of the respective PF. Higher ratings indicate greater cost savings. Increase in Deployment Efficiency
This criterion evaluates the extent to which an introduction of the PF makes deployment for new projects more efficient. The greater the efficiency improvements, the higher the rating. Each of these factors are rated on a scale of 0 (Not Applicable at All), 1 (Low), 2 (Medium), 3 (High), and higher scores are better. Note: Some of these factors are not applicable to some verticals. As such, the final score for each vertical is the percentage it has achieved, to enable comparability between verticals. For example, if the Events vertical has 6 factors that are applicable to it, the maximum score it can achieve is 18 and its final score is the percentage of the score it has achieved out of 18, so if it has achieved 17, its final score is 94%.
Methodology
In order to identify the verticals that will be most beneficial for the ADPC to tackle in Phase II, we created a non-weighted scoring system to rate all verticals against the following factors:
The verticals we selected to obtain further feedback on from high-context delegates, existing projects on Arbitrum, and new projects looking to build on Arbitrum, were those with scores >80% and constitute the below verticals: Note: We did not initially include Risk Service Providers in the list of verticals since these were already available to the DAO via the ARDC. As such, we did not ask for specific feedback from delegates and stakeholders for this vertical. However, given that the ARDC may eliminate this function in its next iteration, we decided to include it in our list and, as it scored very highly, include it in the list of verticals to potentially tackle in Phase II.
Application of Methodology to Frameworks
We identified 27 verticals that we could potentially tackle in Phase II. The below table represents the scores per vertical with the methodology applied, in order from highest to lowest. For a detailed breakdown of the application of the methodology with rationales for each individual score, please see the table here.
Vertical Score Events 94% Tokenomics & Token Launch Teams 91% DevRel Firms 91% OTC Services 88% KYC Providers 86% Risk Service Providers 86% RPC Providers 81% Marketing 79% Oracle Services 76% API Providers 76% Node Management Software 71% Transaction Monitoring & Analytics Tools 63% Identity Management 62% BD / Partnerships Team 58% Human Resourcing 58% Cloud Providers 52% Design / UI / UX 48% Reporting Tools / Dashboards / Analytics 42% Trademarks / Patents / IP Registrations & Defence 38% Treasury Management Services 38% Legal Firms Panel 33% Training / Education Providers 29% R&D 29% Smart Contract Developers 29% Lobby / Industry Groups 25% Travel Providers 22% Policy Development 21%
We reached out to 25 stakeholders for feedback: L2Beat, Coinflip, GMX, DK, Gauntlet, Wintermute, Griff Green, Blockworks, Frisson, JoJo, Jones DAO, Pepperoni Jo3, Treasure, Camelot, Cattin, Premia, MUX Protocol, MaxLomu, Bob Rossi, Karpatkey, Princeton Blockchain Club, Bobbay, Angle Protocol, Merkl, and PaperImperium. Based on our interactions with the community, we decided to move forward with the procurement of RPC providers as the first vertical. This is because RPC costs are high, RPCs are critical for projects to deploy, similar to security audits, and technical due diligence around infrastructure providers is a complex task that drains time and resources from projects. As such, creating a panel of whitelisted RPC providers streamlines the building process for projects. In addition, we locked in 'Events' as a second vertical. The reason for this is that we spoke with Entropy Advisors about the need for a coherent events strategy for Arbitrum DAO, which is also apparent from the multiple concurrent events proposals being proposed in the DAO. As a result, we decided to create a proposal alongside Entropy Advisors and DisruptionJoe to establish a DAO Events Strategy for 2025, which will be published soon. While the proposal on the DAO Events Strategy for 2025 is focused on defining in particular the type and distribution of events as a first step, event services and event providers have to be procured in a second step to execute on the identified strategy. This second step, i.e., the provision of those procurement services for the identified events, is the subject of this proposal.
Community Engagement & Feedback Collection
After shortlisting the top six verticals, we decided to validate the shortlisted verticals with high-context delegates, existing Arbitrum projects, and new projects aiming to build on Arbitrum. The intention was to further narrow down the verticals to the two we would tackle in Phase II.
As in Phase I, the ADPC commits to maintaining its high standards of transparency and community engagement. We will:
Kindly note that Phase II of the ADPC’s term will be subject to the same checks and balances found within the Procurement Committee proposal, regulated by an agreement entered into by all elected ADPC Members, with the Arbitrum Foundation serving as a counterparty to the agreement. These checks and balances include:
Conflict of Interest Provision: ADPC Members will be bound to act in absolute good faith, utmost honesty, refraining from deriving unauthorized profits from their position & disclose conflicts of interest. ADPC members should always disclose any potential or actual conflicts of interests to other ADPC members who will then proceed to mitigate the respective ADPC Members’ involvement in the task in relation to which such ADPC Member is conflicted.
To sum up, all ADPC Members must declare the nature and extent of any interest, direct or indirect, which the ADPC Member is aware that she, he or it has in a proposed task at hand.
Record-keeping and Reporting: Comprehensive and precise record-keeping is imperative. ADPC Members will be required to maintain detailed accounts and documentation of the ADPC’s internal operational workflow together with meeting minutes. Furthermore, periodic reporting is essential so as to keep the ArbitrumDAO updated re. Task-specific progress & internal ADPC Administration.
Duty of Impartiality: ADPC Members will have an obligation to act in an impartial manner in relation to their tasks & workflow, ensuring that the ADPC is not compromised by personal interests or external influences.
Obligation of Recusal: ADPC Members with a conflict of interest involving a project and/or service provider being reviewed by the ADPC should recuse themselves from participating in the evaluation, facilitation & administration of the applicable procurement process.
Prohibition of Self-Dealing: Participants should refrain from voting on sending funds to themselves or organizations where any portion of those funds is expected to flow to them, their other projects, or anyone they have a close personal or economic relationship with.
Ethical Trading: Members are required to follow ethical trading standards concerning ARB and any other relevant digital assets.
We propose to use the Multi-Sig Support Service for Arbitrum DAO. Accordingly, we have taken advantage of the cost savings associated with that service and not included any costs for multi-sig management in this proposal.
The ADPC will utilize a Protocol-Owned Execution strategy on Aera to convert the program’s ARB into USDC for operational purposes. The Protocol-Owned Execution strategy utilizes off-chain logic to monitor onchain liquidity and model the price impact of trading. The ADPC will use an Aera Vault, with Gauntlet as the guardian, to execute the conversion. Trade execution is scheduled and sized according to impact modeling and executed on Odos, or Bebop. Based on current market conditions, it would take approximately one week to trade out of 414K USD worth of ARB with minimal impact.

Protocol-Owned Execution
The Protocol-Owned Execution strategy uses off-chain logic to monitor onchain liquidity, model price impact, and plan the execution of active and passive trading. Based on current market conditions, it will take < 1 week to swap out of 414k USD worth of ARB with minimal impact.
For ARB on the Arbitrum Chain, Gauntlet will swap out tokens using either Odos (DEX aggregator) or BeBop (self-execution solver).
Passive execution uses concentrated ARB positions in an ARB/USDC pool (Odos supports projects such as Camelot, Uniswap V3, and more). The amount converted through this position is periodically claimed, and a new ARB position is set in the pool. These can be thought of as limit orders.

Active and passive execution are used in tandem to maximize liquidity sourcing. Price impact modeling and gas cost determine the intraday trading schedule and size. Historical data is used to determine initial parameters. We continuously monitor slippage, intraday price impact, and medium-term price impact and adjust execution parameters if necessary. Intraday price impact is measured as the likelihood of observable price divergence in the hour after trading. The medium-term impact is measured as the effect of trade size on the divergence relative to a peer benchmark.

The example chart shows rolling slippage for one of Aera’s Trade Execution Customers.

The example chart shows the likelihood of intraday impact for one of Aera’s Trade Execution Customers.
ADPC Vault Parameters
ADPC Members Payment Process
Once the ARB is converted into USDC, the Aera vault will utilize LlamaPay to stream the total payment due to the ADPC member wallet addresses over the course of the 6-month period (120k USDC per member, 360k USDC in total). The remainder of the converted funds (54k USDC) will remain in the MSS as the OpEx budget. This process will be coordinated with the MSS chairs and members.
About Aera
Aera is an on-chain solution to optimize DAO funds autonomously. It addresses the common pain point of inactive treasury management, which often hinders a DAO’s ability to maintain its runway, cover liabilities, and benefit from market growth. Unlike traditional institutions that rely on agile managers for fund allocation, DAOs face unique challenges, including governance and incentive alignment with external managers.
To address these, Aera offers a unified solution for efficiently and transparently managing on-chain treasuries, grants, and incentive funds through customizable vaults. Aera vaults can hold stablecoins, native tokens, and other cryptocurrencies, with their objective functions tailored to each DAO’s needs. Guardians leverage off-chain logic to automate rebalancing decisions, ensuring the vaults meet their objectives across various market scenarios and time horizons.
You can read more about Aera here.
I. Executive Summary II. Background of the ADPC III. Achievements & Progress IV. Key Learnings & Improvements from Phase I V. Phase II Mandate VI. Budget & Methodology VII. Methodology for Shortlisting Verticals for Phase II VIII. Transparency & Community Engagement IX. Checks & Balances X. Multi-Sig XI. ARB Conversion Strategy
The Arbitrum DAO Procurement Committee (”ADPC”), composed of Axis Advisory, Areta, and Daimon Legal, is coming to the end of its first phase on August 20, 2024. As such, this proposal aims to extend the ADPC’s tenure into Phase II for a 6-month period, which will commence on the date on which the Tally vote for this proposal is executed on-chain.
The ADPC’s pilot phase proceeded successfully, with significant outcomes to Arbitrum DAO and a range of key learnings for the committee. Creating a comprehensive procurement process from the ground up to ensure that Arbitrum is seen as a leader not only in the technical sphere but also within decentralized governance has been a great opportunity.
We laid the foundation for the ADPC to be an effective set-up bringing the benefits of well-structured procurement to Arbitrum DAO. Cost savings will result from the creation and use of procurement frameworks and marketplaces developed by the ADPC uniquely for Arbitrum DAO as well as the necessary legal and operational infrastructure and strategic sourcing methodology.
The ADPC's initial phase was conducted as a proof of concept demonstrating the capability of the team and the benefits arising from the strategic use of advanced sourcing methodology. The ADPC proposes to build on these successes into Phase II of the ADPC's engagement. In this Phase II, the ADPC, after careful alignment with key stakeholders in the DAO, proposes to work on all of the following work packages:
Vertical 1 will be focused on procuring RPC providers for projects building in the Arbitrum ecosystem. This decision is based on engagement with delegates and stakeholders as well as an understanding of the core services required by all projects looking to build in the Arbitrum ecosystem.
Vertical 2 will be focused on providing the procurement services for events identified within the DAO Events Strategy for 2025. This event strategy is prepared by the ADPC, Entropy Advisors and Disruption Joe pursuant to a separate proposal. Please note that the ADPC will not request any funding for its events services procurement in that separate proposal.
The scope within the 6-month term is to develop evaluation criteria, draft and publish the Approach to Market (RFP/tender), evaluate responses to Approach to Market and whitelist supplier/s. Contract negotiations with whitelisted suppliers are not in the scope as the counter-party may be the Arbitrum Foundation or third parties utilizing their own counsel, and the ADPC has no influence on those internal legal processes.
Further details on our process for arriving at these shortlisted verticals can be found below in the section on Methodology for Shortlisting Verticals for Phase II.
Work Package 2: Continued management of the Subsidy Fund for Security Services and, based on the success of the first cohort, publishing the proposal for an extension of the fund.
Work Package 3
Definition and creation of an Operational Expense (OpEx) budget for the Arbitrum DAO, to be custodied by the Multi-Signature Safe (MSS), and allocated towards the utilisation of service providers as whitelisted by the ADPC. This creates a utilisation rail for the DAO to be able to utilise the services of the whitelisted service providers procured by the ADPC. Without this in place, the DAO is unable to utilise these service providers without the full proposal process (Forum, Snapshot, On-Chain).
The ADPC will draft and propose the OpEx proposal to the DAO; further details, including the process and procedure for utilization of the OpEx budget by the DAO, will be outlined in this separate proposal to the DAO. This seperate proposal will contain multiple options for the size of the OpEx budget for the community to vote on.
Creating a Phase II Outcome Report, similar to the one we have published for Phase I, and submitting it to the DAO.
Continued alignment with key stakeholders in the DAO on the evolution of the Arbitrum DAO’s structure, and ensuring that the ADPC fits into any structure that is defined (e.g., OpCo).
Ad-hoc tasks, e.g., aligning and connecting whitelisted service providers with existing and incoming projects on Arbitrum, existing and incoming DAO proposals, etc.
The overall budget for the 6-month term will be USD 414,000 including OpEx, details on which can be found below in the Budget & Methodology section. The Funding Request from the on-chain vote will be 954,608 ARB based on the time weighted average ARB price of $0.5204/ARB as further outlined below. A buffer has been added so that, in the case of ARB depreciation, the ADPC multi-sig under the Multi-Sig Service (MSS) is still able to satisfy payments to the ADPC's members. Unutilized ARB will be returned to the Arbitrum DAO treasury.
The multi-sig requested to manage the funds is within the Multi-Sig Support Service (MSS) established by Entropy Advisors. The Multi-Sig that has been created by the MSS is the following address:
arb1:0x13d4Ff2A83fBCB8F5fc73cE66CF5928eD0943cB0
After receipt of the ARB, the ADPC will convert as much of the requested amount as is required to obtain 414,000 USDC and will return the unutilized ARB to the DAO treasury. This is intended to avoid fluctuations in ARB price and ensures that the ADPC avoids using the buffer as much as possible.
The ADPC will utilize a Protocol-Owned Execution strategy on Gauntlet's Aera solution to convert the program’s ARB into USDC for operational purposes. The Protocol-Owned Execution strategy utilizes off-chain logic to monitor on-chain liquidity and model the price impact of trading. The ADPC will use an Aera Vault, with Gauntlet as the guardian, to execute the conversion. Trade execution is scheduled and sized according to impact modelling and executed on Odos, or Bebop. Based on current market conditions, it would take approximately one week to trade out of 414K USD worth of ARB with minimal impact.
Once the ARB is converted into USDC, the Aera vault will utilize LlamaPay to stream the total payment due to the ADPC member wallet addresses over the course of the 6-month period (120k USDC per member, 360k USDC in total). The remainder of the converted funds (54k USDC) will remain in the MSS as the OpEx budget. This process will be coordinated with the MSS chairs and members.
Further details about the ARB conversion strategy and about Aera can be found below in the 'ARB Conversion Strategy' section below.
Note: The proposal includes the re-election of the current members of the ADPC. For any future extension terms of the ADPC, the process outlined in the original Tally vote will stand unless automatic renewal of the then-current members is proposed. Of course, this will be subject to the potential OpCo that gets formed and any implications that may have on the structure of the ADPC.
We would like to acknowledge the consistent participation and deep input from the Arbitrum community, delegates, and stakeholders, without whom our progress would not have been possible. We would especially like to thank the security service providers who deeply engaged with the program from the very beginning. We would also like to thank all respondents to the ADPC’s outreach in determining the procurement frameworks to tackle in Phase II, including @bobbay, @JoJo, @Frisson, @realdumbird, @IronBoots, and @krst, among others.
The ADPC was established as a crucial component of the Arbitrum ecosystem's governance structure, following a successful proposal and subsequent community vote in early 2024. The formation of the ADPC was driven by the growing need for a structured, transparent, and efficient approach to procurement within the Arbitrum ecosystem, ultimately contributing to the ecosystem's growth, security, and sustainability.
The inception of the ADPC can be traced back to discussions within the Arbitrum community about the challenges faced by projects building on the protocol, particularly in securing high-quality service providers. These discussions highlighted the need for a pre-emptive quality assurance mechanism that could benefit the entire ecosystem. Against the background that a dedicated procurement framework has, to our knowledge, not been established in any DAO prior, the committee's formation marked a pivotal moment not only in Arbitrum's governance evolution, but set a precedent for DAOs in general. We designed the ADPC to address immediate needs and to create a foundation for future growth and efficiency in the ecosystem.
Phase I of the ADPC ran for a duration of 182 days from February 21, 2024 (i.e., the day that the KYB for the ADPC members was completed) until August 20, 2024.
The ADPC’s mandate in Phase I consisted of the following:
Oversee and facilitate the Procurement Framework for security-oriented service providers within the Arbitrum Ecosystem.
Research and draft a proposal to set up a subsidy fund for security-oriented services to subsidize the costs for security services for smaller projects within the Arbitrum Ecosystem.
Research and implement a framework that will establish a set of qualitative & quantitative metrics that will be utilized to assess a project's eligibility for the subsidy fund referred to in paragraph [B] above.
Establish procurement frameworks for a myriad of verticals/service types that the Arbitrum DAO could need in the foreseeable future.
Create and communicate guidance notes & circulars that will substantiate & provide additional detail in relation to any procurement framework that is ratified by the ArbitrumDAO from time to time.
The ADPC made significant progress against its mandates:
The development of the RFP documentation was an intensive, multi-stage process that involved various stakeholders and multiple rounds of refinement. The key stages included: This procurement framework, being the first of its kind, set a new standard for procurement processes in the crypto space. The RFP received responses from 12 security service providers and the whitelisting of these providers is still in progress. We expect to execute the agreements necessary for enabling engagement in September 2024.
A. Oversight of Security-Oriented Service Providers Framework
The ADPC finalized and published extensive RFP documentation for whitelisting security service providers on June 19, 2024. This comprehensive framework is designed to establish a marketplace for whitelisted service providers to offer services pursuant to pre-agreed terms, conditions, and pricing to projects that have been granted subsidies under the Security Services Subsidy Fund Proposal.
The initial Subsidy Fund proposal incorporated: Following the publication of the initial proposal, the ADPC engaged in extensive community discussions. Key points of feedback included concerns about the large fund size and potential for inefficient capital allocation and questions about the capacity to manage such a large fund. In response to community feedback, the ADPC revised the proposal. In particular, the subsidy fund was reduced to $2.5 million worth of ARB (75% reduction) to potentially fund up to 12 projects for one cohort of 8 weeks and with a maximum subsidy per project of $250K (10% of the total fund). The ADPC also listened to and incorporated community feedback about the ADPC managing the initial subsidy fund itself. As a consequence, the ADPC translated raised community concerns into a concrete governance proposal to create a separate “Security Services Subsidy Fund Sub-Committee”, consisting of five members elected through a weighted voting system with a proposed compensation of 60,000 ARB in total. However, after thorough discussion, the community voted against the creation of the sub-committee, leaving the disbursement of funds under the subsidy fund to the ADPC.
B. Subsidy Fund Research & Proposal
The ADPC researched, drafted, and passed a proposal to set up a subsidy fund for security-oriented services; the development of the proposal was strongly influenced by community engagement, while the terms and conditions for the receipt of the subsidy (’Means Test’) were mainly based on our experience from traditional procurement processes.
For this assessment, we:
C. Development of Eligibility Framework (’Means Test’)
The Means Test and the related Grant Application T&Cs were uniquely developed for Arbitrum DAO as a structured approach to evaluate applications for financial assistance. The primary goal of the Means Test is to identify applicants who would benefit most from support with the potential for significant positive impact on the Arbitrum ecosystem while (i) ensuring equitable access to subsidies within the Arbitrum Ecosystem and (ii) preventing exploitation by larger players.
More detail about our exploration into future procurement frameworks can be found in the section on Methodology for Shortlisting Verticals for Phase II below.
D. Establishment of Future Procurement Frameworks
While our primary efforts were focused, due to the complexity of the undertaking and the high level of community engagement and input, on the oversight of the security-oriented service providers framework, the research and proposal of the subsidy fund, the development of the eligibility framework ('Means Test') and the creation and communication of guidance, we did conduct work to identify and prioritize potential verticals for future procurement frameworks. Our approach was to create a comprehensive and adaptable methodology that could be applied to various service categories, ensuring that future frameworks would be developed with a robust approach.
E. Creation and Communication of Guidance
The ADPC achieved its goal of keeping the community abreast of its activities and progress during the entirety of its first phase by:
A comprehensive set of learnings and recommendations can be found in the ADPC’s Phase I Outcome Report. A subset of the most important of these learnings that we will implement in Phase II are:
Financial Management & Budgeting
Given the nature of this initial phase being a pilot, the budget for Phase I was more ‘experimental’, and thus did not fully account for all necessary resources. As such, this proposal will include a comprehensive budget plan and management that:
Clear Alignment with Arbitrum Foundation
To improve effective coordination with the Arbitrum Foundation, in Phase II we will:
In Phase II, we will further outline the ADPC’s role in the continued growth of Arbitrum and ensure that it forms an important part of the DAO’s structure going forward, including as a key component of the OpCo.
Create a Long-Term Vision for the ADPC’s Role in Supporting Arbitrum
As can be seen in the Methodology for Shortlisting Verticals for Phase II section below, we have already begun to identify a list of selected procurement frameworks the ADPC can tackle over its next and future phases. To compile this list, we used a comprehensive methodology, involving community feedback and engagement, and took into account current market conditions and need for Arbitrum.
Community Engagement & Transparency
While we spent significant time and resources on community engagement and providing regular, detailed updates, this part of our mandate was more time-consuming than anticipated but crucial for the success of initiatives. Key learnings that we will implement in Phase II are to:
The ADPC proposes the following work packages in Phase II:
We have chosen this vertical based on discussions with key delegates and stakeholders, given that a key focus for Arbitrum is to grow the Orbit ecosystem, while RPC costs are relatively high and RPCs are critical for projects to deploy, similar to security audits. Moreover, the technical due diligence around infrastructure providers is a huge time suck for projects. Pre-vetting RPC providers would make it much more attractive for projects to build on Arbitrum. In case there is any major opposition to the selection of this vertical, the ADPC will in the first month of Phase II engage with key delegates and stakeholders to arrive at a final decision on the vertical to tackle. The stakeholders we have engaged with have demonstrated an interest in each of the verticals listed below. To find such a substitute vertical, we will: Shortlist key stakeholders to schedule calls with; Liaise with the Arbitrum Foundation to identify relevant legal and regulatory considerations associated with these frameworks; Create engagement surveys to be shared with key delegates and projects building on Arbitrum to identify their one prioritized vertical from the below four verticals: For further information on the methodology we used to shortlist these frameworks, see the Methodology for Shortlisting Verticals for Phase II section below.
Vertical 1. Procuring RPC Providers
Vertical 1 will be focused on creating a whitelisted panel of RPC providers that can be procured by projects currently building or looking to build on Arbitrum. This panel of RPC providers will enable streamlined access and transparent pricing during the project’s build phase or post-launch, adding to the ecosystem of support services for Arbitrum projects and Orbit chains.
Vertical Description Need DevRel Firms The procurement of DevRel firms consists of two categories: (1) procuring online content producers that can get Arbitrum mentioned in developer resources, and (2) procuring consultancy shops and dedicated teams for Arbitrum to educate developers and projects about Arbitrum technology and help them build on Arbitrum. After discussions with the Arbitrum Foundation, we realized that there is a lack of concentrated DevRel support from the DAO to disseminate the benefits of Arbitrum tech like Stylus to existing and potential new projects. Improving Arbitrum’s reach in developer resources can help onboard more developers into the ecosystem, while dedicated teams can better help projects looking to build on Arbitrum (e.g., game developers funded via GCP). OTC Services Creating a whitelisted panel of OTC desks via which projects and contributors on Arbitrum (incl. the AF) can safely liquidate their ARB or other assets without causing an impact on the price. Users can submit quotes via a front-end, which can then be routed to all OTC desks, with the best price being chosen. The current ARB liquidation process leads to many projects and grant recipients liquidating ARB themselves which leads to dilutive effects on ARB price, and there is no set way of liquidating ARB. The price impact of swapping ARB is high, and having a panel of whitelisted OTC desks and a streamlined method of liquidating ARB across the DAO is critical. Tokenomics & Token Launch Teams Creating a whitelisted panel of tokenomics and token launch teams that projects building on Arbitrum can tap into, enabling streamlined access and transparent pricing during the project’s build phase or post-launch, adding to the ecosystem of support services for Arbitrum projects and Orbit chains. Tokenomics and token launches are extremely nuanced and difficult aspects for crypto projects to get right, and there are not a lot of ‘top’ teams that can help projects create fit-for-purpose, sustainable tokenomics. Having a whitelisted set of service providers would incentivize projects to build on Arbitrum. Moreover, existing initiatives like GCP will be able to make it more attractive to build on Arbitrum with such a service and any initiatives focused on enabling building on Arbitrum benefit from tokenomics and token launch support. Risk Service Providers Creating a whitelisted panel of risk service providers that projects building on Arbitrum and DAO proposals and initiatives can tap into, enabling streamlined access and transparent pricing for both sets of stakeholders (Arbitrum projects and the DAO). As Arbitrum is the Home of DeFi and a lot of protocols will require access to risk service providers to assess asset and other types of risks, having a panel of whitelisted risk providers is a net benefit for projects. Moreover, in its role in the ARDC, Chaos Labs did a lot of work to assess the base fee increase and other risk assessments for DAO proposals that proved very informative for the DAO to make a decision. Procuring from a panel of providers ensures a better deal for the DAO and is important for a myriad of proposals.
The selection of event provider(s) will follow a two-step process: Together with the ADPC, Entropy Advisors will first create an events & sponsorships strategy while, in parallel, event providers will be whitelisted. Second, individual RFP processes will be conducted to procure event services for specific events defined in the event strategy from the whitelisted panel. Please refer to the “RFP - Establishing a DAO Events Strategy for 2025” proposal for granular detail on how this procurement process will be constructed when it is published in the coming weeks.
Vertical 2. Procuring Events Providers
Vertical 2 will be focused on providing the procurement services for events identified within the DAO Events Strategy for 2025. This event strategy is prepared by the ADPC, Entropy Advisors and Disruption Joe pursuant to a separate proposal.
Note:
Scope for Work Package 1
The scope within the 6-month term is to:
Scope for Work Package 2
To address these inefficiencies and better equip the DAO for future needs, we will propose the establishment of an Operational Expense (OpEx) budget. This budget is designed to streamline the DAO’s interaction with ADPC-whitelisted service providers by creating a direct utilization rail. This rail will allow DAO initiatives and contributors to access and utilize these pre-approved service providers without undergoing the cumbersome proposal process for each engagement. The OpEx budget essentially bypasses the bureaucratic hurdles that currently plague the DAO’s procurement process, enabling a more agile and responsive operational framework. The OpEx budget will be initially administered by the Multi-Signature Service (MSS), ensuring that funds are allocated specifically for the utilization of ADPC-whitelisted service providers. The ADPC will draft the initial proposal for the OpEx budget, which will include detailed guidelines on its usage. Importantly, while the ADPC will establish the budget, it will not have control over its management or the approval of expenditures, thus maintaining a clear separation of duties and preserving DAO oversight.
Objective
The Arbitrum DAO currently faces significant inefficiencies in its ability to engage with service providers, particularly those whitelisted by the ADPC. Presently, any effort to solicit services, such as a security audit, requires the DAO to navigate the entire governance proposal life cycle — a process that can extend over a month for just a single deliverable. This protracted timeline not only delays critical operations but also impedes the DAO's ability to respond swiftly to emerging needs, creating a bottleneck that hinders operational efficiency.
Moreover, the OpEx budget is not just a temporary fix; it is a strategic initiative designed to future-proof the DAO’s operations. As the DAO evolves, the OpEx budget can be seamlessly integrated into future organizational structures, such as the prospective OpCo, which has been under discussion. By establishing this budget now, the DAO ensures it has a ready-made, adaptable infrastructure in place to meet its future operational needs. This forward-thinking approach not only addresses current inefficiencies but also lays the foundation for a more resilient and responsive organizational framework.
Why is an OpEx Budget Needed?
Currently, the DAO’s engagement with service providers is hampered by a rigid and time-consuming process that involves submitting a governance proposal, conducting a Snapshot temperature check, and finally, holding an on-chain vote. This multi-step process is not only inefficient but also stifles the DAO’s ability to procure services in a timely manner, particularly in scenarios requiring quick action. By introducing an OpEx budget, we aim to eliminate these bureaucratic barriers, creating a streamlined pathway for the DAO to access necessary services from ADPC-whitelisted providers.
Key Aspects of the Proposal
In summary, the introduction of an OpEx budget addresses the current inefficiencies in the DAO’s procurement process by providing a streamlined mechanism for engaging with service providers. It also future-proofs the DAO by laying the groundwork for its evolving operational needs, ensuring that the DAO can continue to operate efficiently and effectively as it grows and adapts.
Benefits of the Proposal
Scope for Work Package 4
We are leaving some flexibility in this Work Package given the pace of change in the DAO and the broader crypto market, and recognize that the DAO’s needs and wants will likely change over time. Note: This work package will likely be subject to the ADPC requiring additional funding since this Phase II proposal is based on conducting procurement for two verticals. If the need for additional funding to conduct procurement for these further verticalsarises, the ADPC will approach the DAO with further details about budget and scope.
Scope of Optional Additional Verticals
On completion of Work Package 1 and subject to (i) DAO demand and (ii) capacity of the ADPC at that point, procurement for up to [2] additional verticals on request from the DAO after approval and approved by the DAO governance process. Where the procurement for such additional verticals is likely to require an extension to the ADPC term, this Work Package will be contingent on that renewal being granted by the DAO to avoid partial completion of tasks.
The ADPC is budgeting USD 360,000 for the work in Phase II as outlined in the Phase II Mandate section above. In Phase II, the ADPC will continue with producing the agreed outputs together with a continuation of management of all legacy programs including the management of the Subsidy Fund for Security Service Providers. Management of the Subsidy Fund for Security Services [Work Package 2] Regarding the Management of the Subsidy Fund for Security Services [Work Package 2], given the operational effort to set up and run such a fund, as described in Work Package 2 above, we would usually charge a management fee including Operational Expenses as a percentage fee of the value of the fund. In this case, however, given that this is the pilot phase for the fund and that all the pre-work to set the fund up including the passing of the Tally vote and liaising with the Arbitrum Foundation has already been completed, we will waive all fees to run the fund in the pilot phase as a sign of our commitment and in order to make it as seamless as possible to prove the success of the fund in this first iteration. This fee waiver only applies to the current proposal. If there is an extension to the Subsidy Fund in the future, management fees will be included in the respective proposal.
Phase II Budget
As outlined in the Phase I Outcome Report and the section on Key Learnings & Improvements from Phase I above, the actual work in the ADPC was significantly more time intensive than priced-in, but taken on by the committee as goodwill in the pilot phase. Since we have now left the pilot phase and will provide procurement services for two verticals in Work Package 1, the budget naturally reflects this.
To take this into account, we propose an additional budget of 15% Operational Expenses which will be allocated for the engagement of SMEs and for other operational expenses and running costs. The Operational Expenses budget includes (non-exhaustive): The remaining unused funds of this sub-budget will be returned to Arbitrum’s treasury after Phase II has been concluded. The Operational Expenses Budget for Phase II will total USD 54,000.
Operational Expenses Budget
Phase I highlighted the importance of including operational expenses in the budget: This is necessary to engage external subject matter experts - as we did with DeDaub in Phase I - and cover operational expenses such as third party communication tools and collaboration infrastructure.
ARB Token Calculation
To determine the ARB token amount, we used the 14-day Time-Weighted Average Price (TWAP) of ARB/USD, each as listed EOD UTC, until EOD on Thu Sep 19 on CoinGecko (https://www.coingecko.com/en/coins/arbitrum/historical_data), prior to the proposal being posted on Tally. This method ensures a fair and current valuation while mitigating short-term price volatility. We'll add a 20% buffer to this amount to account for potential price fluctuations between proposal submission and execution. The remaining unused funds of this buffer will be returned to Arbitrum’s treasury after Phase II has been concluded.
| Item | USD Amount | TWAP ARB Amount |
|---|---|---|
| Baseline for Phase II Procurement Deliverables | $360,000 | ARB 691,745 |
| Operational Expenses for external parties and services (15%) | $54,000 | ARB 103,762 |
| Sub-Total | $414,000 | ARB 795,507 |
| ARB Buffer (20%) | $82,800 | ARB 159,101 |
| Total | $496,800 | ARB 954,608 |
The total budget requested is 954,608 ARB. Please find the Google sheet with the corresponding calculation of the TWAP ARB Amount here.
A detailed breakdown of the budget can be found in the Google sheet here.
Importance to Projects on Arbitrum
This factor takes into account the importance of the vertical with respect to the following criteria: - Frequency of use of the vertical by Projects; Higher ratings indicate higher levels of importance. Importance to DAO Proposals & Initiatives
The extent to which the PF solves issues faced by existing DAO proposals and initiatives, helps operationalize them, and increases their chances of success. Higher ratings indicate higher levels of importance. Solving Existing DAO Needs
The extent to which the PF solves issues faced by the DAO in general, and how significantly the PF will help professionalize and operationalize the DAO further. Higher ratings indicate higher levels of utility to the DAO. Overlap with Existing DAO Initiatives / Structure
There are initiatives in the DAO or from the Foundation that are already tackling the problem solved by the PF. The ranking will take into account how well the PF vertical avoids overlap/duplication. Higher scores indicate PF is better at avoiding overlap/duplication. Procurement Complexity / Cost
The complexity of constructing the procurement framework and the cost to do so. Higher ratings indicate lower complexity. Monetary Savings for Projects on Arbitrum
This criterion evaluates cost savings for projects on Arbitrum resulting from an implementation of the respective PF. Higher ratings indicate greater cost savings. Monetary Savings for DAO
This criterion evaluates cost savings for the DAO resulting from an implementation of the respective PF. Higher ratings indicate greater cost savings. Increase in Deployment Efficiency
This criterion evaluates the extent to which an introduction of the PF makes deployment for new projects more efficient. The greater the efficiency improvements, the higher the rating. Each of these factors are rated on a scale of 0 (Not Applicable at All), 1 (Low), 2 (Medium), 3 (High), and higher scores are better. Note: Some of these factors are not applicable to some verticals. As such, the final score for each vertical is the percentage it has achieved, to enable comparability between verticals. For example, if the Events vertical has 6 factors that are applicable to it, the maximum score it can achieve is 18 and its final score is the percentage of the score it has achieved out of 18, so if it has achieved 17, its final score is 94%.
Methodology
In order to identify the verticals that will be most beneficial for the ADPC to tackle in Phase II, we created a non-weighted scoring system to rate all verticals against the following factors:
The verticals we selected to obtain further feedback on from high-context delegates, existing projects on Arbitrum, and new projects looking to build on Arbitrum, were those with scores >80% and constitute the below verticals: Note: We did not initially include Risk Service Providers in the list of verticals since these were already available to the DAO via the ARDC. As such, we did not ask for specific feedback from delegates and stakeholders for this vertical. However, given that the ARDC may eliminate this function in its next iteration, we decided to include it in our list and, as it scored very highly, include it in the list of verticals to potentially tackle in Phase II.
Application of Methodology to Frameworks
We identified 27 verticals that we could potentially tackle in Phase II. The below table represents the scores per vertical with the methodology applied, in order from highest to lowest. For a detailed breakdown of the application of the methodology with rationales for each individual score, please see the table here.
Vertical Score Events 94% Tokenomics & Token Launch Teams 91% DevRel Firms 91% OTC Services 88% KYC Providers 86% Risk Service Providers 86% RPC Providers 81% Marketing 79% Oracle Services 76% API Providers 76% Node Management Software 71% Transaction Monitoring & Analytics Tools 63% Identity Management 62% BD / Partnerships Team 58% Human Resourcing 58% Cloud Providers 52% Design / UI / UX 48% Reporting Tools / Dashboards / Analytics 42% Trademarks / Patents / IP Registrations & Defence 38% Treasury Management Services 38% Legal Firms Panel 33% Training / Education Providers 29% R&D 29% Smart Contract Developers 29% Lobby / Industry Groups 25% Travel Providers 22% Policy Development 21%
We reached out to 25 stakeholders for feedback: L2Beat, Coinflip, GMX, DK, Gauntlet, Wintermute, Griff Green, Blockworks, Frisson, JoJo, Jones DAO, Pepperoni Jo3, Treasure, Camelot, Cattin, Premia, MUX Protocol, MaxLomu, Bob Rossi, Karpatkey, Princeton Blockchain Club, Bobbay, Angle Protocol, Merkl, and PaperImperium. Based on our interactions with the community, we decided to move forward with the procurement of RPC providers as the first vertical. This is because RPC costs are high, RPCs are critical for projects to deploy, similar to security audits, and technical due diligence around infrastructure providers is a complex task that drains time and resources from projects. As such, creating a panel of whitelisted RPC providers streamlines the building process for projects. In addition, we locked in 'Events' as a second vertical. The reason for this is that we spoke with Entropy Advisors about the need for a coherent events strategy for Arbitrum DAO, which is also apparent from the multiple concurrent events proposals being proposed in the DAO. As a result, we decided to create a proposal alongside Entropy Advisors and DisruptionJoe to establish a DAO Events Strategy for 2025, which will be published soon. While the proposal on the DAO Events Strategy for 2025 is focused on defining in particular the type and distribution of events as a first step, event services and event providers have to be procured in a second step to execute on the identified strategy. This second step, i.e., the provision of those procurement services for the identified events, is the subject of this proposal.
Community Engagement & Feedback Collection
After shortlisting the top six verticals, we decided to validate the shortlisted verticals with high-context delegates, existing Arbitrum projects, and new projects aiming to build on Arbitrum. The intention was to further narrow down the verticals to the two we would tackle in Phase II.
As in Phase I, the ADPC commits to maintaining its high standards of transparency and community engagement. We will:
Kindly note that Phase II of the ADPC’s term will be subject to the same checks and balances found within the Procurement Committee proposal, regulated by an agreement entered into by all elected ADPC Members, with the Arbitrum Foundation serving as a counterparty to the agreement. These checks and balances include:
Conflict of Interest Provision: ADPC Members will be bound to act in absolute good faith, utmost honesty, refraining from deriving unauthorized profits from their position & disclose conflicts of interest. ADPC members should always disclose any potential or actual conflicts of interests to other ADPC members who will then proceed to mitigate the respective ADPC Members’ involvement in the task in relation to which such ADPC Member is conflicted.
To sum up, all ADPC Members must declare the nature and extent of any interest, direct or indirect, which the ADPC Member is aware that she, he or it has in a proposed task at hand.
Record-keeping and Reporting: Comprehensive and precise record-keeping is imperative. ADPC Members will be required to maintain detailed accounts and documentation of the ADPC’s internal operational workflow together with meeting minutes. Furthermore, periodic reporting is essential so as to keep the ArbitrumDAO updated re. Task-specific progress & internal ADPC Administration.
Duty of Impartiality: ADPC Members will have an obligation to act in an impartial manner in relation to their tasks & workflow, ensuring that the ADPC is not compromised by personal interests or external influences.
Obligation of Recusal: ADPC Members with a conflict of interest involving a project and/or service provider being reviewed by the ADPC should recuse themselves from participating in the evaluation, facilitation & administration of the applicable procurement process.
Prohibition of Self-Dealing: Participants should refrain from voting on sending funds to themselves or organizations where any portion of those funds is expected to flow to them, their other projects, or anyone they have a close personal or economic relationship with.
Ethical Trading: Members are required to follow ethical trading standards concerning ARB and any other relevant digital assets.
We propose to use the Multi-Sig Support Service for Arbitrum DAO. Accordingly, we have taken advantage of the cost savings associated with that service and not included any costs for multi-sig management in this proposal.
The ADPC will utilize a Protocol-Owned Execution strategy on Aera to convert the program’s ARB into USDC for operational purposes. The Protocol-Owned Execution strategy utilizes off-chain logic to monitor onchain liquidity and model the price impact of trading. The ADPC will use an Aera Vault, with Gauntlet as the guardian, to execute the conversion. Trade execution is scheduled and sized according to impact modeling and executed on Odos, or Bebop. Based on current market conditions, it would take approximately one week to trade out of 414K USD worth of ARB with minimal impact.

Protocol-Owned Execution
The Protocol-Owned Execution strategy uses off-chain logic to monitor onchain liquidity, model price impact, and plan the execution of active and passive trading. Based on current market conditions, it will take < 1 week to swap out of 414k USD worth of ARB with minimal impact.
For ARB on the Arbitrum Chain, Gauntlet will swap out tokens using either Odos (DEX aggregator) or BeBop (self-execution solver).
Passive execution uses concentrated ARB positions in an ARB/USDC pool (Odos supports projects such as Camelot, Uniswap V3, and more). The amount converted through this position is periodically claimed, and a new ARB position is set in the pool. These can be thought of as limit orders.

Active and passive execution are used in tandem to maximize liquidity sourcing. Price impact modeling and gas cost determine the intraday trading schedule and size. Historical data is used to determine initial parameters. We continuously monitor slippage, intraday price impact, and medium-term price impact and adjust execution parameters if necessary. Intraday price impact is measured as the likelihood of observable price divergence in the hour after trading. The medium-term impact is measured as the effect of trade size on the divergence relative to a peer benchmark.

The example chart shows rolling slippage for one of Aera’s Trade Execution Customers.

The example chart shows the likelihood of intraday impact for one of Aera’s Trade Execution Customers.
ADPC Vault Parameters
ADPC Members Payment Process
Once the ARB is converted into USDC, the Aera vault will utilize LlamaPay to stream the total payment due to the ADPC member wallet addresses over the course of the 6-month period (120k USDC per member, 360k USDC in total). The remainder of the converted funds (54k USDC) will remain in the MSS as the OpEx budget. This process will be coordinated with the MSS chairs and members.
About Aera
Aera is an on-chain solution to optimize DAO funds autonomously. It addresses the common pain point of inactive treasury management, which often hinders a DAO’s ability to maintain its runway, cover liabilities, and benefit from market growth. Unlike traditional institutions that rely on agile managers for fund allocation, DAOs face unique challenges, including governance and incentive alignment with external managers.
To address these, Aera offers a unified solution for efficiently and transparently managing on-chain treasuries, grants, and incentive funds through customizable vaults. Aera vaults can hold stablecoins, native tokens, and other cryptocurrencies, with their objective functions tailored to each DAO’s needs. Guardians leverage off-chain logic to automate rebalancing decisions, ensuring the vaults meet their objectives across various market scenarios and time horizons.
You can read more about Aera here.
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/91?u=ocandocrypto
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/90?u=tane
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/88?u=winverse
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/91?u=ocandocrypto
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/90?u=tane
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/88?u=winverse
Democratising lobbyism, on-chain. Check out lobbyfi.xyz
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/86
https://forum.arbitrum.foundation/t/griff-green-delegate-communication-thread/25040/32?u=griff
The Event Horizon Community Voted to Support this Proposal ehARB-34: EventHorizon.vote/vote/arbitrum/ehARB-34
The Event Horizon Community Voted to Support this Proposal ehARB-34: EventHorizon.vote/vote/arbitrum/ehARB-34
See https://forum.arbitrum.foundation/t/alex-lumley-savvy-dao-delegate-communication-thread/26147/
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/83?u=tekr0x.eth
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/54
I support this proposal as it enhances transparency and governance efficiency within the Arbitrum ecosystem.
While I’d like to see focus on the expert service provider network, it’s cool to keep going for 6 more mknths
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/79?u=0x_ultra
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/51?u=castlecapital
Although I see the single DAO focus as a missed opportunity for composable and hence better used and funded tooling, this proposal is still valuable for Arbitrum
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/77?u=mcfly
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/44
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/75?u=0xdonpepe
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/38?u=duokongcrypto
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/74?u=euphoria
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/73?u=todayindefi
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/32?u=larva
Updates to this proposal since Snapshot have not removed us from opposition. Our main objection to the Phase II proposal overall was that it simultaneously authorized the ADPC to continue but did not initiate a re-election process, keeping the same members in the available seats. We simply don’t believe this is good form. While this proposal adds that future extensions must require an election, that is still missing from this proposal. Overall, the proposal is mostly thoughtful and complete, but we do not support normalizing extending terms for any elected position within governance without an election on each individual officeholder.
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/72?u=0xtalvo.eth_mty
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/63?u=mcfly
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/62
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/59?u=winverse
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/57?u=blockworksresearch
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/55?u=ocandocrypto
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/54
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/53?u=tane
https://forum.arbitrum.foundation/t/seed-latam-delegate-communication-thread/13895/47?u=seedgov
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/51?u=castlecapital
We do not support simultaneously extending a budget and re-election. These should be separate votes.
https://forum.arbitrum.foundation/t/griff-green-delegate-communication-thread/25040/32?u=griff
The Event Horizon Community Voted to Support this Proposal ehARB-23: EventHorizon.vote/vote/arbitrum/ehARB-23
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/48?u=blueweb
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/46?u=dianedai
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/45?u=tekr0x.eth
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/43?u=bruce
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/42?u=0x_ultra
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/29?u=pennblockchain
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/38?u=duokongcrypto
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/37?u=0xdonpepe
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/35?u=jojo
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/32?u=larva
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/30?u=0xtalvo.eth_mty
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/18?u=ezr3al
Democratising lobbyism, on-chain. Check out lobbyfi.xyz
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/86
https://forum.arbitrum.foundation/t/griff-green-delegate-communication-thread/25040/32?u=griff
The Event Horizon Community Voted to Support this Proposal ehARB-34: EventHorizon.vote/vote/arbitrum/ehARB-34
The Event Horizon Community Voted to Support this Proposal ehARB-34: EventHorizon.vote/vote/arbitrum/ehARB-34
See https://forum.arbitrum.foundation/t/alex-lumley-savvy-dao-delegate-communication-thread/26147/
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/83?u=tekr0x.eth
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/54
I support this proposal as it enhances transparency and governance efficiency within the Arbitrum ecosystem.
While I’d like to see focus on the expert service provider network, it’s cool to keep going for 6 more mknths
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/79?u=0x_ultra
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/51?u=castlecapital
Although I see the single DAO focus as a missed opportunity for composable and hence better used and funded tooling, this proposal is still valuable for Arbitrum
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/77?u=mcfly
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/44
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/75?u=0xdonpepe
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/38?u=duokongcrypto
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/74?u=euphoria
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/73?u=todayindefi
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/32?u=larva
Updates to this proposal since Snapshot have not removed us from opposition. Our main objection to the Phase II proposal overall was that it simultaneously authorized the ADPC to continue but did not initiate a re-election process, keeping the same members in the available seats. We simply don’t believe this is good form. While this proposal adds that future extensions must require an election, that is still missing from this proposal. Overall, the proposal is mostly thoughtful and complete, but we do not support normalizing extending terms for any elected position within governance without an election on each individual officeholder.
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/72?u=0xtalvo.eth_mty
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/63?u=mcfly
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/62
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/59?u=winverse
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/57?u=blockworksresearch
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/55?u=ocandocrypto
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/54
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/53?u=tane
https://forum.arbitrum.foundation/t/seed-latam-delegate-communication-thread/13895/47?u=seedgov
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/51?u=castlecapital
We do not support simultaneously extending a budget and re-election. These should be separate votes.
https://forum.arbitrum.foundation/t/griff-green-delegate-communication-thread/25040/32?u=griff
The Event Horizon Community Voted to Support this Proposal ehARB-23: EventHorizon.vote/vote/arbitrum/ehARB-23
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/48?u=blueweb
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/46?u=dianedai
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/45?u=tekr0x.eth
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/43?u=bruce
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/42?u=0x_ultra
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/29?u=pennblockchain
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/38?u=duokongcrypto
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/37?u=0xdonpepe
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/35?u=jojo
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/32?u=larva
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/30?u=0xtalvo.eth_mty
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/18?u=ezr3al
gTrade supports the proposal to extend the ADPC's tenure into Phase II. The ADPC has established a much-needed procurement framework, bringing both structure and efficiency to the ecosystem. While there may be concerns about the lack of elections, it's important to consider the time required to effectively onboard new members. From an efficiency standpoint, allowing the current team to continue into the next phase is a resource-optimized approach. The Arbitrum DAO can then evaluate their performance at the conclusion of Phase II.
gTrade supports the proposal to extend the ADPC's tenure into Phase II. The ADPC has established a much-needed procurement framework, bringing both structure and efficiency to the ecosystem. While there may be concerns about the lack of elections, it's important to consider the time required to effectively onboard new members. From an efficiency standpoint, allowing the current team to continue into the next phase is a resource-optimized approach. The Arbitrum DAO can then evaluate their performance at the conclusion of Phase II.
The results are in for the [NON-CONSTITUTIONAL] Arbitrum DAO Procurement Committee: Phase II Proposal on-chain proposal.
See how the community voted and more Arbitrum stats: https://dhive.io/proposal/1384
The results are in for the [NON-CONSTITUTIONAL] Arbitrum DAO Procurement Committee: Phase II Proposal on-chain proposal.
See how the community voted and more Arbitrum stats: https://dhive.io/proposal/1384
Appreciate the work that has done by the Procurement Committe. This proposal overall looks reasonable. However, we feel that the $360k budget breakdown for the verticals is not detailed enough and would like to see a more detailed breakdown.
Appreciate the work that has done by the Procurement Committe. This proposal overall looks reasonable. However, we feel that the $360k budget breakdown for the verticals is not detailed enough and would like to see a more detailed breakdown.
We do recognize the work that has been done and achieved during the pilot phase. And this is a well-thought proposal, generally we support, only with one suggestion:
Based on the achievement that has been done in the first 6 month, the work packages of the 2nd 6 months is way too ambitious. We saw that the budget has also been increased due to the expansion of the scope of work. This makes sense. But with so many verticals, shall we put some priority to certain verticals? What are must do and what are potentially be done if have capacity.
We do recognize the work that has been done and achieved during the pilot phase. And this is a well-thought proposal, generally we support, only with one suggestion:
Based on the achievement that has been done in the first 6 month, the work packages of the 2nd 6 months is way too ambitious. We saw that the budget has also been increased due to the expansion of the scope of work. This makes sense. But with so many verticals, shall we put some priority to certain verticals? What are must do and what are potentially be done if have capacity.
We support the extension of the Procurement Committee and believe the budget allocated for this is reasonable.
Additionally, we’re pleased to see the DAO improving the functioning of governance and working towards becoming a leader in this area.
We support the extension of the Procurement Committee and believe the budget allocated for this is reasonable.
Additionally, we’re pleased to see the DAO improving the functioning of governance and working towards becoming a leader in this area.
First of all, a big thank you to Axis Advisory, Areta, and Daimon Legal for spearheading this initiative and all the work that you've done so far. Through the ADPC, Arbitrum has set an important precedent and much-needed structure for what we believe will be an increasingly important part of decentralised governance more broadly going forward; that is, ultimate power in the hands of token holders with more complex day-to-day tasks being delegated to a community-responsive working group like the ADPC.
As others have already noted, the ADPC did a commendable job in engaging with the community and incorporating feedback, and great to see that additional steps are being taken in this regard.
First of all, a big thank you to Axis Advisory, Areta, and Daimon Legal for spearheading this initiative and all the work that you've done so far. Through the ADPC, Arbitrum has set an important precedent and much-needed structure for what we believe will be an increasingly important part of decentralised governance more broadly going forward; that is, ultimate power in the hands of token holders with more complex day-to-day tasks being delegated to a community-responsive working group like the ADPC.
As others have already noted, the ADPC did a commendable job in engaging with the community and incorporating feedback, and great to see that additional steps are being taken in this regard.
Avantgarde is very much for the continuation of this initiative and supports the ADPC in their proposal for a renewed mandate. Below we share a few questions that arose while going through the draft prop:
Regarding the OpEx budget - can you provide any insight into the oversight mechanisms for this budget? e.g., how the MSS will ensure transparency and accountability in spending and what processes will be in place to report back to the DAO on fund utilisation?
On the management of the Security Services Subsidy Fund (kudos for waiving management fees for the pilot phase) - how are you thinking about this long term, including if the fund grows in size/scope etc?
As far as is understood, the multi-sig management will be handled by the MSS established by Entropy - but what does the specific roles and responsibilities look like? who holds decision-making authority and how would potential conflicts of interest be addressed?
First of all, a big thank you to Axis Advisory, Areta, and Daimon Legal for spearheading this initiative and all the work that you've done so far. Through the ADPC, Arbitrum has set an important precedent and much-needed structure for what we believe will be an increasingly important part of decentralised governance more broadly going forward; that is, ultimate power in the hands of token holders with more complex day-to-day tasks being delegated to a community-responsive working group like the ADPC.
As others have already noted, the ADPC did a commendable job in engaging with the community and incorporating feedback, and great to see that additional steps are being taken in this regard.
First of all, a big thank you to Axis Advisory, Areta, and Daimon Legal for spearheading this initiative and all the work that you've done so far. Through the ADPC, Arbitrum has set an important precedent and much-needed structure for what we believe will be an increasingly important part of decentralised governance more broadly going forward; that is, ultimate power in the hands of token holders with more complex day-to-day tasks being delegated to a community-responsive working group like the ADPC.
As others have already noted, the ADPC did a commendable job in engaging with the community and incorporating feedback, and great to see that additional steps are being taken in this regard.
Avantgarde is very much for the continuation of this initiative and supports the ADPC in their proposal for a renewed mandate. Below we share a few questions that arose while going through the draft prop:
Regarding the OpEx budget - can you provide any insight into the oversight mechanisms for this budget? e.g., how the MSS will ensure transparency and accountability in spending and what processes will be in place to report back to the DAO on fund utilisation?
On the management of the Security Services Subsidy Fund (kudos for waiving management fees for the pilot phase) - how are you thinking about this long term, including if the fund grows in size/scope etc?
As far as is understood, the multi-sig management will be handled by the MSS established by Entropy - but what does the specific roles and responsibilities look like? who holds decision-making authority and how would potential conflicts of interest be addressed?
The results are in for the ArbitrumDAO Procurement Committee Phase II off-chain proposal.
See how the community voted and more Arbitrum stats: https://dhive.io/proposal/1351
The results are in for the ArbitrumDAO Procurement Committee Phase II off-chain proposal.
See how the community voted and more Arbitrum stats: https://dhive.io/proposal/1351
Hey @sid_areta, thank you for providing this update.
Re Point #1, I don't think the Snapshot proposal clearly asks the DAO whether it would be happy to change the rules governing future ADPC elections, as per the terms of the ADPC's initial Tally proposal.
Hey @sid_areta, thank you for providing this update.
Re Point #1, I don't think the Snapshot proposal clearly asks the DAO whether it would be happy to change the rules governing future ADPC elections, as per the terms of the ADPC's initial Tally proposal.
It should be made explicitly clear that voting in favor of this proposal either changes the rules governing future ADPC elections, or that this re-election is a one-off exception to the ADPC election process that was ratified in the initial Tally proposal.
In its current format, the DAO is not given the possibility to change the rules governing future ADPC elections but rather the current ADPC members are proposing a re-election with no optionality regarding candidates, and without a clear structure for how elections in the future will look like.
Hey @sid_areta, thank you for providing this update.
Re Point #1, I don't think the Snapshot proposal clearly asks the DAO whether it would be happy to change the rules governing future ADPC elections, as per the terms of the ADPC's initial Tally proposal.
Hey @sid_areta, thank you for providing this update.
Re Point #1, I don't think the Snapshot proposal clearly asks the DAO whether it would be happy to change the rules governing future ADPC elections, as per the terms of the ADPC's initial Tally proposal.
It should be made explicitly clear that voting in favor of this proposal either changes the rules governing future ADPC elections, or that this re-election is a one-off exception to the ADPC election process that was ratified in the initial Tally proposal.
In its current format, the DAO is not given the possibility to change the rules governing future ADPC elections but rather the current ADPC members are proposing a re-election with no optionality regarding candidates, and without a clear structure for how elections in the future will look like.
hmm... but nowhere in this proposal does it mention anything about election or reelection :thinking: thus the assumption that "this is that Non-Constitutional AIP " that changes the election process is not valid. The respective Snapshot should clearly ask the DAO if the DAO wishes to change the ADPC election process or keep it as is.
Adding to @jameskbh 's point.
According to the initial proposal (https://www.tally.xyz/gov/arbitrum/proposal/43616303506326656287362617487331059827021737444126158637397168372555259240241) there must be a reelection process similar to the Security Council elections (as it mentions adapting Section 4 of the ArbitrumDAO Constitution).The proposal does not mention that former ADPC members can reelect themselves. Instead, it mentions that:
Adding to @jameskbh 's point.
According to the initial proposal (https://www.tally.xyz/gov/arbitrum/proposal/43616303506326656287362617487331059827021737444126158637397168372555259240241) there must be a reelection process similar to the Security Council elections (as it mentions adapting Section 4 of the ArbitrumDAO Constitution).The proposal does not mention that former ADPC members can reelect themselves. Instead, it mentions that:
hmm... but nowhere in this proposal does it mention anything about election or reelection :thinking: thus the assumption that "this is that Non-Constitutional AIP " that changes the election process is not valid. The respective Snapshot should clearly ask the DAO if the DAO wishes to change the ADPC election process or keep it as is.
Adding to @jameskbh 's point.
According to the initial proposal (https://www.tally.xyz/gov/arbitrum/proposal/43616303506326656287362617487331059827021737444126158637397168372555259240241) there must be a reelection process similar to the Security Council elections (as it mentions adapting Section 4 of the ArbitrumDAO Constitution).The proposal does not mention that former ADPC members can reelect themselves. Instead, it mentions that:
Adding to @jameskbh 's point.
According to the initial proposal (https://www.tally.xyz/gov/arbitrum/proposal/43616303506326656287362617487331059827021737444126158637397168372555259240241) there must be a reelection process similar to the Security Council elections (as it mentions adapting Section 4 of the ArbitrumDAO Constitution).The proposal does not mention that former ADPC members can reelect themselves. Instead, it mentions that:
Voted FOR: Arbitrum DAO Procurement Committee: Phase II Proposal
I voted FOR this proposal on Tally for the reasons outlined in my previous commenting rationale.
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/82
I believe in the teams' ability to continue to develop and iterate. I also believe in the grander vision of a market place for builders.
Voted FOR: Arbitrum DAO Procurement Committee: Phase II Proposal
I voted FOR this proposal on Tally for the reasons outlined in my previous commenting rationale.
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/82
I believe in the teams' ability to continue to develop and iterate. I also believe in the grander vision of a market place for builders.
Voting Rationale Link: https://forum.arbitrum.foundation/t/alex-lumley-savvy-dao-delegate-communication-thread/26147/33
Post the passing of the Tally vote for Phase II of the ADPC, we wanted to thank the community for your trust in the ADPC and all the great feedback and deep engagement thus far!
In this second phase, we will focus on the key initiatives highlighted in our work packages above, including:
Post the passing of the Tally vote for Phase II of the ADPC, we wanted to thank the community for your trust in the ADPC and all the great feedback and deep engagement thus far!
In this second phase, we will focus on the key initiatives highlighted in our work packages above, including:
In terms of regular updates and engagement with the community, we aim to:
We’re extremely excited to carry on with our efforts to pioneer decentralized procurement processes in this phase and supporting the growth of the Arbitrum ecosystem through effective procurement strategies.
I voted for this proposal in Tally, for the same reasons I did in Snapshot; past work by the ADPC had a positive impact. However, some concerns raised above are valid. Will keep tabs on reports and progress.
We will vote FOR.
While additional spending is not desired, some way to manage the DAO spending is needed, and this seems to be the only current way proposed. We will monitor the success of this initiative to see if it can meaningfully reduce DAO spending.
GM, I voted ABSTAIN on this proposal.
While I appreciate the ADPC's efforts and support the continuation of their work, including the structure and processes they've established, I believe the analysis provided for selecting RPCs as the vertical was insufficient to justify the decision.
GM, I voted ABSTAIN on this proposal.
While I appreciate the ADPC's efforts and support the continuation of their work, including the structure and processes they've established, I believe the analysis provided for selecting RPCs as the vertical was insufficient to justify the decision.
As I mentioned privately, there was no visible quantitative analysis of potential cost savings—only a high-level indication of whether they were "high" or "low." This would have made way easier to justify the selection.
I apologize for not engaging in a more extensive discussion before the vote.
Hard one.
I appreciate the changes in the proposal, as well as the feedback from the Snapshot proposal.
I highly value the structure and thoroughness of the ADPC reports. Helped a lot while we were planning onboarding working group problems to solved, for example.
Hard one.
I appreciate the changes in the proposal, as well as the feedback from the Snapshot proposal.
I highly value the structure and thoroughness of the ADPC reports. Helped a lot while we were planning onboarding working group problems to solved, for example.
It’s clear that with the current quorum, the proposal will pass, but I genuinely wish we had a better cost-benefit ratio for the expenses. Even though, okay, the next phase will come with re-elections, I feel like lately, the DAO is just saying yes to everything, voting, distributing funds, and we’re not demanding results in return, raising the bar, or seeking more clarity in the process.
Especially with this project that’s involved in security and procurement.
Even though I voted yes on Snapshot, this time I voted Against in Tally
Voted FOR: Arbitrum DAO Procurement Committee: Phase II Proposal
I voted FOR this proposal on Tally for the reasons outlined in my previous commenting rationale.
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/82
I believe in the teams' ability to continue to develop and iterate. I also believe in the grander vision of a market place for builders.
Voted FOR: Arbitrum DAO Procurement Committee: Phase II Proposal
I voted FOR this proposal on Tally for the reasons outlined in my previous commenting rationale.
https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/82
I believe in the teams' ability to continue to develop and iterate. I also believe in the grander vision of a market place for builders.
Voting Rationale Link: https://forum.arbitrum.foundation/t/alex-lumley-savvy-dao-delegate-communication-thread/26147/33
Post the passing of the Tally vote for Phase II of the ADPC, we wanted to thank the community for your trust in the ADPC and all the great feedback and deep engagement thus far!
In this second phase, we will focus on the key initiatives highlighted in our work packages above, including:
Post the passing of the Tally vote for Phase II of the ADPC, we wanted to thank the community for your trust in the ADPC and all the great feedback and deep engagement thus far!
In this second phase, we will focus on the key initiatives highlighted in our work packages above, including:
In terms of regular updates and engagement with the community, we aim to:
We’re extremely excited to carry on with our efforts to pioneer decentralized procurement processes in this phase and supporting the growth of the Arbitrum ecosystem through effective procurement strategies.
I voted for this proposal in Tally, for the same reasons I did in Snapshot; past work by the ADPC had a positive impact. However, some concerns raised above are valid. Will keep tabs on reports and progress.
We will vote FOR.
While additional spending is not desired, some way to manage the DAO spending is needed, and this seems to be the only current way proposed. We will monitor the success of this initiative to see if it can meaningfully reduce DAO spending.
GM, I voted ABSTAIN on this proposal.
While I appreciate the ADPC's efforts and support the continuation of their work, including the structure and processes they've established, I believe the analysis provided for selecting RPCs as the vertical was insufficient to justify the decision.
GM, I voted ABSTAIN on this proposal.
While I appreciate the ADPC's efforts and support the continuation of their work, including the structure and processes they've established, I believe the analysis provided for selecting RPCs as the vertical was insufficient to justify the decision.
As I mentioned privately, there was no visible quantitative analysis of potential cost savings—only a high-level indication of whether they were "high" or "low." This would have made way easier to justify the selection.
I apologize for not engaging in a more extensive discussion before the vote.
Hard one.
I appreciate the changes in the proposal, as well as the feedback from the Snapshot proposal.
I highly value the structure and thoroughness of the ADPC reports. Helped a lot while we were planning onboarding working group problems to solved, for example.
Hard one.
I appreciate the changes in the proposal, as well as the feedback from the Snapshot proposal.
I highly value the structure and thoroughness of the ADPC reports. Helped a lot while we were planning onboarding working group problems to solved, for example.
It’s clear that with the current quorum, the proposal will pass, but I genuinely wish we had a better cost-benefit ratio for the expenses. Even though, okay, the next phase will come with re-elections, I feel like lately, the DAO is just saying yes to everything, voting, distributing funds, and we’re not demanding results in return, raising the bar, or seeking more clarity in the process.
Especially with this project that’s involved in security and procurement.
Even though I voted yes on Snapshot, this time I voted Against in Tally
We vote FOR the proposal on Tally.
We maintain our decision made at its Snapshot voting phase and appreciate the additional information added to the proposal. We also appreciate the future effort to make sure that there will be elections before the next phase of the committee with potential collaborations with Entropy and/or other suitable entities.
We vote FOR the proposal on Tally.
We maintain our decision made at its Snapshot voting phase and appreciate the additional information added to the proposal. We also appreciate the future effort to make sure that there will be elections before the next phase of the committee with potential collaborations with Entropy and/or other suitable entities.
We voted FOR the Procurement Committee Phase II on Tally. We're looking forward to the outcomes of all 4 work packages and believe that Axis, Areta, and Daimon will do a good job. We hope to see regular reports to ensure accountability.
The following reflects the views of L2BEAT’s governance team, composed of @krst and @Sinkas, and it’s based on the combined research, fact-checking, and ideation of the two.
We’re voting AGAINST the proposal, just like we did during temp-check, and for the same reasons outlined in our previous comment as we don’t feel that our concerns had been addressed and mitigated.
The following reflects the views of L2BEAT’s governance team, composed of @krst and @Sinkas, and it’s based on the combined research, fact-checking, and ideation of the two.
We’re voting AGAINST the proposal, just like we did during temp-check, and for the same reasons outlined in our previous comment as we don’t feel that our concerns had been addressed and mitigated.
We value your perspective and we understand that you’re currently against this proposal, and will closely take your inputs into account when moving this forward. As promised, we’ll connect you with builders who have expressed an interest in the procurement of RPC services, so they can share their insights on the value they see in it. Re. the OpEx budget, we are taking your feedback into account as we design how to make it operational.
We’d like to point out that unfortunately this did not happen and we remain skeptical about the usefulness and effectiveness of this procurement processes. Moreover, even in the budget breakdown the OpEx budget (WP3) remains a single vague line with costs being somehow spread out across WP1 tasks. We are still not convinced by the budget breakdown and the tasks listed there.
While we appreciate and respect the work the ADPC team has done so far, we don't see enough justification to allocate this amount of funding to continue this initiative.
I voted FOR this proposal on Tally for the reasons outlined below. I'm comfortable with the team's approach of focusing on execution only for the events vertical to reduce scope. I still think it's ambitious to tackle two verticals at once, but am willing to let it play out and observe the results. I'm fine with the re-election of the current ARDC members, as I think continuity will benefit execution.
I voted FOR this proposal on Tally for the reasons outlined below. I'm comfortable with the team's approach of focusing on execution only for the events vertical to reduce scope. I still think it's ambitious to tackle two verticals at once, but am willing to let it play out and observe the results. I'm fine with the re-election of the current ARDC members, as I think continuity will benefit execution.
Overall, I think the amount of work proposed in Phase II is ambitious. My instinct is to recommend that we reduce the scope of Work Package 1 by focusing on only the RPC vertical. That way, the team will have more capacity to execute well on Work Packages 2-4. I think we can execute on the event vertical in Phase III.
I plan to spend more time with this proposal to provide additional feedback in the future.
DAOplomats is voting in favor on Tally.
We supported this proposal during temp check and maintaining that stance.
I voted FOR on Tally, but my comments still remain true: we should have a proper structure to keep the knowledge within the DAO for if/when service providers change, the work can proceed without a big disruption.
Voted For: After reviewing the proposal and feedback from fellow delegates I believe that Arbtirum DAO will benefit from this proposal being approved. Feedback regarding the election is a bit unclear to me, so I expect that the committee will be fully transparent about all future activities and will take our feedback into consideration. But I don't think this is such a blocker that we need another rewrite of the proposal. I believe that the committee will take our feedback and improve without a new proposal.
I fully support the proposal so voted for. A exceptional work has been done and budget seems rasonable.
I'm voting against the proposal in Tally
The reasons for not doing it now are unclear to me. I understand that there have been conversations with key stakeholders, but I don’t understand why we wouldn’t discuss or vote on the funds the DAO intends to allocate to these new Subsidy Funds before proceeding with the procurement work and legal agreements. My main concern is that the DAO might spend resources and time on this work, only for it to lose meaning later if the DAO either doesn’t agree on the amount to allocate or simply decides not to go through with it.
I'm reiterating my choice by voting in favor at this phase too. I'm both satisfied with the past performances and with the goals that have been set for the second phase. I also appreciate the efforts that were made to come up with a detailed explanation of the budget, providing a transparent and large view of their intentions. Concerning the electoral procedure, I already expressed my thoughts here https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/21?u=duokongcrypto
voting Against the current onchain proposal because we can’t create a procurement committee on the premise that it’s members will be elected by the DAO every 6 months and then on the end of the first term don’t do an election process and entrench the current members even more, with more scope, and therefor more power, especially for a procurement committee which is a function that concentrates immense power in itself, by definition.
We voted in favor of this proposal during the Snapshot stage, and we'll continue our support on Tally.
The changes posted by @sid_areta are improving greatly the Tally proposal, particularly regarding future phase re-elections. As others have noted, we should begin developing a general election framework, including tenure terms (duration and compensation).
We voted FOR the Procurement Committee Phase II on Tally. We're looking forward to the outcomes of all 4 work packages and believe that Axis, Areta, and Daimon will do a good job. We hope to see regular reports to ensure accountability.
The following reflects the views of L2BEAT’s governance team, composed of @krst and @Sinkas, and it’s based on the combined research, fact-checking, and ideation of the two.
We’re voting AGAINST the proposal, just like we did during temp-check, and for the same reasons outlined in our previous comment as we don’t feel that our concerns had been addressed and mitigated.
The following reflects the views of L2BEAT’s governance team, composed of @krst and @Sinkas, and it’s based on the combined research, fact-checking, and ideation of the two.
We’re voting AGAINST the proposal, just like we did during temp-check, and for the same reasons outlined in our previous comment as we don’t feel that our concerns had been addressed and mitigated.
We value your perspective and we understand that you’re currently against this proposal, and will closely take your inputs into account when moving this forward. As promised, we’ll connect you with builders who have expressed an interest in the procurement of RPC services, so they can share their insights on the value they see in it. Re. the OpEx budget, we are taking your feedback into account as we design how to make it operational.
We’d like to point out that unfortunately this did not happen and we remain skeptical about the usefulness and effectiveness of this procurement processes. Moreover, even in the budget breakdown the OpEx budget (WP3) remains a single vague line with costs being somehow spread out across WP1 tasks. We are still not convinced by the budget breakdown and the tasks listed there.
While we appreciate and respect the work the ADPC team has done so far, we don't see enough justification to allocate this amount of funding to continue this initiative.
I voted FOR this proposal on Tally for the reasons outlined below. I'm comfortable with the team's approach of focusing on execution only for the events vertical to reduce scope. I still think it's ambitious to tackle two verticals at once, but am willing to let it play out and observe the results. I'm fine with the re-election of the current ARDC members, as I think continuity will benefit execution.
I voted FOR this proposal on Tally for the reasons outlined below. I'm comfortable with the team's approach of focusing on execution only for the events vertical to reduce scope. I still think it's ambitious to tackle two verticals at once, but am willing to let it play out and observe the results. I'm fine with the re-election of the current ARDC members, as I think continuity will benefit execution.
Overall, I think the amount of work proposed in Phase II is ambitious. My instinct is to recommend that we reduce the scope of Work Package 1 by focusing on only the RPC vertical. That way, the team will have more capacity to execute well on Work Packages 2-4. I think we can execute on the event vertical in Phase III.
I plan to spend more time with this proposal to provide additional feedback in the future.
DAOplomats is voting in favor on Tally.
We supported this proposal during temp check and maintaining that stance.
I voted FOR on Tally, but my comments still remain true: we should have a proper structure to keep the knowledge within the DAO for if/when service providers change, the work can proceed without a big disruption.
Voted For: After reviewing the proposal and feedback from fellow delegates I believe that Arbtirum DAO will benefit from this proposal being approved. Feedback regarding the election is a bit unclear to me, so I expect that the committee will be fully transparent about all future activities and will take our feedback into consideration. But I don't think this is such a blocker that we need another rewrite of the proposal. I believe that the committee will take our feedback and improve without a new proposal.
I fully support the proposal so voted for. A exceptional work has been done and budget seems rasonable.
I'm voting against the proposal in Tally
The reasons for not doing it now are unclear to me. I understand that there have been conversations with key stakeholders, but I don’t understand why we wouldn’t discuss or vote on the funds the DAO intends to allocate to these new Subsidy Funds before proceeding with the procurement work and legal agreements. My main concern is that the DAO might spend resources and time on this work, only for it to lose meaning later if the DAO either doesn’t agree on the amount to allocate or simply decides not to go through with it.
I'm reiterating my choice by voting in favor at this phase too. I'm both satisfied with the past performances and with the goals that have been set for the second phase. I also appreciate the efforts that were made to come up with a detailed explanation of the budget, providing a transparent and large view of their intentions. Concerning the electoral procedure, I already expressed my thoughts here https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/21?u=duokongcrypto
voting Against the current onchain proposal because we can’t create a procurement committee on the premise that it’s members will be elected by the DAO every 6 months and then on the end of the first term don’t do an election process and entrench the current members even more, with more scope, and therefor more power, especially for a procurement committee which is a function that concentrates immense power in itself, by definition.
We voted in favor of this proposal during the Snapshot stage, and we'll continue our support on Tally.
The changes posted by @sid_areta are improving greatly the Tally proposal, particularly regarding future phase re-elections. As others have noted, we should begin developing a general election framework, including tenure terms (duration and compensation).
I'm voting against the proposal in Tally
The reasons for not doing it now are unclear to me. I understand that there have been conversations with key stakeholders, but I don’t understand why we wouldn’t discuss or vote on the funds the DAO intends to allocate to these new Subsidy Funds before proceeding with the procurement work and legal agreements. My main concern is that the DAO might spend resources and time on this work, only for it to lose meaning later if the DAO either doesn’t agree on the amount to allocate or simply decides not to go through with it.
However, for my support in Tally, I would like to see two things: first, a discussion about the amounts to be allocated to the new subsidy funds,
As I mentioned in my feedback, I believe the DAO should first determine whether it wants to allocate resources to RPC and event service providers, and how much, in order to properly assess the cost-benefit of the procurement service.
I am very grateful to the team behind the ADPC, they truly took the feedback into account and worked hard on this proposal. Also, as I mentioned to Bernard privately, I highly value the structure and completeness of their reports. I believe they raise the bar for the quality of reporting and information the DAO receives. If that pending discussion moves forward, I would be happy to vote in favor at another opportunity
Had to vote AGAINST, in agreement with @GFXlabs that automatic renewal of member terms without an election is bad form, even if it is time ineffient.
If it was a continuation of the same project i would understand, but given there are completely new deliverables i don't see the need for having the same members.
Vote: FOR
Type and Proposal Link Snapshot - Arbitrum DAO Procurement Committee: Phase II
Voting Rationale Link: https://forum.arbitrum.foundation/t/alex-lumley-savvy-dao-delegate-communication-thread/26147/15
=== COMMENTING ON PROPOSAL: ===
Vote: FOR
Type and Proposal Link Snapshot - Arbitrum DAO Procurement Committee: Phase II
Voting Rationale Link: https://forum.arbitrum.foundation/t/alex-lumley-savvy-dao-delegate-communication-thread/26147/15
=== COMMENTING ON PROPOSAL: ===
The Arbitrum DAO Procurement Committee has demonstrated considerable success in Phase I, establishing important procurement frameworks and infrastructure. However, while we support extending their tenure, we acknowledge that the proposal could benefit from a clearer budget breakdown, especially in terms of how funds will be allocated across different initiatives. In future phases, it would also be beneficial to engage the community earlier on re-election processes, ensuring a smooth transition and avoiding unnecessary centralization concerns. Addressing these key points would enhance both transparency and alignment with the DAO’s long-term objectives.
Finally, I believe a great direction for ADPC is to head towards building a market place for builders that really shows builders: Arbitrum is the best place to build your business. Focusing on the builder stakeholders and getting a good enough marketplace first, would add more value than going vertical by vertical.
Just voted 'FOR' this proposal on Tally for the reasons already outlined on my previous reply. Also, I appreciate the changes made from the Snapshot proposal (Budget breakdown + ARB Conversion Strategy) which provide further clarity for this proposal.
The following reflects the views of the Lampros Labs DAO governance team, composed of @Blueweb, @Euphoria, and Hirangi Pandya (@Nyx), based on our combined research, analysis, and ideation.
We are voting FOR this proposal in the Tally voting.
The following reflects the views of the Lampros Labs DAO governance team, composed of @Blueweb, @Euphoria, and Hirangi Pandya (@Nyx), based on our combined research, analysis, and ideation.
We are voting FOR this proposal in the Tally voting.
The changes made by @sid_areta from the Snapshot to the Tally proposal have provided better clarity to the proposal. Aside from these updates, our overall thoughts remain the same as expressed in our rationale during the Snapshot voting.
We’re voting FOR this proposal to extend the ADPC’s tenure into Phase II.
The team has shown they know what they’re doing by successfully completing Phase I, and keeping them on board ensures we maintain that momentum. Their plans for Phase II demonstrate they’re ready to keep delivering value, with a well-justified budget and a strong emphasis on transparency that aligns with our DAO’s values. We’ve also been impressed by their regular communication through calls and open discussions throughout Phase I.
We voted FOR this proposal
Rationale
We voted FOR this proposal
Rationale
I'll be voting in favor of extending the ADPC's role into Phase II on Tally and Snapshot. Their achievements in Phase I, including cost savings and setting up procurement frameworks, have demonstrated their effectiveness. The Phase II strategy is well-planned, with a clear and transparent budget.
After consideration, Treasure’s Arbitrum Representative Council (ARC) would like to share the following feedback on the proposal.
We voted FOR this proposal.
After consideration, Treasure’s Arbitrum Representative Council (ARC) would like to share the following feedback on the proposal.
We voted FOR this proposal.
We commend the ADPC for its accomplishments in its first term, particularly in establishing the service infrastructure that has become highly sought after by various projects. This aligns well with our vision of the DAO as a service hub, contributing to making Arbitrum a prime destination for builders.
While we occasionally wished for a quicker pace, we value the significant efforts of the ADPC team and support their continued leadership in managing this process. We also recognize the potential of several additional verticals being explored. However, L2Beats’ perspective on the importance of a comprehensive DAO budget before finalizing an OpEx-specific budget offers a compelling point of consideration. We look forward to seeing how discussions and this proposal evolve as the ADPC and the community provide further feedback.
Voted in favour to this proposal in the Snapshot stage.
Changes posted by @sid_areta are positive towards the Tally vote, especially around any future phase re-election.
Thanks for the detailed budget information.
However, I have a question: This budget does not include information on committee members' salaries. Are they part of the original budget or will they be separate expenses?
We voted YES to extending the ADPC for another 6 month term. We would like to first acknowledge this group’s pioneering efforts — as a DAO Procurement Committee is the first of its kind. We would like to also thank the committee for its laborious work. After reviewing the Outcome Report and attending the most recent ADPC call, it has become more apparent how time and energy intensive it was for the committee to navigate and set-up the required legal infrastructure backbone.
With that said, we would like to echo others concerns about the election procedure. Although we agree that it makes sense for continuity for the committee members to be automatically re-elected, the Tally vote that set up the ADPC does say that members are elected for a term of 6 months. Therefore, at the end of Phase II, we would like to see an election take place.
Hi all, thank you so much for your continued engagement and feedback on this proposal, and your trust in us for the next term!
Over the past few weeks, we had a lot of great discussions on and off the forum that have allowed us to identify the areas to sharpen our focus in for Phase II:
Hi all, thank you so much for your continued engagement and feedback on this proposal, and your trust in us for the next term!
Over the past few weeks, we had a lot of great discussions on and off the forum that have allowed us to identify the areas to sharpen our focus in for Phase II:
Furthermore, we have heard the community's sentiments on key topics and are taking them into consideration as outlined below, specifically:
Re-Elections
We will make sure that there is a round of elections held prior to any next phase and will drive the preparation ourselves - obviously, we would also appreciate any support from Entropy as the DAO Liaison to make sure expectations and handover are aligned with the DAO’s expectations and best practice. We absolutely have no intention of centralizing any power in the current members and solely proposed re-election for Phase II to enable productivity and efficiency and avoid significant ramp-up costs and time. As such, we want to make it clear that any next iteration of the ADPC includes a well-planned and executed election process.
Budget Breakdown
On the basis of the feedback we have received from @dianedai, @pedrob, @CastleCapital, @kuiclub, @BlockworksResearch, @PGov, @ocandocrypto, and @Tane, we have included a breakdown of the budget including the tasks and allocation of resources at the bottom of the Budget section of the proposal above:
Please note that the breakdown assumes efficiency gains from executing the work packages as proposed. The delivery timelines are based on our project plan and are indicative. If the scope of the proposal is altered, individual budgets will need to be to account for any potential modifications.
Further, we have heard feedback that whitelisting Dev Shops and making their services easy to access for projects aiming to build on Arbitrum would be valuable for the ecosystem in the mid-term, and we will explore this vertical further if it is relevant to the community and if our capacity allows us to do so. We will also explore opening up another round of whitelisting for security service providers, since we have seen demand from multiple top auditors who were not able to apply in the first round.
Lastly, we are grateful to have had helpful discussions with key delegates off the forum on further verticals to tackle. As you all know, it’s not always easy to capture everyone’s attention, and we’re mindful that mindspace is the rarest commodity - we truly appreciate any time you have taken to engage with this on the forum or directly with us.
Overall, with this incredibly helpful direction from the community and key delegates and our resharpened focus, we couldn’t be more excited to continue our work in Phase II!
Hi @krst and @Sinkas,
Thank you again for the thorough discussions we’ve had over the past few weeks. We do appreciate the exchange we’re continuing to have.
Hi @krst and @Sinkas,
Thank you again for the thorough discussions we’ve had over the past few weeks. We do appreciate the exchange we’re continuing to have.
We value your perspective and we understand that you’re currently against this proposal, and will closely take your inputs into account when moving this forward. As promised, we’ll connect you with builders who have expressed an interest in the procurement of RPC services, so they can share their insights on the value they see in it. Re. the OpEx budget, we are taking your feedback into account as we design how to make it operational.
I know we’ve discussed these topics before, and while our views on feasibility differ slightly (though not entirely), we remain confident in our ability to fulfil our commitments and support the creation of this fertile ground for the DAO.
We’ll stay in close touch and hope to alleviate any concerns going forward. Thanks again for providing meaningful feedback that helps us to shape our scope in the right direction. Appreciate it!
We're voting FOR this proposal. The ADPC has proven its value in Phase I. While concerns about centralization and election procedures are valid, disrupting the committee's momentum could be counterproductive. We urge the ADPC to prioritize knowledge transfer and explore more robust election processes for future iterations, ensuring long-term decentralization and continuity. As mentioned by others, we should start working on a general election framework, tenure terms (duration and compensation).
Hi all! In preparation for the Tally vote for Phase II of the ADPC, we wanted to (i) highlight the changes we made to the proposal after the Snapshot vote and (ii) provide further clarifications. These changes and clarifications incorporate the feedback provided by the community and optimize our operations.
Re-Elections
As highlighted in the comment above:
The following reflects the views of L2BEAT’s governance team, composed of @krst and @Sinkas, and it’s based on the combined research, fact-checking, and ideation of the two.
We’re voting AGAINST the proposal.
The following reflects the views of L2BEAT’s governance team, composed of @krst and @Sinkas, and it’s based on the combined research, fact-checking, and ideation of the two.
We’re voting AGAINST the proposal.
First off, we want to thank the ADPC both for its tenure over the past 6 months and for the effort put into creating this proposal. We appreciate their work, and we carefully considered our decision before voting.
There are 3 distinct reasons why we’ve decided to vote against the proposal:
We believe the work proposed is valuable, but it comes at a time when there’s no fertile ground in the DAO for it to work. We’d suggest a separate proposal is created for managing the security services subsidy fund and for the other work packages to be revisited down the line.
I'm voting against the proposal in Tally
The reasons for not doing it now are unclear to me. I understand that there have been conversations with key stakeholders, but I don’t understand why we wouldn’t discuss or vote on the funds the DAO intends to allocate to these new Subsidy Funds before proceeding with the procurement work and legal agreements. My main concern is that the DAO might spend resources and time on this work, only for it to lose meaning later if the DAO either doesn’t agree on the amount to allocate or simply decides not to go through with it.
However, for my support in Tally, I would like to see two things: first, a discussion about the amounts to be allocated to the new subsidy funds,
As I mentioned in my feedback, I believe the DAO should first determine whether it wants to allocate resources to RPC and event service providers, and how much, in order to properly assess the cost-benefit of the procurement service.
I am very grateful to the team behind the ADPC, they truly took the feedback into account and worked hard on this proposal. Also, as I mentioned to Bernard privately, I highly value the structure and completeness of their reports. I believe they raise the bar for the quality of reporting and information the DAO receives. If that pending discussion moves forward, I would be happy to vote in favor at another opportunity
Had to vote AGAINST, in agreement with @GFXlabs that automatic renewal of member terms without an election is bad form, even if it is time ineffient.
If it was a continuation of the same project i would understand, but given there are completely new deliverables i don't see the need for having the same members.
Vote: FOR
Type and Proposal Link Snapshot - Arbitrum DAO Procurement Committee: Phase II
Voting Rationale Link: https://forum.arbitrum.foundation/t/alex-lumley-savvy-dao-delegate-communication-thread/26147/15
=== COMMENTING ON PROPOSAL: ===
Vote: FOR
Type and Proposal Link Snapshot - Arbitrum DAO Procurement Committee: Phase II
Voting Rationale Link: https://forum.arbitrum.foundation/t/alex-lumley-savvy-dao-delegate-communication-thread/26147/15
=== COMMENTING ON PROPOSAL: ===
The Arbitrum DAO Procurement Committee has demonstrated considerable success in Phase I, establishing important procurement frameworks and infrastructure. However, while we support extending their tenure, we acknowledge that the proposal could benefit from a clearer budget breakdown, especially in terms of how funds will be allocated across different initiatives. In future phases, it would also be beneficial to engage the community earlier on re-election processes, ensuring a smooth transition and avoiding unnecessary centralization concerns. Addressing these key points would enhance both transparency and alignment with the DAO’s long-term objectives.
Finally, I believe a great direction for ADPC is to head towards building a market place for builders that really shows builders: Arbitrum is the best place to build your business. Focusing on the builder stakeholders and getting a good enough marketplace first, would add more value than going vertical by vertical.
Just voted 'FOR' this proposal on Tally for the reasons already outlined on my previous reply. Also, I appreciate the changes made from the Snapshot proposal (Budget breakdown + ARB Conversion Strategy) which provide further clarity for this proposal.
The following reflects the views of the Lampros Labs DAO governance team, composed of @Blueweb, @Euphoria, and Hirangi Pandya (@Nyx), based on our combined research, analysis, and ideation.
We are voting FOR this proposal in the Tally voting.
The following reflects the views of the Lampros Labs DAO governance team, composed of @Blueweb, @Euphoria, and Hirangi Pandya (@Nyx), based on our combined research, analysis, and ideation.
We are voting FOR this proposal in the Tally voting.
The changes made by @sid_areta from the Snapshot to the Tally proposal have provided better clarity to the proposal. Aside from these updates, our overall thoughts remain the same as expressed in our rationale during the Snapshot voting.
We’re voting FOR this proposal to extend the ADPC’s tenure into Phase II.
The team has shown they know what they’re doing by successfully completing Phase I, and keeping them on board ensures we maintain that momentum. Their plans for Phase II demonstrate they’re ready to keep delivering value, with a well-justified budget and a strong emphasis on transparency that aligns with our DAO’s values. We’ve also been impressed by their regular communication through calls and open discussions throughout Phase I.
We voted FOR this proposal
Rationale
We voted FOR this proposal
Rationale
I'll be voting in favor of extending the ADPC's role into Phase II on Tally and Snapshot. Their achievements in Phase I, including cost savings and setting up procurement frameworks, have demonstrated their effectiveness. The Phase II strategy is well-planned, with a clear and transparent budget.
After consideration, Treasure’s Arbitrum Representative Council (ARC) would like to share the following feedback on the proposal.
We voted FOR this proposal.
After consideration, Treasure’s Arbitrum Representative Council (ARC) would like to share the following feedback on the proposal.
We voted FOR this proposal.
We commend the ADPC for its accomplishments in its first term, particularly in establishing the service infrastructure that has become highly sought after by various projects. This aligns well with our vision of the DAO as a service hub, contributing to making Arbitrum a prime destination for builders.
While we occasionally wished for a quicker pace, we value the significant efforts of the ADPC team and support their continued leadership in managing this process. We also recognize the potential of several additional verticals being explored. However, L2Beats’ perspective on the importance of a comprehensive DAO budget before finalizing an OpEx-specific budget offers a compelling point of consideration. We look forward to seeing how discussions and this proposal evolve as the ADPC and the community provide further feedback.
Voted in favour to this proposal in the Snapshot stage.
Changes posted by @sid_areta are positive towards the Tally vote, especially around any future phase re-election.
Thanks for the detailed budget information.
However, I have a question: This budget does not include information on committee members' salaries. Are they part of the original budget or will they be separate expenses?
We voted YES to extending the ADPC for another 6 month term. We would like to first acknowledge this group’s pioneering efforts — as a DAO Procurement Committee is the first of its kind. We would like to also thank the committee for its laborious work. After reviewing the Outcome Report and attending the most recent ADPC call, it has become more apparent how time and energy intensive it was for the committee to navigate and set-up the required legal infrastructure backbone.
With that said, we would like to echo others concerns about the election procedure. Although we agree that it makes sense for continuity for the committee members to be automatically re-elected, the Tally vote that set up the ADPC does say that members are elected for a term of 6 months. Therefore, at the end of Phase II, we would like to see an election take place.
Hi all, thank you so much for your continued engagement and feedback on this proposal, and your trust in us for the next term!
Over the past few weeks, we had a lot of great discussions on and off the forum that have allowed us to identify the areas to sharpen our focus in for Phase II:
Hi all, thank you so much for your continued engagement and feedback on this proposal, and your trust in us for the next term!
Over the past few weeks, we had a lot of great discussions on and off the forum that have allowed us to identify the areas to sharpen our focus in for Phase II:
Furthermore, we have heard the community's sentiments on key topics and are taking them into consideration as outlined below, specifically:
Re-Elections
We will make sure that there is a round of elections held prior to any next phase and will drive the preparation ourselves - obviously, we would also appreciate any support from Entropy as the DAO Liaison to make sure expectations and handover are aligned with the DAO’s expectations and best practice. We absolutely have no intention of centralizing any power in the current members and solely proposed re-election for Phase II to enable productivity and efficiency and avoid significant ramp-up costs and time. As such, we want to make it clear that any next iteration of the ADPC includes a well-planned and executed election process.
Budget Breakdown
On the basis of the feedback we have received from @dianedai, @pedrob, @CastleCapital, @kuiclub, @BlockworksResearch, @PGov, @ocandocrypto, and @Tane, we have included a breakdown of the budget including the tasks and allocation of resources at the bottom of the Budget section of the proposal above:
Please note that the breakdown assumes efficiency gains from executing the work packages as proposed. The delivery timelines are based on our project plan and are indicative. If the scope of the proposal is altered, individual budgets will need to be to account for any potential modifications.
Further, we have heard feedback that whitelisting Dev Shops and making their services easy to access for projects aiming to build on Arbitrum would be valuable for the ecosystem in the mid-term, and we will explore this vertical further if it is relevant to the community and if our capacity allows us to do so. We will also explore opening up another round of whitelisting for security service providers, since we have seen demand from multiple top auditors who were not able to apply in the first round.
Lastly, we are grateful to have had helpful discussions with key delegates off the forum on further verticals to tackle. As you all know, it’s not always easy to capture everyone’s attention, and we’re mindful that mindspace is the rarest commodity - we truly appreciate any time you have taken to engage with this on the forum or directly with us.
Overall, with this incredibly helpful direction from the community and key delegates and our resharpened focus, we couldn’t be more excited to continue our work in Phase II!
Hi @krst and @Sinkas,
Thank you again for the thorough discussions we’ve had over the past few weeks. We do appreciate the exchange we’re continuing to have.
Hi @krst and @Sinkas,
Thank you again for the thorough discussions we’ve had over the past few weeks. We do appreciate the exchange we’re continuing to have.
We value your perspective and we understand that you’re currently against this proposal, and will closely take your inputs into account when moving this forward. As promised, we’ll connect you with builders who have expressed an interest in the procurement of RPC services, so they can share their insights on the value they see in it. Re. the OpEx budget, we are taking your feedback into account as we design how to make it operational.
I know we’ve discussed these topics before, and while our views on feasibility differ slightly (though not entirely), we remain confident in our ability to fulfil our commitments and support the creation of this fertile ground for the DAO.
We’ll stay in close touch and hope to alleviate any concerns going forward. Thanks again for providing meaningful feedback that helps us to shape our scope in the right direction. Appreciate it!
We're voting FOR this proposal. The ADPC has proven its value in Phase I. While concerns about centralization and election procedures are valid, disrupting the committee's momentum could be counterproductive. We urge the ADPC to prioritize knowledge transfer and explore more robust election processes for future iterations, ensuring long-term decentralization and continuity. As mentioned by others, we should start working on a general election framework, tenure terms (duration and compensation).
Hi all! In preparation for the Tally vote for Phase II of the ADPC, we wanted to (i) highlight the changes we made to the proposal after the Snapshot vote and (ii) provide further clarifications. These changes and clarifications incorporate the feedback provided by the community and optimize our operations.
Re-Elections
As highlighted in the comment above:
The following reflects the views of L2BEAT’s governance team, composed of @krst and @Sinkas, and it’s based on the combined research, fact-checking, and ideation of the two.
We’re voting AGAINST the proposal.
The following reflects the views of L2BEAT’s governance team, composed of @krst and @Sinkas, and it’s based on the combined research, fact-checking, and ideation of the two.
We’re voting AGAINST the proposal.
First off, we want to thank the ADPC both for its tenure over the past 6 months and for the effort put into creating this proposal. We appreciate their work, and we carefully considered our decision before voting.
There are 3 distinct reasons why we’ve decided to vote against the proposal:
We believe the work proposed is valuable, but it comes at a time when there’s no fertile ground in the DAO for it to work. We’d suggest a separate proposal is created for managing the security services subsidy fund and for the other work packages to be revisited down the line.
We voted YES to extending the ADPC for another 6 month term. We would like to first acknowledge this group’s pioneering efforts — as a DAO Procurement Committee is the first of its kind. We would like to also thank the committee for its laborious work. After reviewing the Outcome Report and attending the most recent ADPC call, it has become more apparent how time and energy intensive it was for the committee to navigate and set-up the required legal infrastructure backbone.
With that said, we would like to echo others concerns about the election procedure. Although we agree that it makes sense for continuity for the committee members to be automatically re-elected, the Tally vote that set up the ADPC does say that members are elected for a term of 6 months. Therefore, at the end of Phase II, we would like to see an election take place.
We look forward to the Phase II deliverables to procure Events Providers and RPC Providers, and would like to see updates made to the DAO throughout the process.
Hi all! In preparation for the Tally vote for Phase II of the ADPC, we wanted to (i) highlight the changes we made to the proposal after the Snapshot vote and (ii) provide further clarifications. These changes and clarifications incorporate the feedback provided by the community and optimize our operations.
Re-Elections
As highlighted in the comment above:
We will make sure that there is a round of elections held prior to any next phase and will drive the preparation ourselves - obviously, we would also appreciate any support from Entropy as the DAO Liaison to make sure expectations and handover are aligned with the DAO’s expectations and best practice. We absolutely have no intention of centralizing any power in the current members and solely proposed re-election for Phase II to enable productivity and efficiency and avoid significant ramp-up costs and time. As such, we want to make it clear that any next iteration of the ADPC includes a well-planned and executed election process.
Budget Breakdown
Based on feedback received from community members, we have provided a detailed breakdown of the budget in the Google sheet here. As mentioned above:
Please note that the breakdown assumes efficiency gains from executing the work packages as proposed. The delivery timelines are based on our project plan and are indicative. If the scope of the proposal is altered, individual budgets will need to be to account for any potential modifications.
ARB Conversion Strategy
We want to ensure that the amount of ARB utilized to obtain the budget of 414,000 USDC is as minimal as possible. Therefore, we have decided to use a Protocol-Owned Execution strategy on Gauntlet’s Aera solution for the conversion mechanism..
Once the ARB is converted into USDC, the Aera vault will utilize LlamaPay to stream the total payment due to the ADPC member wallet addresses over the course of the 6-month period (120k USDC per member, 360k USDC in total). The remainder of the converted funds (54k USDC) will remain in the MSS as the OpEx budget. This process will be coordinated with the MSS chairs and members.
Further details about the ARB conversion strategy and about Aera can be found in the newly added Section XI. ARB Conversion Strategy in the proposal.
ARB Token Calculation
We have updated the final ARB amount required to obtain the budget of 414,000 USDC based on the 14-day Time-Weighted Average Price (TWAP) of ARB/USD, each as listed EOD UTC, until EOD on Thu Sep 19 on CoinGecko (https://www.coingecko.com/en/coins/arbitrum/historical_data).
The TWAP ARB price used has been updated from $0.5425 to $0.5204, and the total amount of ARB requested has been updated from ARB 915,658 to ARB 954,608.
The Tally vote for this proposal will be live from 15.25 UTC on 26 September 2024 to 15.25 UTC on 10 October 2024 here.
We’re looking forward to continuing our efforts in Phase II and would like to thank the community for all the incredibly helpful feedback and engagement on this proposal!
gm, I voted FOR this proposal, acknowledging that:
gm, I voted FOR this proposal, acknowledging that:
However, I would like to challenge the decision to focus on RPC providers for Phase 2. With the launch of a new Orbit chain, we are currently using the free tier options offered by many providers. Based on my experience, this is sufficient for the early stages of ecosystem development. Chains in a growth phase are better positioned to select from a broader range of providers.
If the goal is to support emerging projects, I believe there are other areas where we could achieve greater impact.
A̶d̶d̶i̶t̶i̶o̶n̶a̶l̶l̶y̶, I̶ w̶o̶u̶l̶d̶ l̶i̶k̶e̶ t̶o̶ s̶e̶e̶ t̶h̶e̶ c̶o̶m̶p̶l̶e̶t̶i̶o̶n̶ o̶f̶ t̶h̶e̶ w̶h̶i̶t̶e̶l̶i̶s̶t̶i̶n̶g̶ p̶r̶o̶c̶e̶s̶s̶ f̶r̶o̶m̶ P̶h̶a̶s̶e̶ 1̶, w̶h̶i̶c̶h̶ h̶a̶s̶ n̶o̶t̶ y̶e̶t̶ b̶e̶e̶n̶ f̶u̶l̶l̶y̶ d̶e̶l̶i̶v̶e̶r̶e̶d̶. EDIT: looks like this has been completed
Thank you.
I voted for this extension, so the work is not disrupted, but I have several points to make:
I voted for this extension, so the work is not disrupted, but I have several points to make:
Happy to help in the implementation of those points.
Vote in favor in the coming days. The APDC has done an outstanding job in its duties. While the re-election period is reasonable, we believe that re-electing the main committee every six months should not become the norm. We encourage other representatives to reconsider the election cycle or extend the term, as projects like ADPC require ongoing attention and long-term consistency in monitoring service provision.
Regarding the breakdown of the ADPC budget and scope, we suggest it be presented as a separate proposal, with increased transparency.
DAOplomats is voting in favor of extending the ADPC tenure for another six months.
The work done by the ADPC has been a strong PoC and we would love to see them continue, completing a 12-month term. We also strongly resonate with @JoJo comment on re-election as retaining the current team should enable us to see proper results at the end of the twelve months.
DAOplomats is voting in favor of extending the ADPC tenure for another six months.
The work done by the ADPC has been a strong PoC and we would love to see them continue, completing a 12-month term. We also strongly resonate with @JoJo comment on re-election as retaining the current team should enable us to see proper results at the end of the twelve months.
We would suggest, however, that discussions on Phase III and/or re-elections should start at least two months before the end of Phase II. This would provide ample time for delegates and the community to reflect on the work done by the ADPC and prepare adequately if an election were to happen so there would be no delay in the mandate after Phase II.
Blockworks Research will be voting FOR this proposal on Snapshot.
The work that the APDC is invaluable, and we recognize that. Additionally, while we think a re-election period is justifiable, we cannot in good faith say that a relection period every 6 months for major committees should be the precedent, and would like to ask other delegates to either reconsider the elections or consider extending the tenure of the committee. For something as major as the ADPC, it requires ongoing attention, monitoring possible deals and service provision is truly a task of consistency.
Blockworks Research will be voting FOR this proposal on Snapshot.
The work that the APDC is invaluable, and we recognize that. Additionally, while we think a re-election period is justifiable, we cannot in good faith say that a relection period every 6 months for major committees should be the precedent, and would like to ask other delegates to either reconsider the elections or consider extending the tenure of the committee. For something as major as the ADPC, it requires ongoing attention, monitoring possible deals and service provision is truly a task of consistency.
To add to the discussion of itemization within the ADPC budget and scoping. This seems like this should be a possibly separate proposal. We're not sure how far the ADPC members have delved into possible service providers, etc for a following term, and thus an itemized budget might need to be a follow-up proposal or simply prior to the Tally discussion.
Uh, hard.
ADPC, genuinely in its Phase 1, has done a great job, providing significant structure to the DAO—from the subsidy fund to bringing in audit leaders and external representatives to build a more robust ecosystem.
Uh, hard.
ADPC, genuinely in its Phase 1, has done a great job, providing significant structure to the DAO—from the subsidy fund to bringing in audit leaders and external representatives to build a more robust ecosystem.
I understand that six months is a short time to set a precedent and delegate responsibilities to new members, but I believe this will be important in a future iteration. A clearer breakdown of costs would also be beneficial, as there’s a noticeable increase. Not to mention that due to the token’s devaluation, there’s a higher request in ARB.
All this to say, I’ve decided to vote in favor of this proposal, but I encourage ADPC to take into account the feedback from my colleagues in the comments to address some of the collective needs.
We’re living in challenging times, and security is non-negotiable, but it’s crucial to set precedents and demand accountability for the future.
We are in favor of extending the ADPC's tenure into Phase II because of the impressive foundational work completed in Phase I, which has set a strong precedent for effective procurement for Phase 2. The committee’s focus on transparency and its consistent engagement with the community is also very nice to see.
Expressing some similar concerns, the proposed budget if one. While the overall amount seems reasonable given the expanded scope of Phase II, maybe a more detailed breakdown would make it easier to fully assess the allocation of funds.
Voting "For"
ADPC has demonstrated during Phase 1 they are capable and worth of extending at what seems to be a reasonable price.
Edit: in order to save forum space, I am editing my original comment. to indicate my opinion has not changed since the snapshot vote. As such, I will be voting "for" in tally.
Thank you so much @sid_areta for the detailed answers.
A key organizational challenge we faced was ensuring the alignment of each ADPC member on every major decision. We took some time at the beginning of our tenure to identify the best working model and have managed to streamline our communication and touchpoints over the last 7 months.
We vote Yes - Extend for the proposal on Snapshot.
We appreciate all the work and comprehensive report provided for the Phase I and continuous effort to be made by the experienced actors in the area. However, we echo the concerns by other delegates on bigger scopes and higher compensations to each party (2.5x from the one in Phase I). Also, the detailed breakdown of the budget, especially the below part should be explicitly clarified in the proposal.
Castle appreciates the efforts to address the DAO's needs and has thoroughly reviewed the Phase II proposal. We will be voting Yes in support of the proposal but would like to request further clarification on a few key areas to ensure it fully aligns with the community’s best interests.
Budget Breakdown and Utilization of Funds While the proposal includes a significant request for funds, there is some lack of clarity around the specific breakdown according to the initiatives included. A more detailed budget breakdown would help the community make a well-informed decision. In particular, we would like to understand: • How will the requested funds be allocated across the different initiatives within Phase II? • Regarding the contingency buffer, what criteria will determine when the ADPC can utilize the allocated budget?
Broad Scope of Work We also have concerns that the scope of work outlined in the proposal appears too broad, which could potentially dilute focus and hinder efficient execution. A more targeted approach with clearly defined milestones would enable the DAO community to better monitor progress.
After consideration, the @SEEDgov delegation has decided to “Yes - Extend” on this proposal at the Snapshot vote.
Initially, we had reservations about whether to support the initiative, particularly considering the broad scope, the allocated budget, and the ongoing discussion regarding the re-election of committee members.
Hi @pedrob, first of all thank you very much for taking the time to go through the entire Outcome Report and our proposal in such detail - we hugely appreciate the level of engagement and feedback.
To answer your questions below:
Hi @pedrob, first of all thank you very much for taking the time to go through the entire Outcome Report and our proposal in such detail - we hugely appreciate the level of engagement and feedback.
To answer your questions below:
First, I would like to ask about your work in general as a committee. Do you believe it was efficient? Did you face organizational challenges? Do you think you effectively balanced the decentralization and oversight that a DAO requires with the efficiency needed to execute your tasks? Was it worth implementing the work as a three-member committee? Why continue with that composition? Why not -for instance- concentrate the work on a single member or increase the number to five?
We think that the committee structure worked very well. We had the right mix of teams and skill-sets, with Daimon Legal and Axis Advisory focused on legals and Areta bringing operational and strategy expertise to drive the ADPC forward. Since what we have been attempting is so novel, and no tender process has ever been conducted publicly in the crypto space, we had to build a lot of infrastructure and processes from the ground up. This, of course, presented some challenges, that we outlined in the report, but nothing unusual and think we can proudly say managed and learned from them well.
A second bigger topic is that we also focused quite heavily on transparency and oversight - this can be seen in our comprehensive Notion dashboard and the Outcome Report which you have referred to. While this focus on oversight did require a significant time commitment from the ADPC, we believe it was time well spent as it is the hallmark of a decentralized, public, DAO-native process. A key organizational challenge we faced was ensuring the alignment of each ADPC member on every major decision. We took some time at the beginning of our tenure to identify the best working model and have managed to streamline our communication and touchpoints over the last 7 months.
We also believe that the current 3-parties structure serves the procurement function very well. We have managed to obtain the right mix of skill-sets, as mentioned above, which has allowed us to lay the groundwork to set up further procurement frameworks. A 5-party committee at this point would add further complexity to our operations, and may, to a certain extent, slow down our decision-making and speed of execution, while not being necessary due to the existing mix of skill-sets. On the other hand, boiling the work down to one party would not be feasible since each party does not have the mix of all the skill-sets required to successfully deliver (legal, operational, business strategy, procurement, etc.). We think that a 3-party committee offers sufficient checks and balances while enabling operational efficiency, i.e., it is the correct trade-off between decentralization and efficiency.
My first question is: What are the reasons you identify for not being able to complete the entire work in 6 months?
By the time of the 6 months getting over, we did complete the whitelisting process and have announced 9 whitelisted providers pending KYB and signing of the agreement with the Arbitrum Foundation.
To dive a little deeper into the RFP process, due to the necessity of a robust legal framework for the application processes, the operation of the marketplace and the subsidy grant, we had to create legal documents, including a first-of-its-kind Security Service Panel Head Agreement, the Application Documents, and the Terms and Conditions for the Means Test. These documents took time to create: they had to be drafted from scratch since we had to be very intentional about the type of marketplace structure we wanted to create. We also had to liaise closely and align with the Arbitrum Foundation, who would be the ultimate counterparties to these agreements, since the ADPC does not have a legal entity set up. Due to this dependency, we went through several rounds of iteration and significant time was initially spent developing legal terms in alignment with the Arbitrum Foundation who has its own preferred model terms. This is a key learning we have taken to Phase II, where we will ensure complete alignment with the Foundation before we begin drafting any legal documents.
As an example, I understand that the STEP, without being called a procurement framework committee, did similar work (RFP, applications, selection of service providers, and fund distribution). They completed all the steps in less than 3 months, from the on-chain proposal approval executed in April to the communication of the chosen service providers in June, ultimately approved during the first days of July.
What differences do you identify between your work and the delay compared to theirs?
With regards to the STEP, some of the key differences are that there was no standard legal agreement or legal documentation that STEP had to create. The RFP for STEP was not linked to a legal agreement that had to be signed by each of the providers. With the ADPC, our primary work was to establish this broader, overarching framework that could potentially cover multiple verticals and create a marketplace structure. This was not the same with STEP.
With the ADPC, we had to dedicate a significant amount of time to create the legal frameworks underlying the RFP, which is what led to the process taking more time than that of STEP.
An obvious one is that the Subsidy Fund had to be discussed and voted on separately from the ADPC proposal. I ask, wouldn’t it be better if this temp check included signaling that the DAO intends to allocate “x” amount of resources to those service providers, justifying the procurement framework? That would also give more weight to the budget you’re requesting to carry out that work.
Good point! To clarify, we are not allocating a set budget to each service provider via the Subsidy Fund. The entire size of the Fund is up to $2.5M worth of ARB, and projects looking to build on Arbitrum will apply to the fund to obtain a subsidy up to 70% of the fees charged by the security service providers. Once a project is initially shortlisted on the basis of the Means Test, we will request quotes from each of the whitelisted security service providers, and upon receipt of the quotes, each project will select their preferred provider. The ADPC will then make the final subsidy decisions on the basis of each initially shortlisted project’s preferred provider and their scoring on the Means Test. The initial size of the Subsidy Fund was a decision that we left to the DAO and one that invariably required a lot of discussion amongst contributors and delegates.
We are also not proposing at this stage that separate Subsidy Funds be created for the verticals we tackle in Work Package 1 (RPC Services and Events Providers). By pre-vetting and whitelisting RPC and security service providers in this instance, we want to create standardized pricing and a streamlined model of engagement with these providers for projects in the ecosystem. To illustrate this more clearly, our ideal system would be the following:
Projects looking to obtain a security audit can input a work order outlining their requirements into a quotation system. This work order is forwarded to all whitelisted providers, each of whom respond with their quotes. The projects can then select the quote with the best price, ensuring they obtain better pricing, SLAs, and improved service. Moreover, the contract they will sign with the provider will be under the legal terms created by the ADPC, ensuring a streamlined engagement model.
Would that be the OpEx budget you mention? Another alternative could be that if this temp check is approved, the budget is included before the proposal goes to Tally.
The OpEx budget has a different intention. To give you some context: currently, the DAO cannot utilize the services of the providers whitelisted by the ADPC, be it security service providers from Phase I or RPC providers from Phase II. In case the DAO wants to procure such services, it would be necessary to undergo a fully-fledged governance process, which can be a blocker in certain situations. With the OpEx budget (we definitely have to change the name!), we aim to create a Utilization Rail for the DAO to procure services from the whitelisted providers.
For example, let's assume a budget of $100K is allocated to utilize the services of security service providers as part of this OpEx budget. Let's further assume that there is a proposal which requires a security analysis similar to that performed by OpenZeppelin for the ARDC. With the OpEx budget, the proposal author can apply to (partially) utilize this $100K budget to conduct that security analysis. Following the application, an entity (similar to the DAO Advocate for the ARDC) will need to approve that request. Once the request is approved, a scope is sent to each of the whitelisted security service providers, and each interested provider responds with a quote to perform that service. The DAO Advocate can then choose the best-priced quote for that scope of work.
In Work Package 3, we will draft a proposal for the DAO to assess the creation of individual Utilization Rails for each of the verticals where the ADPC is whitelisting providers - security services, RPCs, and Events. Hopefully this better clarifies the work around the OpEx budget.
On the other hand, if the first procurement framework — the Subsidy Fund — took more than 6 months to complete, why are you requesting a renewal for 6 months to develop double the work — RPC and events providers — instead of, for example, one year?
As outlined above, we can streamline the work to deliver greater output within the same timeframe and a similarly scaled budget by using our learnings from the initial phase and building on top of the groundwork that was laid earlier.
What have you learned from this? What concrete measures will you take to manage your time more efficiently without compromising the culture of transparency and collaboration?
Good question. Our weekly internal calls are necessary for alignment and progression on work tasks. From a community perspective, we think that our bi-weekly ADPC calls are valuable for attendees to update them on our progress. In addition, we constantly updated the Notion hub and ADPC update thread, providing transparency into our operations and progress.
Re. community discussions on proposals, this is an inevitable part of DAO governance and one we believe to be incredibly valuable. As such, we have decided to allocate greater capacity and budget in Phase II to account for the time spent on ensuring a high level of community input and discussion.
I’d like to hear more about that cost-benefit analysis, especially since you’re now requesting $500K USD versus the $144K USD (+ msig funds). The increase is considerable.
Please note that the budget for this proposal is not $500k but $414K, of which $54K is allocated for operational expenses. If this budget for operational expenses is not used, it will be returned to the DAO. That leaves a budget for our work in the amount of $360K. As outlined above, $144K was requested in Phase I to kick-start the pilot phase with one vertical. As further described in the proposal and the Outcome Report, the workload in the ADPC was significantly more time and capacity intensive than priced-in, but taken on by the committee as goodwill to make the engagement work. Since we have now left the initial phase and will provide procurement services for two more verticals in Work Package 1, paired with dedicated value in the additional work packages, while continuing to work on the Security Subsidy Fund, the budget merely reflects the capacity and time spent by the teams.
In terms of cost-benefit, we could negotiate additional discounts and value-adds, better SLAs and improved service scopes from security providers. Bundling the buying and negotiation power of a whole ecosystem compared to individual reach-outs of projects, the approach of utilizing a marketplace to inquire services from a panel of whitelisted providers has allowed us to generate leverage through strategic sourcing methodology. While we cannot quantify this impact yet, given that the Subsidy Fund has not begun yet, we will aim to provide as specific cost-benefit information as soon as possible in our reporting to precisely quantify the cost-benefit.
Hopefully the above responses have been able to answer your questions - please let us know if you require any further clarification!
The following reflects the views of the Lampros Labs DAO governance team, composed of @Blueweb, @Euphoria, and @Nyx, based on our combined research, analysis and ideation.
We're voting FOR this proposal to extend the ADPC's tenure into Phase II.
The following reflects the views of the Lampros Labs DAO governance team, composed of @Blueweb, @Euphoria, and @Nyx, based on our combined research, analysis and ideation.
We're voting FOR this proposal to extend the ADPC's tenure into Phase II.
The team has shown they know what they're doing by successfully completing Phase I, and keeping them on board ensures we maintain that momentum. Their plans for Phase II demonstrate they're ready to keep delivering value, with a well-justified budget and a strong emphasis on transparency that aligns with our DAO's values. We've also been impressed by their regular communication through calls and open discussions throughout Phase I.
To add to this, we agree with Jojo's point about the importance of continuity in this case.
I am strongly against any new election. While I think there could be others that potentially have the knowledge to move this forward (even tho 90% of the lawyerish force of arbitrum is in the parties above), even just the handover, and the reshape of vision, would literally eat on the whole mandate time wise with suboptimal results.
As Jojo mentioned, even just the handover and reshaping of vision for a new team would eat up a lot of the mandate time, leading to suboptimal results. The current team's experience and established processes are valuable assets that will allow them to continue in Phase II.
Overall, we believe that extending the ADPC's tenure is the right move for Arbitrum DAO, allowing for continued progress and efficiency in our procurement process.
we are not serious people. we can't create a procurement committee on the premise that it's members will be elected by the DAO every 6 months and then on the end of the first term don't do an election process and entrench the current members even more, with more scope, and therefor more power. especially for a procurement committee which is a function that concentrates immense power in itself by definition.
we are not serious people. this proposal should not pass no matter how much of a good or bad or incomplete job has been done or not.
We voted YES to extending the ADPC for another 6 month term. We would like to first acknowledge this group’s pioneering efforts — as a DAO Procurement Committee is the first of its kind. We would like to also thank the committee for its laborious work. After reviewing the Outcome Report and attending the most recent ADPC call, it has become more apparent how time and energy intensive it was for the committee to navigate and set-up the required legal infrastructure backbone.
With that said, we would like to echo others concerns about the election procedure. Although we agree that it makes sense for continuity for the committee members to be automatically re-elected, the Tally vote that set up the ADPC does say that members are elected for a term of 6 months. Therefore, at the end of Phase II, we would like to see an election take place.
We look forward to the Phase II deliverables to procure Events Providers and RPC Providers, and would like to see updates made to the DAO throughout the process.
Hi all! In preparation for the Tally vote for Phase II of the ADPC, we wanted to (i) highlight the changes we made to the proposal after the Snapshot vote and (ii) provide further clarifications. These changes and clarifications incorporate the feedback provided by the community and optimize our operations.
Re-Elections
As highlighted in the comment above:
We will make sure that there is a round of elections held prior to any next phase and will drive the preparation ourselves - obviously, we would also appreciate any support from Entropy as the DAO Liaison to make sure expectations and handover are aligned with the DAO’s expectations and best practice. We absolutely have no intention of centralizing any power in the current members and solely proposed re-election for Phase II to enable productivity and efficiency and avoid significant ramp-up costs and time. As such, we want to make it clear that any next iteration of the ADPC includes a well-planned and executed election process.
Budget Breakdown
Based on feedback received from community members, we have provided a detailed breakdown of the budget in the Google sheet here. As mentioned above:
Please note that the breakdown assumes efficiency gains from executing the work packages as proposed. The delivery timelines are based on our project plan and are indicative. If the scope of the proposal is altered, individual budgets will need to be to account for any potential modifications.
ARB Conversion Strategy
We want to ensure that the amount of ARB utilized to obtain the budget of 414,000 USDC is as minimal as possible. Therefore, we have decided to use a Protocol-Owned Execution strategy on Gauntlet’s Aera solution for the conversion mechanism..
Once the ARB is converted into USDC, the Aera vault will utilize LlamaPay to stream the total payment due to the ADPC member wallet addresses over the course of the 6-month period (120k USDC per member, 360k USDC in total). The remainder of the converted funds (54k USDC) will remain in the MSS as the OpEx budget. This process will be coordinated with the MSS chairs and members.
Further details about the ARB conversion strategy and about Aera can be found in the newly added Section XI. ARB Conversion Strategy in the proposal.
ARB Token Calculation
We have updated the final ARB amount required to obtain the budget of 414,000 USDC based on the 14-day Time-Weighted Average Price (TWAP) of ARB/USD, each as listed EOD UTC, until EOD on Thu Sep 19 on CoinGecko (https://www.coingecko.com/en/coins/arbitrum/historical_data).
The TWAP ARB price used has been updated from $0.5425 to $0.5204, and the total amount of ARB requested has been updated from ARB 915,658 to ARB 954,608.
The Tally vote for this proposal will be live from 15.25 UTC on 26 September 2024 to 15.25 UTC on 10 October 2024 here.
We’re looking forward to continuing our efforts in Phase II and would like to thank the community for all the incredibly helpful feedback and engagement on this proposal!
gm, I voted FOR this proposal, acknowledging that:
gm, I voted FOR this proposal, acknowledging that:
However, I would like to challenge the decision to focus on RPC providers for Phase 2. With the launch of a new Orbit chain, we are currently using the free tier options offered by many providers. Based on my experience, this is sufficient for the early stages of ecosystem development. Chains in a growth phase are better positioned to select from a broader range of providers.
If the goal is to support emerging projects, I believe there are other areas where we could achieve greater impact.
A̶d̶d̶i̶t̶i̶o̶n̶a̶l̶l̶y̶, I̶ w̶o̶u̶l̶d̶ l̶i̶k̶e̶ t̶o̶ s̶e̶e̶ t̶h̶e̶ c̶o̶m̶p̶l̶e̶t̶i̶o̶n̶ o̶f̶ t̶h̶e̶ w̶h̶i̶t̶e̶l̶i̶s̶t̶i̶n̶g̶ p̶r̶o̶c̶e̶s̶s̶ f̶r̶o̶m̶ P̶h̶a̶s̶e̶ 1̶, w̶h̶i̶c̶h̶ h̶a̶s̶ n̶o̶t̶ y̶e̶t̶ b̶e̶e̶n̶ f̶u̶l̶l̶y̶ d̶e̶l̶i̶v̶e̶r̶e̶d̶. EDIT: looks like this has been completed
Thank you.
I voted for this extension, so the work is not disrupted, but I have several points to make:
I voted for this extension, so the work is not disrupted, but I have several points to make:
Happy to help in the implementation of those points.
Vote in favor in the coming days. The APDC has done an outstanding job in its duties. While the re-election period is reasonable, we believe that re-electing the main committee every six months should not become the norm. We encourage other representatives to reconsider the election cycle or extend the term, as projects like ADPC require ongoing attention and long-term consistency in monitoring service provision.
Regarding the breakdown of the ADPC budget and scope, we suggest it be presented as a separate proposal, with increased transparency.
DAOplomats is voting in favor of extending the ADPC tenure for another six months.
The work done by the ADPC has been a strong PoC and we would love to see them continue, completing a 12-month term. We also strongly resonate with @JoJo comment on re-election as retaining the current team should enable us to see proper results at the end of the twelve months.
DAOplomats is voting in favor of extending the ADPC tenure for another six months.
The work done by the ADPC has been a strong PoC and we would love to see them continue, completing a 12-month term. We also strongly resonate with @JoJo comment on re-election as retaining the current team should enable us to see proper results at the end of the twelve months.
We would suggest, however, that discussions on Phase III and/or re-elections should start at least two months before the end of Phase II. This would provide ample time for delegates and the community to reflect on the work done by the ADPC and prepare adequately if an election were to happen so there would be no delay in the mandate after Phase II.
Blockworks Research will be voting FOR this proposal on Snapshot.
The work that the APDC is invaluable, and we recognize that. Additionally, while we think a re-election period is justifiable, we cannot in good faith say that a relection period every 6 months for major committees should be the precedent, and would like to ask other delegates to either reconsider the elections or consider extending the tenure of the committee. For something as major as the ADPC, it requires ongoing attention, monitoring possible deals and service provision is truly a task of consistency.
Blockworks Research will be voting FOR this proposal on Snapshot.
The work that the APDC is invaluable, and we recognize that. Additionally, while we think a re-election period is justifiable, we cannot in good faith say that a relection period every 6 months for major committees should be the precedent, and would like to ask other delegates to either reconsider the elections or consider extending the tenure of the committee. For something as major as the ADPC, it requires ongoing attention, monitoring possible deals and service provision is truly a task of consistency.
To add to the discussion of itemization within the ADPC budget and scoping. This seems like this should be a possibly separate proposal. We're not sure how far the ADPC members have delved into possible service providers, etc for a following term, and thus an itemized budget might need to be a follow-up proposal or simply prior to the Tally discussion.
Uh, hard.
ADPC, genuinely in its Phase 1, has done a great job, providing significant structure to the DAO—from the subsidy fund to bringing in audit leaders and external representatives to build a more robust ecosystem.
Uh, hard.
ADPC, genuinely in its Phase 1, has done a great job, providing significant structure to the DAO—from the subsidy fund to bringing in audit leaders and external representatives to build a more robust ecosystem.
I understand that six months is a short time to set a precedent and delegate responsibilities to new members, but I believe this will be important in a future iteration. A clearer breakdown of costs would also be beneficial, as there’s a noticeable increase. Not to mention that due to the token’s devaluation, there’s a higher request in ARB.
All this to say, I’ve decided to vote in favor of this proposal, but I encourage ADPC to take into account the feedback from my colleagues in the comments to address some of the collective needs.
We’re living in challenging times, and security is non-negotiable, but it’s crucial to set precedents and demand accountability for the future.
We are in favor of extending the ADPC's tenure into Phase II because of the impressive foundational work completed in Phase I, which has set a strong precedent for effective procurement for Phase 2. The committee’s focus on transparency and its consistent engagement with the community is also very nice to see.
Expressing some similar concerns, the proposed budget if one. While the overall amount seems reasonable given the expanded scope of Phase II, maybe a more detailed breakdown would make it easier to fully assess the allocation of funds.
Voting "For"
ADPC has demonstrated during Phase 1 they are capable and worth of extending at what seems to be a reasonable price.
Edit: in order to save forum space, I am editing my original comment. to indicate my opinion has not changed since the snapshot vote. As such, I will be voting "for" in tally.
Thank you so much @sid_areta for the detailed answers.
A key organizational challenge we faced was ensuring the alignment of each ADPC member on every major decision. We took some time at the beginning of our tenure to identify the best working model and have managed to streamline our communication and touchpoints over the last 7 months.
We vote Yes - Extend for the proposal on Snapshot.
We appreciate all the work and comprehensive report provided for the Phase I and continuous effort to be made by the experienced actors in the area. However, we echo the concerns by other delegates on bigger scopes and higher compensations to each party (2.5x from the one in Phase I). Also, the detailed breakdown of the budget, especially the below part should be explicitly clarified in the proposal.
Castle appreciates the efforts to address the DAO's needs and has thoroughly reviewed the Phase II proposal. We will be voting Yes in support of the proposal but would like to request further clarification on a few key areas to ensure it fully aligns with the community’s best interests.
Budget Breakdown and Utilization of Funds While the proposal includes a significant request for funds, there is some lack of clarity around the specific breakdown according to the initiatives included. A more detailed budget breakdown would help the community make a well-informed decision. In particular, we would like to understand: • How will the requested funds be allocated across the different initiatives within Phase II? • Regarding the contingency buffer, what criteria will determine when the ADPC can utilize the allocated budget?
Broad Scope of Work We also have concerns that the scope of work outlined in the proposal appears too broad, which could potentially dilute focus and hinder efficient execution. A more targeted approach with clearly defined milestones would enable the DAO community to better monitor progress.
After consideration, the @SEEDgov delegation has decided to “Yes - Extend” on this proposal at the Snapshot vote.
Initially, we had reservations about whether to support the initiative, particularly considering the broad scope, the allocated budget, and the ongoing discussion regarding the re-election of committee members.
Hi @pedrob, first of all thank you very much for taking the time to go through the entire Outcome Report and our proposal in such detail - we hugely appreciate the level of engagement and feedback.
To answer your questions below:
Hi @pedrob, first of all thank you very much for taking the time to go through the entire Outcome Report and our proposal in such detail - we hugely appreciate the level of engagement and feedback.
To answer your questions below:
First, I would like to ask about your work in general as a committee. Do you believe it was efficient? Did you face organizational challenges? Do you think you effectively balanced the decentralization and oversight that a DAO requires with the efficiency needed to execute your tasks? Was it worth implementing the work as a three-member committee? Why continue with that composition? Why not -for instance- concentrate the work on a single member or increase the number to five?
We think that the committee structure worked very well. We had the right mix of teams and skill-sets, with Daimon Legal and Axis Advisory focused on legals and Areta bringing operational and strategy expertise to drive the ADPC forward. Since what we have been attempting is so novel, and no tender process has ever been conducted publicly in the crypto space, we had to build a lot of infrastructure and processes from the ground up. This, of course, presented some challenges, that we outlined in the report, but nothing unusual and think we can proudly say managed and learned from them well.
A second bigger topic is that we also focused quite heavily on transparency and oversight - this can be seen in our comprehensive Notion dashboard and the Outcome Report which you have referred to. While this focus on oversight did require a significant time commitment from the ADPC, we believe it was time well spent as it is the hallmark of a decentralized, public, DAO-native process. A key organizational challenge we faced was ensuring the alignment of each ADPC member on every major decision. We took some time at the beginning of our tenure to identify the best working model and have managed to streamline our communication and touchpoints over the last 7 months.
We also believe that the current 3-parties structure serves the procurement function very well. We have managed to obtain the right mix of skill-sets, as mentioned above, which has allowed us to lay the groundwork to set up further procurement frameworks. A 5-party committee at this point would add further complexity to our operations, and may, to a certain extent, slow down our decision-making and speed of execution, while not being necessary due to the existing mix of skill-sets. On the other hand, boiling the work down to one party would not be feasible since each party does not have the mix of all the skill-sets required to successfully deliver (legal, operational, business strategy, procurement, etc.). We think that a 3-party committee offers sufficient checks and balances while enabling operational efficiency, i.e., it is the correct trade-off between decentralization and efficiency.
My first question is: What are the reasons you identify for not being able to complete the entire work in 6 months?
By the time of the 6 months getting over, we did complete the whitelisting process and have announced 9 whitelisted providers pending KYB and signing of the agreement with the Arbitrum Foundation.
To dive a little deeper into the RFP process, due to the necessity of a robust legal framework for the application processes, the operation of the marketplace and the subsidy grant, we had to create legal documents, including a first-of-its-kind Security Service Panel Head Agreement, the Application Documents, and the Terms and Conditions for the Means Test. These documents took time to create: they had to be drafted from scratch since we had to be very intentional about the type of marketplace structure we wanted to create. We also had to liaise closely and align with the Arbitrum Foundation, who would be the ultimate counterparties to these agreements, since the ADPC does not have a legal entity set up. Due to this dependency, we went through several rounds of iteration and significant time was initially spent developing legal terms in alignment with the Arbitrum Foundation who has its own preferred model terms. This is a key learning we have taken to Phase II, where we will ensure complete alignment with the Foundation before we begin drafting any legal documents.
As an example, I understand that the STEP, without being called a procurement framework committee, did similar work (RFP, applications, selection of service providers, and fund distribution). They completed all the steps in less than 3 months, from the on-chain proposal approval executed in April to the communication of the chosen service providers in June, ultimately approved during the first days of July.
What differences do you identify between your work and the delay compared to theirs?
With regards to the STEP, some of the key differences are that there was no standard legal agreement or legal documentation that STEP had to create. The RFP for STEP was not linked to a legal agreement that had to be signed by each of the providers. With the ADPC, our primary work was to establish this broader, overarching framework that could potentially cover multiple verticals and create a marketplace structure. This was not the same with STEP.
With the ADPC, we had to dedicate a significant amount of time to create the legal frameworks underlying the RFP, which is what led to the process taking more time than that of STEP.
An obvious one is that the Subsidy Fund had to be discussed and voted on separately from the ADPC proposal. I ask, wouldn’t it be better if this temp check included signaling that the DAO intends to allocate “x” amount of resources to those service providers, justifying the procurement framework? That would also give more weight to the budget you’re requesting to carry out that work.
Good point! To clarify, we are not allocating a set budget to each service provider via the Subsidy Fund. The entire size of the Fund is up to $2.5M worth of ARB, and projects looking to build on Arbitrum will apply to the fund to obtain a subsidy up to 70% of the fees charged by the security service providers. Once a project is initially shortlisted on the basis of the Means Test, we will request quotes from each of the whitelisted security service providers, and upon receipt of the quotes, each project will select their preferred provider. The ADPC will then make the final subsidy decisions on the basis of each initially shortlisted project’s preferred provider and their scoring on the Means Test. The initial size of the Subsidy Fund was a decision that we left to the DAO and one that invariably required a lot of discussion amongst contributors and delegates.
We are also not proposing at this stage that separate Subsidy Funds be created for the verticals we tackle in Work Package 1 (RPC Services and Events Providers). By pre-vetting and whitelisting RPC and security service providers in this instance, we want to create standardized pricing and a streamlined model of engagement with these providers for projects in the ecosystem. To illustrate this more clearly, our ideal system would be the following:
Projects looking to obtain a security audit can input a work order outlining their requirements into a quotation system. This work order is forwarded to all whitelisted providers, each of whom respond with their quotes. The projects can then select the quote with the best price, ensuring they obtain better pricing, SLAs, and improved service. Moreover, the contract they will sign with the provider will be under the legal terms created by the ADPC, ensuring a streamlined engagement model.
Would that be the OpEx budget you mention? Another alternative could be that if this temp check is approved, the budget is included before the proposal goes to Tally.
The OpEx budget has a different intention. To give you some context: currently, the DAO cannot utilize the services of the providers whitelisted by the ADPC, be it security service providers from Phase I or RPC providers from Phase II. In case the DAO wants to procure such services, it would be necessary to undergo a fully-fledged governance process, which can be a blocker in certain situations. With the OpEx budget (we definitely have to change the name!), we aim to create a Utilization Rail for the DAO to procure services from the whitelisted providers.
For example, let's assume a budget of $100K is allocated to utilize the services of security service providers as part of this OpEx budget. Let's further assume that there is a proposal which requires a security analysis similar to that performed by OpenZeppelin for the ARDC. With the OpEx budget, the proposal author can apply to (partially) utilize this $100K budget to conduct that security analysis. Following the application, an entity (similar to the DAO Advocate for the ARDC) will need to approve that request. Once the request is approved, a scope is sent to each of the whitelisted security service providers, and each interested provider responds with a quote to perform that service. The DAO Advocate can then choose the best-priced quote for that scope of work.
In Work Package 3, we will draft a proposal for the DAO to assess the creation of individual Utilization Rails for each of the verticals where the ADPC is whitelisting providers - security services, RPCs, and Events. Hopefully this better clarifies the work around the OpEx budget.
On the other hand, if the first procurement framework — the Subsidy Fund — took more than 6 months to complete, why are you requesting a renewal for 6 months to develop double the work — RPC and events providers — instead of, for example, one year?
As outlined above, we can streamline the work to deliver greater output within the same timeframe and a similarly scaled budget by using our learnings from the initial phase and building on top of the groundwork that was laid earlier.
What have you learned from this? What concrete measures will you take to manage your time more efficiently without compromising the culture of transparency and collaboration?
Good question. Our weekly internal calls are necessary for alignment and progression on work tasks. From a community perspective, we think that our bi-weekly ADPC calls are valuable for attendees to update them on our progress. In addition, we constantly updated the Notion hub and ADPC update thread, providing transparency into our operations and progress.
Re. community discussions on proposals, this is an inevitable part of DAO governance and one we believe to be incredibly valuable. As such, we have decided to allocate greater capacity and budget in Phase II to account for the time spent on ensuring a high level of community input and discussion.
I’d like to hear more about that cost-benefit analysis, especially since you’re now requesting $500K USD versus the $144K USD (+ msig funds). The increase is considerable.
Please note that the budget for this proposal is not $500k but $414K, of which $54K is allocated for operational expenses. If this budget for operational expenses is not used, it will be returned to the DAO. That leaves a budget for our work in the amount of $360K. As outlined above, $144K was requested in Phase I to kick-start the pilot phase with one vertical. As further described in the proposal and the Outcome Report, the workload in the ADPC was significantly more time and capacity intensive than priced-in, but taken on by the committee as goodwill to make the engagement work. Since we have now left the initial phase and will provide procurement services for two more verticals in Work Package 1, paired with dedicated value in the additional work packages, while continuing to work on the Security Subsidy Fund, the budget merely reflects the capacity and time spent by the teams.
In terms of cost-benefit, we could negotiate additional discounts and value-adds, better SLAs and improved service scopes from security providers. Bundling the buying and negotiation power of a whole ecosystem compared to individual reach-outs of projects, the approach of utilizing a marketplace to inquire services from a panel of whitelisted providers has allowed us to generate leverage through strategic sourcing methodology. While we cannot quantify this impact yet, given that the Subsidy Fund has not begun yet, we will aim to provide as specific cost-benefit information as soon as possible in our reporting to precisely quantify the cost-benefit.
Hopefully the above responses have been able to answer your questions - please let us know if you require any further clarification!
The following reflects the views of the Lampros Labs DAO governance team, composed of @Blueweb, @Euphoria, and @Nyx, based on our combined research, analysis and ideation.
We're voting FOR this proposal to extend the ADPC's tenure into Phase II.
The following reflects the views of the Lampros Labs DAO governance team, composed of @Blueweb, @Euphoria, and @Nyx, based on our combined research, analysis and ideation.
We're voting FOR this proposal to extend the ADPC's tenure into Phase II.
The team has shown they know what they're doing by successfully completing Phase I, and keeping them on board ensures we maintain that momentum. Their plans for Phase II demonstrate they're ready to keep delivering value, with a well-justified budget and a strong emphasis on transparency that aligns with our DAO's values. We've also been impressed by their regular communication through calls and open discussions throughout Phase I.
To add to this, we agree with Jojo's point about the importance of continuity in this case.
I am strongly against any new election. While I think there could be others that potentially have the knowledge to move this forward (even tho 90% of the lawyerish force of arbitrum is in the parties above), even just the handover, and the reshape of vision, would literally eat on the whole mandate time wise with suboptimal results.
As Jojo mentioned, even just the handover and reshaping of vision for a new team would eat up a lot of the mandate time, leading to suboptimal results. The current team's experience and established processes are valuable assets that will allow them to continue in Phase II.
Overall, we believe that extending the ADPC's tenure is the right move for Arbitrum DAO, allowing for continued progress and efficiency in our procurement process.
we are not serious people. we can't create a procurement committee on the premise that it's members will be elected by the DAO every 6 months and then on the end of the first term don't do an election process and entrench the current members even more, with more scope, and therefor more power. especially for a procurement committee which is a function that concentrates immense power in itself by definition.
we are not serious people. this proposal should not pass no matter how much of a good or bad or incomplete job has been done or not.
We are in favor of extending the ADPC's tenure into Phase II because of the impressive foundational work completed in Phase I, which has set a strong precedent for effective procurement for Phase 2. The committee’s focus on transparency and its consistent engagement with the community is also very nice to see.
Expressing some similar concerns, the proposed budget if one. While the overall amount seems reasonable given the expanded scope of Phase II, maybe a more detailed breakdown would make it easier to fully assess the allocation of funds.
Overall, we believe the continuation of the current committee is crucial for maintaining the momentum and achieving the DAO’s long-term goals.
Thank you so much @sid_areta for the detailed answers.
A key organizational challenge we faced was ensuring the alignment of each ADPC member on every major decision. We took some time at the beginning of our tenure to identify the best working model and have managed to streamline our communication and touchpoints over the last 7 months.
I find this statement particularly interesting. I would like to know more about what kind of differences you had, the options for working models, and which one and why you chose it. Of course, it is not necessary to answer this right now. I think your experience will serve as an example for future committees.
We are also not proposing at this stage that separate Subsidy Funds be created for the verticals we tackle in Work Package 1 (RPC Services and Events Providers).
The reasons for not doing it now are unclear to me. I understand that there have been conversations with key stakeholders, but I don’t understand why we wouldn’t discuss or vote on the funds the DAO intends to allocate to these new Subsidy Funds before proceeding with the procurement work and legal agreements. My main concern is that the DAO might spend resources and time on this work, only for it to lose meaning later if the DAO either doesn’t agree on the amount to allocate or simply decides not to go through with it.
Since the deadline is approaching, I will vote FOR the continuation of the committee as a signal of support for the work done and the rationale behind the proposal.
However, for my support in Tally, I would like to see two things: first, a discussion about the amounts to be allocated to the new subsidy funds, and second, a clearer breakdown of the tasks and allocation of resources. I agree, and have experienced with the LTIPP, that the workload in a DAO is often much greater than expected when planning, so it's reasonable to increase the value for all the work to be done. However, I would still like to see a detailed justification of how this is being accounted for
We vote Yes - Extend for the proposal on Snapshot.
We appreciate all the work and comprehensive report provided for the Phase I and continuous effort to be made by the experienced actors in the area. However, we echo the concerns by other delegates on bigger scopes and higher compensations to each party (2.5x from the one in Phase I). Also, the detailed breakdown of the budget, especially the below part should be explicitly clarified in the proposal.
We will allocate the $60k equally across each party of the ADPC. I.e., each of Areta, Axis Advisory, and Daimon Legal and their dedicated teams will be allocated $20k each per month.
On the election, it makes sense to keep the current members because of the nature of the work that requires speciality and continuity, but as the currently selected members are less motivated to work on elections in the future, we would like to see another party (Entropy or Foundation?) to oversee the process and operations of the election for the next term if possible.
Castle appreciates the efforts to address the DAO's needs and has thoroughly reviewed the Phase II proposal. We will be voting Yes in support of the proposal but would like to request further clarification on a few key areas to ensure it fully aligns with the community’s best interests.
Budget Breakdown and Utilization of Funds While the proposal includes a significant request for funds, there is some lack of clarity around the specific breakdown according to the initiatives included. A more detailed budget breakdown would help the community make a well-informed decision. In particular, we would like to understand: • How will the requested funds be allocated across the different initiatives within Phase II? • Regarding the contingency buffer, what criteria will determine when the ADPC can utilize the allocated budget?
Broad Scope of Work We also have concerns that the scope of work outlined in the proposal appears too broad, which could potentially dilute focus and hinder efficient execution. A more targeted approach with clearly defined milestones would enable the DAO community to better monitor progress.
We appreciate the hard work that has gone into this proposal and look forward to further clarifications
After consideration, the @SEEDgov delegation has decided to “Yes - Extend” on this proposal at the Snapshot vote.
Initially, we had reservations about whether to support the initiative, particularly considering the broad scope, the allocated budget, and the ongoing discussion regarding the re-election of committee members.
In this case, we align with @JoJo’s view that it is premature to rotate these positions after only six months—a shortcoming in the original proposal. We hope to see an annual initiative developed to provide greater predictability and more time to assess the committee’s results.
That said, we choose to extend a vote of confidence to the committee, as we appreciate the work accomplished thus far.
I voted YES to extend the proposal to phase two. Having a committee to oversee and manage external providers that we can trust is necessary. The team behind it seems very capable and trustworthy. The budget seems fair based on the scale and size of the proposal.
We are supporting the extension of the ADPC due to the significant progress demonstrated in Phase I, particularly in establishing critical procurement frameworks and promoting transparency within the DAO. The committee’s foundational work in the whitelisting process for security providers and their active community engagement are essential to ensuring accountability and operational efficiency.
Step by step, Phase by phase.
Step by step, Phase by phase.
And re-election of the current ADPC members is the my most favorite part. :grinning:
gm!
Thank you very much for the proposal and congratulations on the work accomplished over the past months.
gm!
Thank you very much for the proposal and congratulations on the work accomplished over the past months.
I've taken some time to review both the Phase I final report and the new proposal. I believe you've done a great job, and the DAO should pay special attention to Section VI, "Complexities," and Section VII, "Key Learnings and Recommendations," as they are crucial for the future of all committees that will be formed.
That being said, I have several questions that overlap somewhat between the information provided in the Phase 1 report and the proposal for Phase 2, as well as some unrelated to the proposal itself but relevant to its operations.
First, I would like to ask about your work in general as a committee. Do you believe it was efficient? Did you face organizational challenges? Do you think you effectively balanced the decentralization and oversight that a DAO requires with the efficiency needed to execute your tasks? Was it worth implementing the work as a three-member committee? Why continue with that composition? Why not -for instance- concentrate the work on a single member or increase the number to five?
Regarding your Phase I Report and the Phase II proposal
In the introduction of the Phase 1 report, you highlight:
This report highlights our successes in establishing groundbreaking procurement frameworks, fostering community engagement, and laying a strong foundation for the future of decentralized procurement within the Arbitrum ecosystem.
Regarding the procurement frameworks, -which is definitely the most important according to the mandate — I notice that the work is still unfinished:
The development and implementation of the procurement framework for security-oriented service providers was a primary mandate for the ADPC. We are pleased to report significant progress in this mandate, with the finalization of extensive RFP documentation, the evaluation of twelve received submissions, of which we have moved 9 to the last phase of the whitelisting process subject to finalizing legal agreements and resolving a few outstanding questions, and the anticipated completion of the whitelisting process in August.
We are currently in the review period evaluating 12 security service providers and expect to execute the agreements necessary for enabling engagement in September 2024
My first question is: What are the reasons you identify for not being able to complete the entire work in 6 months?
As an example, I understand that the STEP, without being called a procurement framework committee, did similar work (RFP, applications, selection of service providers, and fund distribution). They completed all the steps in less than 3 months, from the on-chain proposal approval executed in April to the communication of the chosen service providers in June, ultimately approved during the first days of July.
What differences do you identify between your work and the delay compared to theirs? An obvious one is that the Subsidy Fund had to be discussed and voted on separately from the ADPC proposal. I ask, wouldn’t it be better if this temp check included signaling that the DAO intends to allocate "x" amount of resources to those service providers, justifying the procurement framework? That would also give more weight to the budget you're requesting to carry out that work.
Would that be the OpEx budget you mention? Another alternative could be that if this temp check is approved, the budget is included before the proposal goes to Tally.
On the other hand, if the first procurement framework — the Subsidy Fund — took more than 6 months to complete, why are you requesting a renewal for 6 months to develop double the work — RPC and events providers — instead of, for example, one year?
Regarding community engagement, in the report you highlight:
Throughout its initial term, the ADPC prioritized active engagement with the Arbitrum community, fostering a culture of transparency and collaboration
But then you mention it as a situation that took more time and effort than you initially expected
Unexpected community engagement demands
The high level of community input and discussion, especially surrounding the subsidy fund, required significantly more time and resources for management and response than initially planned
What have you learned from this? What concrete measures will you take to manage your time more efficiently without compromising the culture of transparency and collaboration?
For example, according to your Notion notes, the public bi-weekly calls are only attended by ADPC members (which is definitely not your fault). Couldn’t something more efficient and less time-consuming be done so that the information is available without having to prepare so many calls? What do you think?
Regarding the budget for Phase 1, in the introduction of the report, you mention a cost-benefit analysis:
An overview of the ADPC’s budget utilization and a cost-benefit analysis of its activities during the 6-month period.
which is not followed up in Section IV (Financial Review). Only the distribution of funds is mentioned. (Or did I miss it?)
I’d like to hear more about that cost-benefit analysis, especially since you're now requesting $500K USD versus the $144K USD (+ msig funds). The increase is considerable.
What is the cost-benefit analysis of the DAO investing half a million dollars in procurement frameworks? Have you conducted any analysis? For example, could you perform this exercise based on the results of Phase 1? How much do you estimate the DAO will save due to the work done in whitelisting security service providers?
Final comment.
I understand that I’ve asked many questions that could have been addressed when the Phase 1 report was shared, so I apologize for the timing. I also understand if you’re unable to answer them before the snapshot ends.
I truly admire the work you’ve done. If I’m able to ask so many questions, it’s because you’ve provided a lot of information about what you’ve done, and your work is of high quality. I really like the structure of your reports. Thank you so much for everything.
I’m voting in favor of this proposal. Imo the budget is reasonable and it allows the Procurement Committee to pursue the work they have been doing for the past months. Concerning the automatic re-election of members, I’ve already expressed my opinion in favor in a past comment on the forum (https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/21)
Overall, APDC has established a procurement framework, conducted benchmark evaluations of security providers, and passed a proposal to fund security subsidies, continuing the work and processes from Phase 1. I believe they are trustworthy and commendable. At the same time, I think it's necessary to hold a work progress communication and summary every two months and make it public.
Generally in favor of the proposal Reasons
I will be voting for the proposal to extend the ADPC’s tenure into Phase II on Snapshot.
The ADPC has proven its effectiveness in Phase I, delivering tangible benefits like cost savings and establishing essential procurement frameworks. The plans for Phase II show they're ready to keep delivering value, and the proposed budget is well-justified with the committee’s emphasis on transparency ensuring continued alignment with DAO values. Keeping the same team ensures continuity, they've already shown they know what they're doing, so it makes sense to let them keep the momentum going in Phase II.
Strongly voting "for" on this proposal.
ADPC created one of a kinda entity in arbitrum and I think in crypto in general, and goes in what I think is an extremely good direction for high decentralized orgs like our dao: bridge well known framework and way to solve problems from more traditional industries to ours.
Strongly voting "for" on this proposal.
ADPC created one of a kinda entity in arbitrum and I think in crypto in general, and goes in what I think is an extremely good direction for high decentralized orgs like our dao: bridge well known framework and way to solve problems from more traditional industries to ours.
We don't need to reinvent the wheel everytime, we can easily adapt what already exists in professional world into crypto, with a tailoring for the specific tools and needs we have, and this is what is happening here in my opinion.
I also like the expantion in scope, and I partially share the concern of @Frisson about it potentially be a big too big as workload; at the same time, knowing the parties involved, I think they can pull it off.
As a final note, in this case, like in the stylus sprint, I am strongly against any new election. While I think there could be others that potentially have the knowledge to move this forward (even tho 90% of the lawyerish force of arbitrum is in the parties above), even just the handover, and the reshape of vision, would literally eat on the whole mandate time wise with suboptimal results.
Hi @raam thanks for the comment!
We’re fully aligned with providing clarity around this. This proposal does not aim to permanently change the ADPC election process that was established in the previous Tally vote. Our opinion, which is echoed by @JoJo and @0x_ultra, is that extending the tenure of the current members of the ADPC for this Phase II is the most effective and efficient use of resources for the DAO.
ADPC has done a lot of outstanding work for Arbitrum DAO over the past few months, and I am very grateful to it. In fact, I fully support the proposal, because a good thing needs to be sustainable, and it makes sense to have the necessary budget to accomplish it. I have carefully reviewed the budget mentioned in the proposal, and I think it is relatively reasonable, and there is no over-exaggeration.
Another small question about the 2025 strategy You wrote that it is being prepared, but when will it be presented and suddenly there won't be enough $360k for it?
I will be voted for because this proposal is ideal to simplify communication about the ADPC through clear summaries and promote it on social media. This would increase community understanding and participation. Additionally, greater flexibility in budgeting would allow adaptation to new opportunities, enhancing efficiency in the long term.
Hey @sid_areta, thank you for the response. We understand that the scope for Phase II has expanded to cover more verticals and may require additional time and resources. For this reason, we voted FOR this proposal on Snapshot.
I'm glad you updated your proposal based on community feedback. I especially welcome the re-election as one of the promises being fulfilled.
Hi all,
Thank you so much for you taking the time to provide feedback. We appreciate the level of engagement and alignment on key items! Below, we list some of the amendments to the proposal.
Hi all,
Thank you so much for you taking the time to provide feedback. We appreciate the level of engagement and alignment on key items! Below, we list some of the amendments to the proposal.
This proposal will be live on Snapshot from 11.00 UTC on Sep 5 to 11.00 UTC on Sep 12. You can find the Snapshot link here. Please vote!
Hi @Avantgarde, appreciate the time digesting the proposal and positive feedback. Find some details below:
(1) Re. the OpEx budget:
Regarding the OpEx budget - can you provide any insight into the oversight mechanisms for this budget? e.g., how the MSS will ensure transparency and accountability in spending and what processes will be in place to report back to the DAO on fund utilisation?
Hi @KlausBrave, appreciate you reading through the proposal. Since events are a selected vertical and what we propose is complementary to the GovHack format, it's very useful to get your view as the main event organizer for the DAO!
Let us clarify some of the questions below:
Hi @KlausBrave, appreciate you reading through the proposal. Since events are a selected vertical and what we propose is complementary to the GovHack format, it's very useful to get your view as the main event organizer for the DAO!
Let us clarify some of the questions below:
How does the work load and costs to provide this scale to handle 3 verticals? Can you detail now for 3 verticals how you arrive at the $360k amount?
Tagging @PennBlockchain here as they had a similar question (also thanks for reviewing!).
In Phase I we used $144k to complete one vertical, and as stated in the proposal, the workload in the ADPC was significantly more time and capacity intensive than priced-in, but taken on by the committee as goodwill to make it work. Since we have now left the initial phase and will provide procurement services for two more verticals in Work Package 1, paired with dedicated value in the additional work packages, the budget merely reflects the capacity and time spent by the teams. Using our learnings from the initial phase, we plan to streamline the work to deliver greater output within the same timeframe and a similarly scaled budget.
We will allocate the $60k equally across each party of the ADPC. I.e., each of Areta, Axis Advisory, and Daimon Legal and their dedicated teams will be allocated $20k each per month.
Lastly, just wanted to add a bit of an explainer around the OpEx budget as per @PennBlockchain’s question. Quoting from the proposal:
This budget is designed to streamline the DAO’s interaction with ADPC-whitelisted service providers by creating a direct utilization rail. This rail will allow DAO initiatives and contributors to access and utilize these pre-approved service providers without undergoing the cumbersome proposal process for each engagement. The OpEx budget essentially bypasses the bureaucratic hurdles that currently plague the DAO’s procurement process, enabling a more agile and responsive operational framework.
As it stands and should the proposal be accepted, the DAO would then be able to solicit services re. Events, Security, and RPCs by the end of next term. Naturally as we scale our procurement efforts, the options will correspondingly increase.
Lastly, are funds distributed as a 1 off upfront payment or paid monthly, this level of detail is not in the proposal.
We have added further detail around the funding mechanism into the proposal and updated it to OTC the entire requested amount into USDC upon receipt of the ARB and return the unutilized ARB to the DAO treasury. This is intended to avoid fluctuations in ARB price and ensures that the ADPC avoids using the buffer as much as possible. As such, monthly payments to the ADPC will be made in USDC instead of having to convert the ARB to USDC at the end of each month.
ranked choice voting on snapshot for which verticals are chosen next (as I under it the rank and selection was arrived at from 1-1s with delegates, but there was no option for wider global delegate input in this process, correct me if I am misunderstanding)
Great idea - also one we discussed intensively within the ADPC and delegates. We reached out to 25 delegates and stakeholders directly and via survey for their feedback. We found this to be the most effective process for balancing the high level of context needed for this decision while incorporating as many views from different stakeholders as possible. We have also already started working with Entropy and DisruptionJoe on the Events proposal to ensure that the DAO is able to have a sufficient presence at the larger events in H1 2025. However, your suggestion is well taken - if there is consensus on the DAO wanting to vote individually on the verticals and outsource this decision, we are happy to facilitate this process.
Selecting vertical leads (for RPC and Events) this should be an open process after the vertical is chosen for candidates to respond to and be selected for who is the vertical lead / manager
Could you please expand on what you mean by vertical leads here and what their responsibilities would be?
Good question, and an important point to clarify to avoid confusion - there will be no vertical leads in the sense of dedicated leaders owning any of the verticals. The essence of our process will be to run an open RFP process, giving different providers the opportunity to offer their services and providing the DAO with the most effective access to high-quality services at comparable rates.
We are in favor of extending the ADPC's tenure into Phase II because of the impressive foundational work completed in Phase I, which has set a strong precedent for effective procurement for Phase 2. The committee’s focus on transparency and its consistent engagement with the community is also very nice to see.
Expressing some similar concerns, the proposed budget if one. While the overall amount seems reasonable given the expanded scope of Phase II, maybe a more detailed breakdown would make it easier to fully assess the allocation of funds.
Overall, we believe the continuation of the current committee is crucial for maintaining the momentum and achieving the DAO’s long-term goals.
Thank you so much @sid_areta for the detailed answers.
A key organizational challenge we faced was ensuring the alignment of each ADPC member on every major decision. We took some time at the beginning of our tenure to identify the best working model and have managed to streamline our communication and touchpoints over the last 7 months.
I find this statement particularly interesting. I would like to know more about what kind of differences you had, the options for working models, and which one and why you chose it. Of course, it is not necessary to answer this right now. I think your experience will serve as an example for future committees.
We are also not proposing at this stage that separate Subsidy Funds be created for the verticals we tackle in Work Package 1 (RPC Services and Events Providers).
The reasons for not doing it now are unclear to me. I understand that there have been conversations with key stakeholders, but I don’t understand why we wouldn’t discuss or vote on the funds the DAO intends to allocate to these new Subsidy Funds before proceeding with the procurement work and legal agreements. My main concern is that the DAO might spend resources and time on this work, only for it to lose meaning later if the DAO either doesn’t agree on the amount to allocate or simply decides not to go through with it.
Since the deadline is approaching, I will vote FOR the continuation of the committee as a signal of support for the work done and the rationale behind the proposal.
However, for my support in Tally, I would like to see two things: first, a discussion about the amounts to be allocated to the new subsidy funds, and second, a clearer breakdown of the tasks and allocation of resources. I agree, and have experienced with the LTIPP, that the workload in a DAO is often much greater than expected when planning, so it's reasonable to increase the value for all the work to be done. However, I would still like to see a detailed justification of how this is being accounted for
We vote Yes - Extend for the proposal on Snapshot.
We appreciate all the work and comprehensive report provided for the Phase I and continuous effort to be made by the experienced actors in the area. However, we echo the concerns by other delegates on bigger scopes and higher compensations to each party (2.5x from the one in Phase I). Also, the detailed breakdown of the budget, especially the below part should be explicitly clarified in the proposal.
We will allocate the $60k equally across each party of the ADPC. I.e., each of Areta, Axis Advisory, and Daimon Legal and their dedicated teams will be allocated $20k each per month.
On the election, it makes sense to keep the current members because of the nature of the work that requires speciality and continuity, but as the currently selected members are less motivated to work on elections in the future, we would like to see another party (Entropy or Foundation?) to oversee the process and operations of the election for the next term if possible.
Castle appreciates the efforts to address the DAO's needs and has thoroughly reviewed the Phase II proposal. We will be voting Yes in support of the proposal but would like to request further clarification on a few key areas to ensure it fully aligns with the community’s best interests.
Budget Breakdown and Utilization of Funds While the proposal includes a significant request for funds, there is some lack of clarity around the specific breakdown according to the initiatives included. A more detailed budget breakdown would help the community make a well-informed decision. In particular, we would like to understand: • How will the requested funds be allocated across the different initiatives within Phase II? • Regarding the contingency buffer, what criteria will determine when the ADPC can utilize the allocated budget?
Broad Scope of Work We also have concerns that the scope of work outlined in the proposal appears too broad, which could potentially dilute focus and hinder efficient execution. A more targeted approach with clearly defined milestones would enable the DAO community to better monitor progress.
We appreciate the hard work that has gone into this proposal and look forward to further clarifications
After consideration, the @SEEDgov delegation has decided to “Yes - Extend” on this proposal at the Snapshot vote.
Initially, we had reservations about whether to support the initiative, particularly considering the broad scope, the allocated budget, and the ongoing discussion regarding the re-election of committee members.
In this case, we align with @JoJo’s view that it is premature to rotate these positions after only six months—a shortcoming in the original proposal. We hope to see an annual initiative developed to provide greater predictability and more time to assess the committee’s results.
That said, we choose to extend a vote of confidence to the committee, as we appreciate the work accomplished thus far.
I voted YES to extend the proposal to phase two. Having a committee to oversee and manage external providers that we can trust is necessary. The team behind it seems very capable and trustworthy. The budget seems fair based on the scale and size of the proposal.
We are supporting the extension of the ADPC due to the significant progress demonstrated in Phase I, particularly in establishing critical procurement frameworks and promoting transparency within the DAO. The committee’s foundational work in the whitelisting process for security providers and their active community engagement are essential to ensuring accountability and operational efficiency.
Step by step, Phase by phase.
Step by step, Phase by phase.
And re-election of the current ADPC members is the my most favorite part. :grinning:
gm!
Thank you very much for the proposal and congratulations on the work accomplished over the past months.
gm!
Thank you very much for the proposal and congratulations on the work accomplished over the past months.
I've taken some time to review both the Phase I final report and the new proposal. I believe you've done a great job, and the DAO should pay special attention to Section VI, "Complexities," and Section VII, "Key Learnings and Recommendations," as they are crucial for the future of all committees that will be formed.
That being said, I have several questions that overlap somewhat between the information provided in the Phase 1 report and the proposal for Phase 2, as well as some unrelated to the proposal itself but relevant to its operations.
First, I would like to ask about your work in general as a committee. Do you believe it was efficient? Did you face organizational challenges? Do you think you effectively balanced the decentralization and oversight that a DAO requires with the efficiency needed to execute your tasks? Was it worth implementing the work as a three-member committee? Why continue with that composition? Why not -for instance- concentrate the work on a single member or increase the number to five?
Regarding your Phase I Report and the Phase II proposal
In the introduction of the Phase 1 report, you highlight:
This report highlights our successes in establishing groundbreaking procurement frameworks, fostering community engagement, and laying a strong foundation for the future of decentralized procurement within the Arbitrum ecosystem.
Regarding the procurement frameworks, -which is definitely the most important according to the mandate — I notice that the work is still unfinished:
The development and implementation of the procurement framework for security-oriented service providers was a primary mandate for the ADPC. We are pleased to report significant progress in this mandate, with the finalization of extensive RFP documentation, the evaluation of twelve received submissions, of which we have moved 9 to the last phase of the whitelisting process subject to finalizing legal agreements and resolving a few outstanding questions, and the anticipated completion of the whitelisting process in August.
We are currently in the review period evaluating 12 security service providers and expect to execute the agreements necessary for enabling engagement in September 2024
My first question is: What are the reasons you identify for not being able to complete the entire work in 6 months?
As an example, I understand that the STEP, without being called a procurement framework committee, did similar work (RFP, applications, selection of service providers, and fund distribution). They completed all the steps in less than 3 months, from the on-chain proposal approval executed in April to the communication of the chosen service providers in June, ultimately approved during the first days of July.
What differences do you identify between your work and the delay compared to theirs? An obvious one is that the Subsidy Fund had to be discussed and voted on separately from the ADPC proposal. I ask, wouldn’t it be better if this temp check included signaling that the DAO intends to allocate "x" amount of resources to those service providers, justifying the procurement framework? That would also give more weight to the budget you're requesting to carry out that work.
Would that be the OpEx budget you mention? Another alternative could be that if this temp check is approved, the budget is included before the proposal goes to Tally.
On the other hand, if the first procurement framework — the Subsidy Fund — took more than 6 months to complete, why are you requesting a renewal for 6 months to develop double the work — RPC and events providers — instead of, for example, one year?
Regarding community engagement, in the report you highlight:
Throughout its initial term, the ADPC prioritized active engagement with the Arbitrum community, fostering a culture of transparency and collaboration
But then you mention it as a situation that took more time and effort than you initially expected
Unexpected community engagement demands
The high level of community input and discussion, especially surrounding the subsidy fund, required significantly more time and resources for management and response than initially planned
What have you learned from this? What concrete measures will you take to manage your time more efficiently without compromising the culture of transparency and collaboration?
For example, according to your Notion notes, the public bi-weekly calls are only attended by ADPC members (which is definitely not your fault). Couldn’t something more efficient and less time-consuming be done so that the information is available without having to prepare so many calls? What do you think?
Regarding the budget for Phase 1, in the introduction of the report, you mention a cost-benefit analysis:
An overview of the ADPC’s budget utilization and a cost-benefit analysis of its activities during the 6-month period.
which is not followed up in Section IV (Financial Review). Only the distribution of funds is mentioned. (Or did I miss it?)
I’d like to hear more about that cost-benefit analysis, especially since you're now requesting $500K USD versus the $144K USD (+ msig funds). The increase is considerable.
What is the cost-benefit analysis of the DAO investing half a million dollars in procurement frameworks? Have you conducted any analysis? For example, could you perform this exercise based on the results of Phase 1? How much do you estimate the DAO will save due to the work done in whitelisting security service providers?
Final comment.
I understand that I’ve asked many questions that could have been addressed when the Phase 1 report was shared, so I apologize for the timing. I also understand if you’re unable to answer them before the snapshot ends.
I truly admire the work you’ve done. If I’m able to ask so many questions, it’s because you’ve provided a lot of information about what you’ve done, and your work is of high quality. I really like the structure of your reports. Thank you so much for everything.
I’m voting in favor of this proposal. Imo the budget is reasonable and it allows the Procurement Committee to pursue the work they have been doing for the past months. Concerning the automatic re-election of members, I’ve already expressed my opinion in favor in a past comment on the forum (https://forum.arbitrum.foundation/t/arbitrum-dao-procurement-committee-phase-ii-proposal/26441/21)
Overall, APDC has established a procurement framework, conducted benchmark evaluations of security providers, and passed a proposal to fund security subsidies, continuing the work and processes from Phase 1. I believe they are trustworthy and commendable. At the same time, I think it's necessary to hold a work progress communication and summary every two months and make it public.
Generally in favor of the proposal Reasons
I will be voting for the proposal to extend the ADPC’s tenure into Phase II on Snapshot.
The ADPC has proven its effectiveness in Phase I, delivering tangible benefits like cost savings and establishing essential procurement frameworks. The plans for Phase II show they're ready to keep delivering value, and the proposed budget is well-justified with the committee’s emphasis on transparency ensuring continued alignment with DAO values. Keeping the same team ensures continuity, they've already shown they know what they're doing, so it makes sense to let them keep the momentum going in Phase II.
Strongly voting "for" on this proposal.
ADPC created one of a kinda entity in arbitrum and I think in crypto in general, and goes in what I think is an extremely good direction for high decentralized orgs like our dao: bridge well known framework and way to solve problems from more traditional industries to ours.
Strongly voting "for" on this proposal.
ADPC created one of a kinda entity in arbitrum and I think in crypto in general, and goes in what I think is an extremely good direction for high decentralized orgs like our dao: bridge well known framework and way to solve problems from more traditional industries to ours.
We don't need to reinvent the wheel everytime, we can easily adapt what already exists in professional world into crypto, with a tailoring for the specific tools and needs we have, and this is what is happening here in my opinion.
I also like the expantion in scope, and I partially share the concern of @Frisson about it potentially be a big too big as workload; at the same time, knowing the parties involved, I think they can pull it off.
As a final note, in this case, like in the stylus sprint, I am strongly against any new election. While I think there could be others that potentially have the knowledge to move this forward (even tho 90% of the lawyerish force of arbitrum is in the parties above), even just the handover, and the reshape of vision, would literally eat on the whole mandate time wise with suboptimal results.
Hi @raam thanks for the comment!
We’re fully aligned with providing clarity around this. This proposal does not aim to permanently change the ADPC election process that was established in the previous Tally vote. Our opinion, which is echoed by @JoJo and @0x_ultra, is that extending the tenure of the current members of the ADPC for this Phase II is the most effective and efficient use of resources for the DAO.
ADPC has done a lot of outstanding work for Arbitrum DAO over the past few months, and I am very grateful to it. In fact, I fully support the proposal, because a good thing needs to be sustainable, and it makes sense to have the necessary budget to accomplish it. I have carefully reviewed the budget mentioned in the proposal, and I think it is relatively reasonable, and there is no over-exaggeration.
Another small question about the 2025 strategy You wrote that it is being prepared, but when will it be presented and suddenly there won't be enough $360k for it?
I will be voted for because this proposal is ideal to simplify communication about the ADPC through clear summaries and promote it on social media. This would increase community understanding and participation. Additionally, greater flexibility in budgeting would allow adaptation to new opportunities, enhancing efficiency in the long term.
Hey @sid_areta, thank you for the response. We understand that the scope for Phase II has expanded to cover more verticals and may require additional time and resources. For this reason, we voted FOR this proposal on Snapshot.
I'm glad you updated your proposal based on community feedback. I especially welcome the re-election as one of the promises being fulfilled.
Hi all,
Thank you so much for you taking the time to provide feedback. We appreciate the level of engagement and alignment on key items! Below, we list some of the amendments to the proposal.
Hi all,
Thank you so much for you taking the time to provide feedback. We appreciate the level of engagement and alignment on key items! Below, we list some of the amendments to the proposal.
This proposal will be live on Snapshot from 11.00 UTC on Sep 5 to 11.00 UTC on Sep 12. You can find the Snapshot link here. Please vote!
Hi @Avantgarde, appreciate the time digesting the proposal and positive feedback. Find some details below:
(1) Re. the OpEx budget:
Regarding the OpEx budget - can you provide any insight into the oversight mechanisms for this budget? e.g., how the MSS will ensure transparency and accountability in spending and what processes will be in place to report back to the DAO on fund utilisation?
Hi @KlausBrave, appreciate you reading through the proposal. Since events are a selected vertical and what we propose is complementary to the GovHack format, it's very useful to get your view as the main event organizer for the DAO!
Let us clarify some of the questions below:
Hi @KlausBrave, appreciate you reading through the proposal. Since events are a selected vertical and what we propose is complementary to the GovHack format, it's very useful to get your view as the main event organizer for the DAO!
Let us clarify some of the questions below:
How does the work load and costs to provide this scale to handle 3 verticals? Can you detail now for 3 verticals how you arrive at the $360k amount?
Tagging @PennBlockchain here as they had a similar question (also thanks for reviewing!).
In Phase I we used $144k to complete one vertical, and as stated in the proposal, the workload in the ADPC was significantly more time and capacity intensive than priced-in, but taken on by the committee as goodwill to make it work. Since we have now left the initial phase and will provide procurement services for two more verticals in Work Package 1, paired with dedicated value in the additional work packages, the budget merely reflects the capacity and time spent by the teams. Using our learnings from the initial phase, we plan to streamline the work to deliver greater output within the same timeframe and a similarly scaled budget.
We will allocate the $60k equally across each party of the ADPC. I.e., each of Areta, Axis Advisory, and Daimon Legal and their dedicated teams will be allocated $20k each per month.
Lastly, just wanted to add a bit of an explainer around the OpEx budget as per @PennBlockchain’s question. Quoting from the proposal:
This budget is designed to streamline the DAO’s interaction with ADPC-whitelisted service providers by creating a direct utilization rail. This rail will allow DAO initiatives and contributors to access and utilize these pre-approved service providers without undergoing the cumbersome proposal process for each engagement. The OpEx budget essentially bypasses the bureaucratic hurdles that currently plague the DAO’s procurement process, enabling a more agile and responsive operational framework.
As it stands and should the proposal be accepted, the DAO would then be able to solicit services re. Events, Security, and RPCs by the end of next term. Naturally as we scale our procurement efforts, the options will correspondingly increase.
Lastly, are funds distributed as a 1 off upfront payment or paid monthly, this level of detail is not in the proposal.
We have added further detail around the funding mechanism into the proposal and updated it to OTC the entire requested amount into USDC upon receipt of the ARB and return the unutilized ARB to the DAO treasury. This is intended to avoid fluctuations in ARB price and ensures that the ADPC avoids using the buffer as much as possible. As such, monthly payments to the ADPC will be made in USDC instead of having to convert the ARB to USDC at the end of each month.
ranked choice voting on snapshot for which verticals are chosen next (as I under it the rank and selection was arrived at from 1-1s with delegates, but there was no option for wider global delegate input in this process, correct me if I am misunderstanding)
Great idea - also one we discussed intensively within the ADPC and delegates. We reached out to 25 delegates and stakeholders directly and via survey for their feedback. We found this to be the most effective process for balancing the high level of context needed for this decision while incorporating as many views from different stakeholders as possible. We have also already started working with Entropy and DisruptionJoe on the Events proposal to ensure that the DAO is able to have a sufficient presence at the larger events in H1 2025. However, your suggestion is well taken - if there is consensus on the DAO wanting to vote individually on the verticals and outsource this decision, we are happy to facilitate this process.
Selecting vertical leads (for RPC and Events) this should be an open process after the vertical is chosen for candidates to respond to and be selected for who is the vertical lead / manager
Could you please expand on what you mean by vertical leads here and what their responsibilities would be?
Good question, and an important point to clarify to avoid confusion - there will be no vertical leads in the sense of dedicated leaders owning any of the verticals. The essence of our process will be to run an open RFP process, giving different providers the opportunity to offer their services and providing the DAO with the most effective access to high-quality services at comparable rates.
Hi @raam thanks for the comment!
We’re fully aligned with providing clarity around this. This proposal does not aim to permanently change the ADPC election process that was established in the previous Tally vote. Our opinion, which is echoed by @JoJo and @0x_ultra, is that extending the tenure of the current members of the ADPC for this Phase II is the most effective and efficient use of resources for the DAO.
For any future extension terms of the ADPC, the process outlined in the original Tally vote will stand unless automatic renewal of the then-current members is proposed. Of course, this will be subject to the potential OpCo that gets formed and any implications that may have on the structure of the ADPC.
We will add the above explanation to the proposal - thank you for clarity on the election requirements and appreciate the engagement on this!
Hi @Avantgarde, appreciate the time digesting the proposal and positive feedback. Find some details below:
(1) Re. the OpEx budget:
Regarding the OpEx budget - can you provide any insight into the oversight mechanisms for this budget? e.g., how the MSS will ensure transparency and accountability in spending and what processes will be in place to report back to the DAO on fund utilisation?
The proposal published by Entropy already binds MSS participants to a transparency and accountability policy relating to breach of duties, conflicts of interest, etc. and there is also a process for the removal of a member if this occurs (if 8/12 agree that this has occurred).
(2) Re. the management of the Security Services Subsidy Fund
On the management of the Security Services Subsidy Fund (kudos for waiving management fees for the pilot phase) - how are you thinking about this long term, including if the fund grows in size/scope etc?
For future iterations we aim to open up management of the fund to other parties who can apply to be selected to manage the fund, akin to our previous proposal to establish a sub-committee for the Security Services Subsidy Fund. In alignment with delegates and the DAO, we believe that the ability to select projects to receive subsidies benefits from having more parties/stakeholders involved in the long-term. Given the operational effort to set up and run such a fund, we propose these parties charge a management fee including operational expenses as a percentage fee of the value of the fund.
(3) Re. Reporting
As far as is understood, the multi-sig management will be handled by the MSS established by Entropy - but what does the specific roles and responsibilities look like? who holds decision-making authority and how would potential conflicts of interest be addressed?
As funds will be endowed in the MSS, they will be subject to the MSS reporting requirements which are currently being handled by R3gen Finance through token flow reporting. This report will detail expenditures, inflows from Sequencer Flows, and other direct outflows from the Arbitrum Treasury. The report will also include ancillary items such as include transaction fees, treasury holdings, spending estimations, and contributor analyses.
Hope that helped to clarify some of the open items. Let us know if you have any further questions!
Similar to questions raised by @Avantgarde and @KlausBrave, we would like clarification on the OpEx budget and the compensation for the ADPC. Specifically:
Further to @jameskbh point on budget break down for the $360k. Last time it was 3 providers at $8k/month x 6 months = $144k.
Further to @jameskbh point on budget break down for the $360k. Last time it was 3 providers at $8k/month x 6 months = $144k.
I also suggest for the verticals it be a formal process for:
ranked choice voting on snapshot for which verticals are chosen next (as I understand it the rank and selection was arrived at from 1-1s with delegates, but there was no option for wider global delegate input in this process, correct me if I am misunderstanding)
Selecting vertical leads (for RPC and Events) this should be an open process after the vertical is chosen for candidates to respond to and be selected for who is the vertical lead / manager
Hi @Frisson, thank you for your feedback! Appreciate you taking the time to digest the work so far and the Outcome Report. As always, let us know if we can support with answering any more questions!
On the scope, we're fully aligned on the ambition. Like last term, we prefer to focus the scope on where we see the biggest value add for the DAO, even if it means we might need to work a bit more extensively to deliver, rather than removing elements where we see value. We still view this as a precedent-setting effort and, like last term, we will ensure the execution is at 100%.
Hi @Frisson, thank you for your feedback! Appreciate you taking the time to digest the work so far and the Outcome Report. As always, let us know if we can support with answering any more questions!
On the scope, we're fully aligned on the ambition. Like last term, we prefer to focus the scope on where we see the biggest value add for the DAO, even if it means we might need to work a bit more extensively to deliver, rather than removing elements where we see value. We still view this as a precedent-setting effort and, like last term, we will ensure the execution is at 100%.
Sharing some more details on Work Package 1 to explain our reasoning below: The bulk of the effort in Work Package 1 will be around the RPC vertical. The Events vertical, due to the need for the DAO, is already front-loaded with strategic planning around the events calendar in collaboration with Entropy and DisruptionJoe. Hence, the procurement of providers for this vertical will be solely about executing this strategy and will not prevent the APDC team from delivering on other items. We were aware of the specific angle for the DAO early, so decided to structure this vertical as individual RFPs per event, rather than a marketplace of providers similar to the Security Services marketplace from Phase I.
Hope I could add some more color to the why of our work packages here. We're confident that we can fully deliver on both verticals and be a net positive to the DAO!
As always, we hugely appreciate your engagement and support 🙂
I’m jumping into the discussion a bit late, but I wanted to share my thoughts on the election - no election topic. Generally, I’m all for elections and democratic principles as they are fundamental to decentralized governance. However, I think it’s also important to consider the context and specifics of the situation. And I agree with @JoJo on this.
The initial proposal mentioned that elections would be held for the second phase. But sometimes, to truly understand if certain choices are effective or not, you need to be in the process and see things unfold. I believe that while elections are a fundamental principle, continuity is also a key factor. Elections should only take place if they are truly beneficial in the given context. As @Immutablelawyer pointed out, holding new elections could lead to bureaucratic overhead and an inefficient use of resources due to the electoral process and the onboarding of new members.
I’m jumping into the discussion a bit late, but I wanted to share my thoughts on the election - no election topic. Generally, I’m all for elections and democratic principles as they are fundamental to decentralized governance. However, I think it’s also important to consider the context and specifics of the situation. And I agree with @JoJo on this.
The initial proposal mentioned that elections would be held for the second phase. But sometimes, to truly understand if certain choices are effective or not, you need to be in the process and see things unfold. I believe that while elections are a fundamental principle, continuity is also a key factor. Elections should only take place if they are truly beneficial in the given context. As @Immutablelawyer pointed out, holding new elections could lead to bureaucratic overhead and an inefficient use of resources due to the electoral process and the onboarding of new members.
In this case, I think continuity is crucial for achieving the established goals effectively. This is why, I believe that re-electing the current members directly would be the best course of action. However, it’s important that this issue has been raised because it needs to be addressed when the proposal goes to Snapshot. It’s crucial to get community consensus on modifying the election process for the second phase, should the proposal be approved. But I've read that this last point has already been taken into consideration, so I guess that we will see it in the next steps on Snapshot.
From what I can tell the ADPC did a great job towards the DAO. The reports and status updates have always been on point and very detailed. I agree with @Frisson that the workload sounds ambitious but I'm happy to be proven wrong.
I support this proposal and I am happy to see that all member want to continue this great work.
We think the reports that Areta has compiled and published are some of the most impressive and well rounded in DeFi. Overall, it seems the first phase of this has went really well and we are in full support of a phase two being enacted. The budget seems very reasonable and we are looking forward to the team’s future work.
I appreciate the ADPC's work during the pilot phase to set up a procurement framework, benchmark security providers, and pass a proposal to fund a security subsidy.
Overall, I think the amount of work proposed in Phase II is ambitious. My instinct is to recommend that we reduce the scope of Work Package 1 by focusing on only the RPC vertical. That way, the team will have more capacity to execute well on Work Packages 2-4. I think we can execute on the event vertical in Phase III.
I appreciate the ADPC's work during the pilot phase to set up a procurement framework, benchmark security providers, and pass a proposal to fund a security subsidy.
Overall, I think the amount of work proposed in Phase II is ambitious. My instinct is to recommend that we reduce the scope of Work Package 1 by focusing on only the RPC vertical. That way, the team will have more capacity to execute well on Work Packages 2-4. I think we can execute on the event vertical in Phase III.
I plan to spend more time with this proposal to provide additional feedback in the future.
ADPC created a one of a kind type of structure in our DAO. The effort of coming up with something that can source service provider on one side, and serve protocols on the other, was something that was not on my bingo card for 2024 so to say.
While i think this initiative, due to the complex semantic (both for non english speaker, but also tied to how "lawyerish" is), is not totally known and widespread in arbitrum, we could be doing an effort to market it with an eli5, both in this forum and outside on twitter, to make people more aware of it. This is my current feedback.
ADPC created a one of a kind type of structure in our DAO. The effort of coming up with something that can source service provider on one side, and serve protocols on the other, was something that was not on my bingo card for 2024 so to say.
While i think this initiative, due to the complex semantic (both for non english speaker, but also tied to how "lawyerish" is), is not totally known and widespread in arbitrum, we could be doing an effort to market it with an eli5, both in this forum and outside on twitter, to make people more aware of it. This is my current feedback.
For the rest
I also want to chim in on the election topic. I understand that we want, as a general principle, to go for rotation/election every time.
I also think is not necessarily the right decision for all the initiatives. The ones that are extremely vertical, that requires a specific background, and that would have a very long handover, like this one, might not necessarily benefit from a new election. Assuming new people would get elected, I don't see them being able to just continue the current work + adding the new packages without spending at least 30% of the mandate to just catch up. I am also in the camp that for certain initiatives going for 6 months election means we will never be able to retain professional partners, or at least will be extremely hard, because planning initiatives on such a short term of time and not being sure about being compensated in future for your work might just lead people away. For this reason, in this very specific case, I would like to see Joseph, Areta and Daimon to just keep doing what they are doing. IMHO we shouldn't talk about rotating them before another 12 months to see proper results (unless, of course, something bad like operating outside the mandate happens).
Hi @jameskbh, we have taken on your feedback and will insert the detail stating that the ADPC will be re-electing current members as opposed to creating new elections altogether.
Hi @jameskbh, we have taken on your feedback and will insert the detail stating that the ADPC will be re-electing current members as opposed to creating new elections altogether.
As per our comment to @jameskbh - it will be inserted in the proposal together with some other minor amendments in light of the feedback we've received from the community (this should be done in the next hour).
Naturally, all amendments will be finalised prior to this going to Snapshot for a temperature check - hope this clarifies things!
I propose to explicitly indicate the line in the vote: we support the proposal, but with re-elections.
Hey @raam !
Thanks for pointing this out.
Re. "the DAO may approve and implement a Non-Constitutional AIP to change the rules governing future ADPC elections, but the AIP process may not be used to intervene in an ongoing election", this is that Non-Constitutional AIP. Nowhere does the Tally proposal state that the Non-Constitutional AIP has to be a separate Non-Constitutional AIP.
Hey @raam !
Thanks for pointing this out.
Re. "the DAO may approve and implement a Non-Constitutional AIP to change the rules governing future ADPC elections, but the AIP process may not be used to intervene in an ongoing election", this is that Non-Constitutional AIP. Nowhere does the Tally proposal state that the Non-Constitutional AIP has to be a separate Non-Constitutional AIP.
Thanks for the feedback as always ser!
Thanks for your reply!
I understand the incentive and the approach of the current cohort.
I just want to have explicit on the proposal that the DAO is renouncing the new elections (or a similar wording), as you are asking the DAO to change the procedure that was approved on the previous iteration.
I see a few issues with the proposal as it stands:
Hi @jameskbh, we have taken on your feedback and will insert the detail stating that the ADPC will be re-electing current members as opposed to creating new elections altogether.
Thanks for your feedback, it's much appreciated!
Extend ADPC's term of office to a second 6-month period to support. The proposal is complete.
Hi @cp0x !
Many thanks for your feedback!
Regarding the OpEx budget: We first have to determine the size of the budget and create a corresponding proposal during the ADPC's second term.
Additionally, no funds have been made available by the DAO for the Security Services Subsidy Fund Sub-Committee: As the Snapshot vote didn't show community support, there was no Tally vote requesting such funds.
Hey @jameskbh !
Thanks for your comment!
Hey @jameskbh !
Thanks for your comment!
The re-election of the same members can still be considered a legitimate election under the terms initially outlined. The key aspect of an election is that it allows stakeholders to express their preferences through a voting process. In this case, if the existing members are re-elected, it indicates that the electorate has reviewed their performance and decided that they should continue in their roles.
Additionally, running a new election and integrating new members into the ADPC involves significant bureaucratic overhead. The election process itself, including candidate vetting, voting, and onboarding, requires time and resources that could otherwise be directed towards more pressing matters, such as advancing the committee’s goals and managing the subsidy fund.
Of course, we are proposing what we think is best for the DAO considering the ramp-up cost of the mandate and performance of the current committee. Should the DAO have strong opinions against, we obviously remain flexible.
Appreciate the feedback on the proposal ser 🤝
The ADPC has done a great job at communicating with delegates and the community to understand the next best ways to support the DAO. I really appreciate the outreach and openness to utilize community feedback to move this proposal forward.
I am optimistic about the potential of the two chosen verticals in Work package 1; RPCs and events, to empower our community and take us to the next level.
The ADPC has done a great job at communicating with delegates and the community to understand the next best ways to support the DAO. I really appreciate the outreach and openness to utilize community feedback to move this proposal forward.
I am optimistic about the potential of the two chosen verticals in Work package 1; RPCs and events, to empower our community and take us to the next level.
For teams to provide great services to the chain, a strong foundation is important, and RPCs contribute to that foundation. Reliable and consistent RPCs do come with a hefty tag price and it’s unlikely that orbit chains can afford this service. With the DAO supporting the RPC cost here for select orbit chains, this defo alleviates that stress for orbit chains so they can focus on building a stronger culture and community rather than being blocked by costs. I am interested to see how the RPCs are categorised.
We have firsthand experience at Across with RPC providers who consistently provide great service, enabling us to support chains like Arbitrum with fast and cheap fills. For Across to provide a consistent and reliable experience to orbit chains, RPCs play a key role for us here.
I have personally spoken to a handful of orbit chains who have clearly mentioned that some RPCs are too costly for them, especially in the early stages and this financial blocker has prevented in various aspects.
Regarding events, I believe an in-person presence is key to helping Arbitrum expand. It’s important to have these events to bring a combination of Arb contributors (OCL, DAO, Tandem, dapp, chains etc.) together and discuss important problems or further develop the culture.
Hello all.
This is a well thought proposal, with important objectives delineated for the next iteration of the ADPC. I have some questions about the Committee members:
In the original proposal, there was this definition about elections:
Work Package 3: Creation of OpEx (Operational Expense) Budget for the DAO to Utilize Whitelisted Service Providers
Hi @raam thanks for the comment!
We’re fully aligned with providing clarity around this. This proposal does not aim to permanently change the ADPC election process that was established in the previous Tally vote. Our opinion, which is echoed by @JoJo and @0x_ultra, is that extending the tenure of the current members of the ADPC for this Phase II is the most effective and efficient use of resources for the DAO.
For any future extension terms of the ADPC, the process outlined in the original Tally vote will stand unless automatic renewal of the then-current members is proposed. Of course, this will be subject to the potential OpCo that gets formed and any implications that may have on the structure of the ADPC.
We will add the above explanation to the proposal - thank you for clarity on the election requirements and appreciate the engagement on this!
Hi @Avantgarde, appreciate the time digesting the proposal and positive feedback. Find some details below:
(1) Re. the OpEx budget:
Regarding the OpEx budget - can you provide any insight into the oversight mechanisms for this budget? e.g., how the MSS will ensure transparency and accountability in spending and what processes will be in place to report back to the DAO on fund utilisation?
The proposal published by Entropy already binds MSS participants to a transparency and accountability policy relating to breach of duties, conflicts of interest, etc. and there is also a process for the removal of a member if this occurs (if 8/12 agree that this has occurred).
(2) Re. the management of the Security Services Subsidy Fund
On the management of the Security Services Subsidy Fund (kudos for waiving management fees for the pilot phase) - how are you thinking about this long term, including if the fund grows in size/scope etc?
For future iterations we aim to open up management of the fund to other parties who can apply to be selected to manage the fund, akin to our previous proposal to establish a sub-committee for the Security Services Subsidy Fund. In alignment with delegates and the DAO, we believe that the ability to select projects to receive subsidies benefits from having more parties/stakeholders involved in the long-term. Given the operational effort to set up and run such a fund, we propose these parties charge a management fee including operational expenses as a percentage fee of the value of the fund.
(3) Re. Reporting
As far as is understood, the multi-sig management will be handled by the MSS established by Entropy - but what does the specific roles and responsibilities look like? who holds decision-making authority and how would potential conflicts of interest be addressed?
As funds will be endowed in the MSS, they will be subject to the MSS reporting requirements which are currently being handled by R3gen Finance through token flow reporting. This report will detail expenditures, inflows from Sequencer Flows, and other direct outflows from the Arbitrum Treasury. The report will also include ancillary items such as include transaction fees, treasury holdings, spending estimations, and contributor analyses.
Hope that helped to clarify some of the open items. Let us know if you have any further questions!
Similar to questions raised by @Avantgarde and @KlausBrave, we would like clarification on the OpEx budget and the compensation for the ADPC. Specifically:
Further to @jameskbh point on budget break down for the $360k. Last time it was 3 providers at $8k/month x 6 months = $144k.
Further to @jameskbh point on budget break down for the $360k. Last time it was 3 providers at $8k/month x 6 months = $144k.
I also suggest for the verticals it be a formal process for:
ranked choice voting on snapshot for which verticals are chosen next (as I understand it the rank and selection was arrived at from 1-1s with delegates, but there was no option for wider global delegate input in this process, correct me if I am misunderstanding)
Selecting vertical leads (for RPC and Events) this should be an open process after the vertical is chosen for candidates to respond to and be selected for who is the vertical lead / manager
Hi @Frisson, thank you for your feedback! Appreciate you taking the time to digest the work so far and the Outcome Report. As always, let us know if we can support with answering any more questions!
On the scope, we're fully aligned on the ambition. Like last term, we prefer to focus the scope on where we see the biggest value add for the DAO, even if it means we might need to work a bit more extensively to deliver, rather than removing elements where we see value. We still view this as a precedent-setting effort and, like last term, we will ensure the execution is at 100%.
Hi @Frisson, thank you for your feedback! Appreciate you taking the time to digest the work so far and the Outcome Report. As always, let us know if we can support with answering any more questions!
On the scope, we're fully aligned on the ambition. Like last term, we prefer to focus the scope on where we see the biggest value add for the DAO, even if it means we might need to work a bit more extensively to deliver, rather than removing elements where we see value. We still view this as a precedent-setting effort and, like last term, we will ensure the execution is at 100%.
Sharing some more details on Work Package 1 to explain our reasoning below: The bulk of the effort in Work Package 1 will be around the RPC vertical. The Events vertical, due to the need for the DAO, is already front-loaded with strategic planning around the events calendar in collaboration with Entropy and DisruptionJoe. Hence, the procurement of providers for this vertical will be solely about executing this strategy and will not prevent the APDC team from delivering on other items. We were aware of the specific angle for the DAO early, so decided to structure this vertical as individual RFPs per event, rather than a marketplace of providers similar to the Security Services marketplace from Phase I.
Hope I could add some more color to the why of our work packages here. We're confident that we can fully deliver on both verticals and be a net positive to the DAO!
As always, we hugely appreciate your engagement and support 🙂
I’m jumping into the discussion a bit late, but I wanted to share my thoughts on the election - no election topic. Generally, I’m all for elections and democratic principles as they are fundamental to decentralized governance. However, I think it’s also important to consider the context and specifics of the situation. And I agree with @JoJo on this.
The initial proposal mentioned that elections would be held for the second phase. But sometimes, to truly understand if certain choices are effective or not, you need to be in the process and see things unfold. I believe that while elections are a fundamental principle, continuity is also a key factor. Elections should only take place if they are truly beneficial in the given context. As @Immutablelawyer pointed out, holding new elections could lead to bureaucratic overhead and an inefficient use of resources due to the electoral process and the onboarding of new members.
I’m jumping into the discussion a bit late, but I wanted to share my thoughts on the election - no election topic. Generally, I’m all for elections and democratic principles as they are fundamental to decentralized governance. However, I think it’s also important to consider the context and specifics of the situation. And I agree with @JoJo on this.
The initial proposal mentioned that elections would be held for the second phase. But sometimes, to truly understand if certain choices are effective or not, you need to be in the process and see things unfold. I believe that while elections are a fundamental principle, continuity is also a key factor. Elections should only take place if they are truly beneficial in the given context. As @Immutablelawyer pointed out, holding new elections could lead to bureaucratic overhead and an inefficient use of resources due to the electoral process and the onboarding of new members.
In this case, I think continuity is crucial for achieving the established goals effectively. This is why, I believe that re-electing the current members directly would be the best course of action. However, it’s important that this issue has been raised because it needs to be addressed when the proposal goes to Snapshot. It’s crucial to get community consensus on modifying the election process for the second phase, should the proposal be approved. But I've read that this last point has already been taken into consideration, so I guess that we will see it in the next steps on Snapshot.
From what I can tell the ADPC did a great job towards the DAO. The reports and status updates have always been on point and very detailed. I agree with @Frisson that the workload sounds ambitious but I'm happy to be proven wrong.
I support this proposal and I am happy to see that all member want to continue this great work.
We think the reports that Areta has compiled and published are some of the most impressive and well rounded in DeFi. Overall, it seems the first phase of this has went really well and we are in full support of a phase two being enacted. The budget seems very reasonable and we are looking forward to the team’s future work.
I appreciate the ADPC's work during the pilot phase to set up a procurement framework, benchmark security providers, and pass a proposal to fund a security subsidy.
Overall, I think the amount of work proposed in Phase II is ambitious. My instinct is to recommend that we reduce the scope of Work Package 1 by focusing on only the RPC vertical. That way, the team will have more capacity to execute well on Work Packages 2-4. I think we can execute on the event vertical in Phase III.
I appreciate the ADPC's work during the pilot phase to set up a procurement framework, benchmark security providers, and pass a proposal to fund a security subsidy.
Overall, I think the amount of work proposed in Phase II is ambitious. My instinct is to recommend that we reduce the scope of Work Package 1 by focusing on only the RPC vertical. That way, the team will have more capacity to execute well on Work Packages 2-4. I think we can execute on the event vertical in Phase III.
I plan to spend more time with this proposal to provide additional feedback in the future.
ADPC created a one of a kind type of structure in our DAO. The effort of coming up with something that can source service provider on one side, and serve protocols on the other, was something that was not on my bingo card for 2024 so to say.
While i think this initiative, due to the complex semantic (both for non english speaker, but also tied to how "lawyerish" is), is not totally known and widespread in arbitrum, we could be doing an effort to market it with an eli5, both in this forum and outside on twitter, to make people more aware of it. This is my current feedback.
ADPC created a one of a kind type of structure in our DAO. The effort of coming up with something that can source service provider on one side, and serve protocols on the other, was something that was not on my bingo card for 2024 so to say.
While i think this initiative, due to the complex semantic (both for non english speaker, but also tied to how "lawyerish" is), is not totally known and widespread in arbitrum, we could be doing an effort to market it with an eli5, both in this forum and outside on twitter, to make people more aware of it. This is my current feedback.
For the rest
I also want to chim in on the election topic. I understand that we want, as a general principle, to go for rotation/election every time.
I also think is not necessarily the right decision for all the initiatives. The ones that are extremely vertical, that requires a specific background, and that would have a very long handover, like this one, might not necessarily benefit from a new election. Assuming new people would get elected, I don't see them being able to just continue the current work + adding the new packages without spending at least 30% of the mandate to just catch up. I am also in the camp that for certain initiatives going for 6 months election means we will never be able to retain professional partners, or at least will be extremely hard, because planning initiatives on such a short term of time and not being sure about being compensated in future for your work might just lead people away. For this reason, in this very specific case, I would like to see Joseph, Areta and Daimon to just keep doing what they are doing. IMHO we shouldn't talk about rotating them before another 12 months to see proper results (unless, of course, something bad like operating outside the mandate happens).
Hi @jameskbh, we have taken on your feedback and will insert the detail stating that the ADPC will be re-electing current members as opposed to creating new elections altogether.
Hi @jameskbh, we have taken on your feedback and will insert the detail stating that the ADPC will be re-electing current members as opposed to creating new elections altogether.
As per our comment to @jameskbh - it will be inserted in the proposal together with some other minor amendments in light of the feedback we've received from the community (this should be done in the next hour).
Naturally, all amendments will be finalised prior to this going to Snapshot for a temperature check - hope this clarifies things!
I propose to explicitly indicate the line in the vote: we support the proposal, but with re-elections.
Hey @raam !
Thanks for pointing this out.
Re. "the DAO may approve and implement a Non-Constitutional AIP to change the rules governing future ADPC elections, but the AIP process may not be used to intervene in an ongoing election", this is that Non-Constitutional AIP. Nowhere does the Tally proposal state that the Non-Constitutional AIP has to be a separate Non-Constitutional AIP.
Hey @raam !
Thanks for pointing this out.
Re. "the DAO may approve and implement a Non-Constitutional AIP to change the rules governing future ADPC elections, but the AIP process may not be used to intervene in an ongoing election", this is that Non-Constitutional AIP. Nowhere does the Tally proposal state that the Non-Constitutional AIP has to be a separate Non-Constitutional AIP.
Thanks for the feedback as always ser!
Thanks for your reply!
I understand the incentive and the approach of the current cohort.
I just want to have explicit on the proposal that the DAO is renouncing the new elections (or a similar wording), as you are asking the DAO to change the procedure that was approved on the previous iteration.
I see a few issues with the proposal as it stands:
Hi @jameskbh, we have taken on your feedback and will insert the detail stating that the ADPC will be re-electing current members as opposed to creating new elections altogether.
Thanks for your feedback, it's much appreciated!
Extend ADPC's term of office to a second 6-month period to support. The proposal is complete.
Hi @cp0x !
Many thanks for your feedback!
Regarding the OpEx budget: We first have to determine the size of the budget and create a corresponding proposal during the ADPC's second term.
Additionally, no funds have been made available by the DAO for the Security Services Subsidy Fund Sub-Committee: As the Snapshot vote didn't show community support, there was no Tally vote requesting such funds.
Hey @jameskbh !
Thanks for your comment!
Hey @jameskbh !
Thanks for your comment!
The re-election of the same members can still be considered a legitimate election under the terms initially outlined. The key aspect of an election is that it allows stakeholders to express their preferences through a voting process. In this case, if the existing members are re-elected, it indicates that the electorate has reviewed their performance and decided that they should continue in their roles.
Additionally, running a new election and integrating new members into the ADPC involves significant bureaucratic overhead. The election process itself, including candidate vetting, voting, and onboarding, requires time and resources that could otherwise be directed towards more pressing matters, such as advancing the committee’s goals and managing the subsidy fund.
Of course, we are proposing what we think is best for the DAO considering the ramp-up cost of the mandate and performance of the current committee. Should the DAO have strong opinions against, we obviously remain flexible.
Appreciate the feedback on the proposal ser 🤝
The ADPC has done a great job at communicating with delegates and the community to understand the next best ways to support the DAO. I really appreciate the outreach and openness to utilize community feedback to move this proposal forward.
I am optimistic about the potential of the two chosen verticals in Work package 1; RPCs and events, to empower our community and take us to the next level.
The ADPC has done a great job at communicating with delegates and the community to understand the next best ways to support the DAO. I really appreciate the outreach and openness to utilize community feedback to move this proposal forward.
I am optimistic about the potential of the two chosen verticals in Work package 1; RPCs and events, to empower our community and take us to the next level.
For teams to provide great services to the chain, a strong foundation is important, and RPCs contribute to that foundation. Reliable and consistent RPCs do come with a hefty tag price and it’s unlikely that orbit chains can afford this service. With the DAO supporting the RPC cost here for select orbit chains, this defo alleviates that stress for orbit chains so they can focus on building a stronger culture and community rather than being blocked by costs. I am interested to see how the RPCs are categorised.
We have firsthand experience at Across with RPC providers who consistently provide great service, enabling us to support chains like Arbitrum with fast and cheap fills. For Across to provide a consistent and reliable experience to orbit chains, RPCs play a key role for us here.
I have personally spoken to a handful of orbit chains who have clearly mentioned that some RPCs are too costly for them, especially in the early stages and this financial blocker has prevented in various aspects.
Regarding events, I believe an in-person presence is key to helping Arbitrum expand. It’s important to have these events to bring a combination of Arb contributors (OCL, DAO, Tandem, dapp, chains etc.) together and discuss important problems or further develop the culture.
Hello all.
This is a well thought proposal, with important objectives delineated for the next iteration of the ADPC. I have some questions about the Committee members:
In the original proposal, there was this definition about elections:
Work Package 3: Creation of OpEx (Operational Expense) Budget for the DAO to Utilize Whitelisted Service Providers
Thanks for your reply!
I understand the incentive and the approach of the current cohort.
I just want to have explicit on the proposal that the DAO is renouncing the new elections (or a similar wording), as you are asking the DAO to change the procedure that was approved on the previous iteration.
I see a few issues with the proposal as it stands:
I hope that makes sense.
Hi @cp0x !
Many thanks for your feedback!
Regarding the OpEx budget: We first have to determine the size of the budget and create a corresponding proposal during the ADPC's second term.
Additionally, no funds have been made available by the DAO for the Security Services Subsidy Fund Sub-Committee: As the Snapshot vote didn't show community support, there was no Tally vote requesting such funds.
Regarding the breakdown of the budget: Thank you for the compliment! The USD 360k is the cost of providing the procurement work for two verticals while still running the legacy procurement framework. A learning from Phase 1 was that we needed greater resources to put together one procurement framework. Leaving the pilot phase where we worked on one vertical and moving now to the execution phase where we will be delivering more than double the services requires greater resources. To put this into perspective: The pilot phase was priced at USD 144k for one vertical.
Thanks again for the feedback! :handshake:
Hello all.
This is a well thought proposal, with important objectives delineated for the next iteration of the ADPC. I have some questions about the Committee members:
In the original proposal, there was this definition about elections:
We propose adapting section 4 of the ArbitrumDAO Constitution & optimizing it to apply to the election for ADPC Members [REF: The Amended Constitution of the Arbitrum DAO | Arbitrum DAO - Governance docs ]. Hereunder, we propose an adapted model of Section 4 of the ArbitrumDAO Constitution to implement in the ADPC Elections.
The ADPC election process is scheduled to begin 3 business days from the ratification of the on-chain proposal that will secure the funding for the ADPC.
The date chosen for the first election will form the basis for all future elections. Every election should begin 6 months after the previous election has been finalized.
All ADPC committee members are expected to serve their term unless terminated by the ArbitrumDAO through Snapshot as stipulated in the Agreement regulating the ADPC [Further details below re. the Agreement & Defining provisions in the Checks & Balances section].
There will be one election with the first three [3] ranking members in the weighted voting Snapshot being elected to the ADPC.
I don't see any mention of a new election for this next phase in the current proposal. Can you clarify why?
Work Package 3: Creation of OpEx (Operational Expense) Budget for the DAO to Utilize Whitelisted Service Providers
I have a question about this budget. I agree that the operating budget helps to overcome bureaucracy, and here's the question: Will this budget be formed from the funds that were requested for the Security Services Subsidy Fund Sub-Committee? If not, then I suggest doing just that, because these funds are needed for one purpose.
The ADPC is budgeting USD 360,000 for the work in Phase II as outlined in the Phase II Mandate section above
I read your detailed report (it is very good), but I did not find the breakdown of the budget for this $360k. Perhaps I missed the breakdown, so tell me where I can see it. Are the subcommittee that was not voted on included in the costs?
Thanks for your reply!
I understand the incentive and the approach of the current cohort.
I just want to have explicit on the proposal that the DAO is renouncing the new elections (or a similar wording), as you are asking the DAO to change the procedure that was approved on the previous iteration.
I see a few issues with the proposal as it stands:
I hope that makes sense.
Hi @cp0x !
Many thanks for your feedback!
Regarding the OpEx budget: We first have to determine the size of the budget and create a corresponding proposal during the ADPC's second term.
Additionally, no funds have been made available by the DAO for the Security Services Subsidy Fund Sub-Committee: As the Snapshot vote didn't show community support, there was no Tally vote requesting such funds.
Regarding the breakdown of the budget: Thank you for the compliment! The USD 360k is the cost of providing the procurement work for two verticals while still running the legacy procurement framework. A learning from Phase 1 was that we needed greater resources to put together one procurement framework. Leaving the pilot phase where we worked on one vertical and moving now to the execution phase where we will be delivering more than double the services requires greater resources. To put this into perspective: The pilot phase was priced at USD 144k for one vertical.
Thanks again for the feedback! :handshake:
Hello all.
This is a well thought proposal, with important objectives delineated for the next iteration of the ADPC. I have some questions about the Committee members:
In the original proposal, there was this definition about elections:
We propose adapting section 4 of the ArbitrumDAO Constitution & optimizing it to apply to the election for ADPC Members [REF: The Amended Constitution of the Arbitrum DAO | Arbitrum DAO - Governance docs ]. Hereunder, we propose an adapted model of Section 4 of the ArbitrumDAO Constitution to implement in the ADPC Elections.
The ADPC election process is scheduled to begin 3 business days from the ratification of the on-chain proposal that will secure the funding for the ADPC.
The date chosen for the first election will form the basis for all future elections. Every election should begin 6 months after the previous election has been finalized.
All ADPC committee members are expected to serve their term unless terminated by the ArbitrumDAO through Snapshot as stipulated in the Agreement regulating the ADPC [Further details below re. the Agreement & Defining provisions in the Checks & Balances section].
There will be one election with the first three [3] ranking members in the weighted voting Snapshot being elected to the ADPC.
I don't see any mention of a new election for this next phase in the current proposal. Can you clarify why?
Work Package 3: Creation of OpEx (Operational Expense) Budget for the DAO to Utilize Whitelisted Service Providers
I have a question about this budget. I agree that the operating budget helps to overcome bureaucracy, and here's the question: Will this budget be formed from the funds that were requested for the Security Services Subsidy Fund Sub-Committee? If not, then I suggest doing just that, because these funds are needed for one purpose.
The ADPC is budgeting USD 360,000 for the work in Phase II as outlined in the Phase II Mandate section above
I read your detailed report (it is very good), but I did not find the breakdown of the budget for this $360k. Perhaps I missed the breakdown, so tell me where I can see it. Are the subcommittee that was not voted on included in the costs?