Before moving forward with the details, I’d love to hear your thoughts on the Subsidy Fund implemented by the ADPC. Do you think it was well executed? What is your opinion on the results? And why do you propose making such a drastic change to that model instead of, for instance, suggesting that this new committee execute the v2?
There are a few reasons why we believe it is better for the AF (or potentially the future OpCo, when it is up and running) to take on the work for the security subsidy fund and allow the procurement committee to pursue other initiatives:
- Time to action. The ADPC was approved by the DAO on the 8th February 2024 to put together a framework for subsidising audits. ADPC received funds from the subsidy program on 25th July 2024 to run an 8 week program. Final allocations for the 8 week program were completed in December 2024.
It took around ~10 months to stand up and complete the 8 week program. Unfortunately, this meant there was no security subsidy fund by the ArbitrumDAO for most of 2024. Due to this shortcoming, (the AF) have stepped in via our grant program to sponsor audits for builders over the past year. Furthermore, ADPC is now focused on RPC providers until April 2025 and has also included multiple other work packages in its scope for this term. This implies the DAO will not have a subsidy fund for a further few months.
We believe the security subsidy fund is essential for supporting early stage builders and it should be stood up as soon as possible. We (Arbitrum) cannot afford to further delay a fully fledged program that is openly available at any time.
- Technical expertise. One of the anticipated lessons learnt from the security subsidy program run by the ADPC is the need for involvement of technical experts who can evaluate the project that needs an audit and ensure the quote from the auditor is indeed a fair/accurate assessment.
The ADPC’s membership lacks the technical expertise to evaluate applications for a security subsidy program and will need to fund external parties for assistance. We’d recommend the DAO approve programs that match the ADPC’s core competencies so they can have a greater impact without relying on third parties.
- Financial cost. To date, the ADPC’s has charged the DAO $24k per month for the first 6 months and the current fee is $60k per month for 6 months (150% pay increase). By April 2025, they will have charged the DAO $540k. If the next iteration of the ADPC continues at $60k per month, then it will cost $720k per year ($20k per member excluding other costs such as $54k for operational expenses).
We believe this is a very high overhead to pay for running a $10m security subsidy program. At $720k per year, the AF or upcoming OpCo can hire full time staff to run this alongside other programs that we all deem as mission critical for Arbitrum.
- AF involvement in ADPC program. In most DAO programs, we are not involved in the day-to-day operations of the program, but for the security subsidy fund, we found ourselves heavily involved in the process of selecting which teams get the subsidy to pay auditors and engaging with these stakeholders. Additionally, with the RPC program, the ADPC is insistent that we take on responsibility for their framework from April 2025 onwards.
Our increased involvement was a sign that it may be better for the ADPC to focus on topics that match their core competencies and not necessarily run an audit subsidy program. Additionally, if we are expected to carry on the continuation of a framework and execute it on behalf of others, then we (AF) should just set it up ourselves.
Are there any lessons from that experience that could be applied?
Yes, some of the lessons we can share:
-
Funds up front. The ADPC started in February, but only got the funds in July 2025 as there was a requirement to go back to the DAO’s voting process to request the funds. The lesson here is to ensure the DAO allocates funds to new programs and enable it to get started more quickly.
-
Technical expertise. Evaluating the cost of an audit requires domain expertise and it is not something a general committee is well-suited for handling. This is why we have put forth this proposal as we can request technical members at the AF and OCL to evaluate audit proposals.
-
Services in kind. Some audit firms prefer to not charge a project for the audit in return for tokens/equity later. We should be explicit on whether this type of behaviour should be allowed as it can be beneficial to early-stage projects, but also potentially unfair for competing audit firms.
-
Flexibility in scope. After agreements were made between all parties, many projects/auditors also wanted to change the scope of the audits, and requested different terms, accordingly. Flexibility is possible when there is an on-going application process as opposed to the 8-week trial that effectively allocated the entire budget all at once.
-
Towards fixed rates. All auditors have different costs, but for each auditor, we should work towards a fixed cost of “per auditor week”, so all projects can benefit from discounted rates.
We think this proposal is valuable, though we see some possible issues. The ARDC v1 saw an issue where proposals would come to the security member to audit contracts for new protocols. Similarly, we can see some issue where these protocols receive auditing work, launch on Arbitrum, but then do the bare minimum in ecosystem management and development after launch, while prioritizing other L2s (eg. Base). With this in mind, does it make sense to have this structure for all apps or for only specific applications (i.e., those built with Stylus) and structure the committee differently for other types of applications, or make a priority pathway instead?
We’d avoid overcomplicating the structure of the committee for other type of applications. The motivation to pick team members from AF or OCL is to take advantage of the domain expertise across the organisations. If there is an application that the committee alone cannot evaluate, then they can request assistance from the wider organisation.
On the final point, how to avoid projects getting a grant and then launching on another chain, this is generally the same problem that all grant programs encounter:
- We will prioritise projects who are leveraging Arbitrum’s core technology stack, like a smart contract for stylus or deploying their own chain.
- We may decide to invest in the project over a simple grant as that offers a closer partnership with the project and helps align incentives for all parties involved to remain on Arbitrum.
- Depending on subsidy size, there may be clauses that require projects to launch on Arbitrum before other projects.
However, for the most part, it is more of an art than a science to avoid the above issue.
Furthermore, could we have some elaboration on the option for investment offered by the subsidy? How would this agreement work, what does DAO involvement look like here, etc? We understand that it may be more difficult to lock in apps (and that the auditing program may not be the right place to bundle this), though it is worth noting.
The AF will perform the investment on behalf of the ArbitrumDAO. We decided to include investing as an option in the program to ensure that if an investment makes sense, then we will be able to do it for the community.
Also, on what metrics should we evaluate the success of this program? Projects safely launched on Arbitrum and consistently used?
The metrics should be 1) how many projects that received a subsidy eventually launched on Arbitrum, 2) the growth of each project relative to similar deployments on other chains, 3) the total funds secured and 4) total funds lost due to smart contract vulnerabilities.
Note, it is always worth keeping in mind, audits are not full-proof to avoid bugs, and the main metric is supporting new projects to launch on Arbitrum with some sanity checking by experts and ultimately trying to avoid projects from being forced to ‘test in production.’
Converting 30M ARB to USD immediately is not the play here coz it creates unnecessary sell pressure.
It is a 1 year program and we will not be converting the ARB to USD upfront.
Our goal is to minimize the total ARB that is exchanged and 30m ARB is just a very conservative estimate for the total budget based on the current exchange rate.
How about this solution: can we take obligations from sponsored projects to remain in the Arbitrum ecosystem? And if they want to leave the ecosystem, they will have to return the money spent on the audit and preferably in Arbitrum tokens. I think this would avoid additional risks
We expect to add exclusivity clauses to nearly all agreements for new projects who have not yet launched or existing projects whenever it is reasonably doable.
In the last iteration of the security subsidy funds, there was a committee that made projects compile a rather long (as far as I can read) form, that resulted in some protocols being selected and others not with criteria that were not super clear… How would it work here? Can existing projects already apply?
We will have an application process and example questions/information requested is already outlined in the proposal. This will be used to help us screen the project before performing more due diligence. All projects will be welcome to apply, but we will prioritise early stage projects or projects that really require the financial assistance.
How will the application process work for projects applying? Will communication with the projects and selection decisions be made publicly, similar to how the Questbook DDA and Stylus Sprint rounds were handled, as they have set a good standard for this?
Many early stage projects will still be in stealth mode when they apply for the audit program and will not want to publicly disclose their audit details. Additionally, we expect this program to be very popular, and many projects who apply will not be accepted simply due to volume & grants available. We are expecting the applications to remain private, but the winners to be announced.
Just to clarify, multiple auditors will be chosen, right? We assume that no single audit firm will dominate the program. Will there be a cap on the number of projects any individual auditor can take on to ensure diversity and prevent monopolization?
Yes, the intention is to have auditors compete amongst each other for the project, hopefully leading to better prices for the project. We should avoid caps to ensure the marketplace remains competitive, but will also ensure that there is not a monopoly.
Also, will there be a marketing push to ensure more projects are aware of it? The success of this program also depends on outreach. Visibility could help attract high-quality projects to apply and build on Arbitrum.
The AF will focus significant resources to market this to all projects building on Arbitrum. As you mention, our goal is to get high quality projects, so they need to be aware of this program!
How are teams determined to be eligible for this support? I think its good that its removing that financial barrier from those teams but we should be a tad cautious not to overspend and audit every team.
We put together a list of points that we will evaluate like team background, likelihood of success, etc. There are not enough funds to audit every project. Additionally, we believe it is better to return funds to the DAO than to overspend it / make sure the full budget is exhausted on projects we do not believe will ‘make it’.
You are talking about a long term perspective and setting a budget for only 1 year. In my opinion, this is not a long term perspective and Arbitrum already had a program of audit compensation during the year. How is this program better?
All DAO programs should have an expiry time to ensure the authors have to return to the DAO, show results, and then continue the program. We set the expiry time to 1 year with the option to continue via a snapshot vote if there are still funds available. In regards to ADPC program, we have put an answer at the top of this post 
I think this budget is greatly overstated. I don’t see 100 projects a year that Arbitrum needs so much that we are ready to give them 30 million ARB. Will we proceed from how much money we have or from what projects we need?
100 projects is an illustration to simply show the number of audit subsidies a $10m budget can cover. However, there are hundreds of projects that will likely apply to this program. The committee’s job is to spot the winners that can move the needle for Arbitrum and ensure they are supported. We do not have a metric to sponsor ‘100 projects in 1 year’ and will only sponsor projects that require the assistance.
Differentiation from ADPC Subsidy Fund: Could you elaborate on how this new program significantly improves upon the revised ADPC Subsidy Fund? What specific shortcomings of the previous program does this address?
There was a simpler question before and we provided an answer earlier in this post.
Timing and Evaluation: The ADPC has announced that they will be posting the Subsidy Fund Outcome report (ADPC Update Thread (Phase II) - #22 by sid_areta) in the coming days. Wouldn’t it be prudent to wait for this report before proceeding with a similar program / giving final shape to a new one? This would allow us to learn from issues of the previous program, identify areas for improvement and ensure we’re not duplicating efforts unnecessarily.
We (the AF) were heavily involved in the ADPC’s security subsidy program and how the funds were allocated. So, we are aware of several lessons learnt that can be applied to this program. The report will be helpful to the wider DAO and it should be publicly available before we reach the on-chain voting stage.
What is the criteria for the election and for onboarding the auditors? There will be a request for a commitment from the auditors to have “X” hours available? One thing is to be part of a “whitelist” with no real commitment, and a different thing is to be aligned with the DAO and have manpower available.
We do not expect an auditor to participate in the program if they are not able to commit time to audit projects. Additionally, if they do not audit any projects, then they will be removed from the whitelist.
Can you share the expected skills/knowledge for both this elected member and the auditors?
We expect the elected member to have a strong technical background with experience of writing smart contracts and obtaining audits for their own project in the past. In regards to auditors, we plan to only accept reputable firms.
Can you share more details about the threshold between grant/investment? Who will decide that? The Audit Commitee?
It’ll be decided by the Audit committee, but the difference in grant or investment will really come down to the individual project and their subsidy request. We do not believe it is wise to advertise or commit to a threshold in advance.