[DIP v1.6] Delegate Incentive Program Results (May 2025)

May Participants

For the May iteration of the program, 78 participants enrolled, 67 of whom met the regular requirements to qualify.

You can see the full list here.


Security Council Elections: Mandatory Voting

Please note that for the months of April and May, we have added a special requirement to be eligible for the program: delegates must have voted in the Security Council Elections that concluded on May 3rd, 2025.

You can visualize this in each Delegate’s Profile in the Karma Dashboard.

Delegates who didn’t vote on Security Council elections and won’t qualify for April and May incentives:

  • DisruptionJoe
  • Lovely4Wonders
  • BristolBlockchain
  • LobbyFi
  • danielo - RnDAO
  • McFly - Bacon Labs
  • Agnes
  • Bobbay
  • Bruce1

Parameters Breakdown

Snapshot Voting

During the month, there were a total of 4 Snapshot Votes, which were considered for the assignment of scores by SV. These are the proposals that were considered:

  1. Approval of STEP 2 Committee’s Preferred Allocations
  2. [Non-consitutional]: Top-up for Hackathon Continuation Program
  3. DeFi Renaissance Incentive Program (DRIP)
  4. [Constitutional] AIP: Constitutional Quorum Threshold Reduction

Tally Voting

For this month, a total of 2 Tally Votes were considered for TV scoring. These are:

  1. The Watchdog: Arbitrum DAO’s Grant Misuse Bounty Program
  2. [CONSTITUTIONAL] AIP: ArbOS Version 40 Callisto

It is important to note that only those proposals that ended in May were counted.

Participation Rate (90D)

During the last 90 days (March-April-May), a total of 6 on-chain votes were considered for the assignment of scores by PR90. These are the proposals that were considered:

  1. The Watchdog: Arbitrum DAO’s Grant Misuse Bounty Program
  2. [CONSTITUTIONAL] AIP: ArbOS Version 40 Callisto
  3. [NON-CONSTITUTIONAL] Arbitrum Audit Program
  4. [NON-CONSTITUTIONAL] Arbitrum Onboarding V2: A Governance Bootcamp
  5. [CONSTITUTIONAL] - Adopt Timeboost + Nova Fee Sweep
  6. Request to Increase the Stylus Sprint Committee’s Budget

Note that proposals are always considered in the month in which they are finalized.

Delegate Feedback

In the Karma Dashboard, you can find the detailed breakdown of your Delegate Feedback.

Presence in Discussion Multiplier

As approved in the Tally proposal, the Presence in Discussion parameter acts as a multiplier that measures the presence and participation of delegates throughout the month.

For May, 8 proposals were considered:

  1. [RFC] Proposal to Adjust the Voting Power of the Arbitrum Community Pool & Ratifying the Agentic Governance Pivot
  2. [Constitutional] AIP: Constitutional Quorum Threshold Reduction
  3. [Non-Constitutional] Invest in Builders & Ignite ARB Demand with q/acc
  4. Wind Down the MSS + Transfer Payment Responsibilities to the Arbitrum Foundation
  5. Agentic Governance Initiative [AGI]
  6. DeFi Renaissance Incentive Program (DRIP)
  7. A Vision for the Future of Arbitrum
  8. SOS Discussions

To get the multiplier a delegate needed:

For 5% (1.05) = At least 2 comments (≥25%)

For 10% (1.10) = At least 4 comments (≥50%)

For 20% (1.20) = At least 6 comments (≥75%)

It is important to note that we considered JamesKBH feedback, so for the multiplier calculation, if the delegate made a valid comment on that topic/thread in the previous month, it was considered in the current month.

Delegate Feedback Reporting

You can check the Delegate Feedback Reporting in our Notion page.

We want to keep iterating these reports with community feedback. If you have any suggestions, please feel free to reach us.


May Results

You can see the dashboard with the results implemented by Karma here.

Of all the participating delegates, 24 were eligible to receive compensation.

  • Tier 1: 1 delegate. (4.17%)
  • Tier 2: 7 delegates. (29,16%)
  • Tier 3: 16 delegates. (66,67%)
Delegate TIER PUSD
L2Beat 1 7,000.00
MaxLomu 2 4,740.54
Reverie 2 4,663.80
GMX 2 4,603.80
Jojo 2 4,309.09
Tekr0x.eth 2 4,288.71
Camelot 2 4,253.40
olimpio 2 4,219.80
Griff 3 3,219.34
Karpatkey 3 3,164.23
Areta 3 3,158.50
Gauntlet 3 3,149.00
Tane 3 3,138.41
CastleCapital 3 3,127.41
AranaDigital 3 3,095.00
Uniswap-Arbitrum Delegate Program 3 3,092.97
404DAO 3 3,090.18
StableLab 3 3,089.04
Curia 3 3,046.85
BlockworksResearch 3 3,042.50
TempeTechie 3 3,038.62
GFXLabs 3 3,012.83
Bob-Rossi 3 3,011.59
DAOplomats 3 3,005.63

The total cost destined for the delegates this month would be $87,561.24.

It’s important to note that the final numbers might be different because of the ARB Cap, as stated in the proposal.

You can also check our Public Table to see the detailed breakdown of delegates’ results.

Eligible Delegates - Average Voting Power

This month, we decided to display the incentive distribution based on the Average Voting Power (AVP) of each delegate eligible for compensation.

Total Voting Power Incentivized

During May, the Delegate Incentive Program incentivized an average of 111,308,290 ARB (+8.98% MOM).

AVP-Based Distribution – May

From a total of 24 eligible delegates:

  • Delegates with AVP < 1,000,000: 8 (33.33%)
  • Delegates with AVP > 1,000,000: 16 (66.67%)

Within the group of Delegates with AVP < 1,000,000:

  • Delegates with AVP < 100,000: 5 (62.50% of this group, 20.83% of total)
  • Delegates with AVP > 100,000: 3 (37.50% of this group, 12.50% of total)

Distribution Per Tiers – May

  • Tier 1: 1 eligible delegate in total
    • Delegates with AVP < 1,000,000: 0 (0%)
    • Delegates with AVP > 1,000,000: 1 (100%)
  • Tier 2: 7 eligible delegates in total
    • Delegates with AVP < 1,000,000: 1 (14.29%)
    • Delegates with AVP > 1,000,000: 6 (85.71%)
  • Tier 3: 16 eligible delegates in total
    • Delegates with AVP < 1,000,000: 7 (43.75%)
    • Delegates with AVP > 1,000,000: 9 (56.25%)

Conclusion

During May, there was a higher amount of incentivized Voting Power at the same time that the number of incentivized delegates decreased compared to April.

This is related to the fact that high-VP delegates have increased their participation in the incentive program, while the number of incentivized low-VP delegates has decreased compared to April.

Payments

We track all payment data for greater transparency in our Payment Distribution Thread.

Bonus Points

This month, 2 bi-weekly and 1 GRC calls took place, with a maximum possible score of 3.75%.
Note on Delegates Who Didn’t Qualify

  • For the GRC calls, 1,25% BP will be awarded for each attendance.
  • For the Open Discussion of Proposal(s) - Bi-weekly Governance calls, 1.25% BP will be awarded for attending each call.

Extraordinary Contributions

This month, four delegates were awarded Bonus Points for their contributions to Arbitrum DAO:

  • L2Beat team were given 27.5 Bonus Points:
    We would like to highlight three “extraordinary” contributions:
    • Builders’ Voices Needed: Shaping the Future of Arbitrum Together: Although the ultimate impact of this call to action is yet to be fully defined, we have already seen partial results, as several builders—many of whom typically do not engage with the DAO—have responded to the thread. This is highly valuable, and in our view, this initiative already deserves 10 Bonus Points.
    • SOS Discussion Calls: During April (and the beginning of May), L2Beat effectively organized a series of calls to discuss the different SOS submissions that appeared on the forum. These sessions provided a space for each proposer to present their SOS matrices and allowed delegates and other stakeholders to ask questions. We also view this as an initiative that deserves 12.5 Bonus Points.
    • GRC Calls: While May wasn’t the first month in which L2Beat began organizing these calls, we want to formally start acknowledging their efforts. They’ve successfully restructured the format of these calls, enabling the community to receive updates on all funded initiatives within a one-hour session. For this reason, we are awarding them 5 Bonus Points in recognition.
  • Tekr0x received 10 Bonus Points: During the analysis month, the delegate made an outstanding contribution to the Arbitrum Gaming Ventures initiative through the post Gaming on Arbitrum – A Guide for DAO Members which we consider highly valuable and detailed. This contribution was also acknowledged by a member of the AGV
  • Cp0x received 5 Bonus Points for his participation in the SOS Discussions ([SOS Submission] {Merged: TBD} – Strategic Objectives)
  • TempeTechie received 10 Bonus Points for his participation in the SOS Discussions ([SOS Submission] {Merged: TBD} – Strategic Objectives )

On Delegates Who Did Not Qualify

We know that some delegates, mostly smaller ones, came close to meeting the criteria this month but did not qualify. While this can be discouraging, it’s important to understand that the program is built around two core pillars:

1) Participation in Voting to Help Reach Quorum
Delegates with larger voting power are in a better position to influence outcomes and contribute to quorum.

2) Contributor Professionalization in Arbitrum
Regardless of voting power, the program evaluates the substance of each delegate’s participation in discussions. It is essential that contributions either lead to proposal changes, influence the positions of other delegates, or add clear value to ongoing debates.

For smaller delegates, this second point is especially important. If their contributions are limited in visibility or impact, it becomes difficult to justify compensation, as their voting activity alone carries limited weight in meeting the DAO’s goals.

Lastly, we want to clarify that the feedback shared in our monthly reports is intended to be constructive. It is not a judgment of individual value, but part of a broader effort to support and develop capable delegates and contributors who can bring meaningful input to both daily governance and long-term decision-making.

Dispute Period

As stated in the proposal, delegates have a timeframe to express their disagreement with the results presented by the Incentive Program Administrator.

To raise a dispute, delegates should do so by posting a message in the forum using the following template:

Title: Dispute

Delegate Name

Reason for dispute (please detail):

Side note: We would like to remind everyone that we will not be processing disputes regarding other delegates’ scores, except in cases related to objective parameters (such as voting or call attendance).

Additionally, it’s important to note that disputes concerning subjective parameters (DF and Bonus Points) are unlikely to succeed unless they are exceptionally well-argued.

3 Likes

Title: Dispute

Delegate Name: DonOfDAOS

Reason for dispute (please detail): I received 0 on delegate feedback yet I contributed notably, specifically targeted novel and useful contributions, and I checked in throughout the month to make sure I was on track.

  1. I was the only person to notice or respond to this builder and provided in-depth feedback. I went further to meet them on call, to which they explicitly acknowledged I was the only member of the community to take the time to try and help them build here: [RFC] Signals Protocol
  2. again, I was the only community member to point this builder in the right direction: [RFC] Protocol Participation Request: DAO Liquidity Injection via Smart Contracts into Paribus on Arbitrum - #3 by DonOfDAOs
  3. Similarly, I was the first community member to address these builders after nearly a week with no response: [CONSTITUTIONAL] Register $BORING in the Arbitrum generic-custom gateway - #2 by DonOfDAOs
  4. I was one of the first to provide detailed feedback and questioning to help evolve this proposal: [Non-Constitutional] Invest in Builders & Ignite ARB Demand with q/acc - #10 by DonOfDAOs
  5. I opened discussion on broader privacy standards for the DAO here: Proposal: enable the new TogetherCrew functionality: Free* summarizer and Q&A for delegates telegram chat - #33 by DonOfDAOs
  6. Contributed to the Quorum discussions here: [Constitutional] AIP: Constitutional Quorum Threshold Reduction - #27 by DonOfDAOs

And this is among several other general communications. Certainly, 0 points must be a mistake as I also don’t see any delegate feedback in the Notion.

Further, why is my participation 83% (5/6) when I voted on every single proposal? In fact, it shows immediately next to this number that I voted on all 6, yet =5/6 is the manually entered forumla in my participation column.
Screenshot 2025-06-16 at 10.57.36 PM

The next section shows I didn’t vote on the Stylus proposal which had a snapshot of Feb 19th, 119 days ago and well beyond the 90 day window.

I see the following:

How does it make any sense to count the end of the voting window for participation when one cannot for the full length of that time if they were not delegated to before the snapshot? Effectively, they are being docked for a proposal which began weeks prior to the 90 window for which they may not have even had voting power to use even if they wanted to participate. The start should be the beginning of the period.

Besides which, I haven’t missed a single proposal and there were many more than 6 in the past 90 days.

Finally, I commented on all of the following to qualify for presence in discussions:

  1. here: [RFC] Proposal to Adjust the Voting Power of the Arbitrum Community Pool & Ratifying the Agentic Governance Pivot - #7 by DonOfDAOs
  2. here: [Constitutional] AIP: Constitutional Quorum Threshold Reduction - #27 by DonOfDAOs
  3. here: [Non-Constitutional] Invest in Builders & Ignite ARB Demand with q/acc - #10 by DonOfDAOs
  4. N/A
  5. Avoided Conflict of Interest
  6. here: DeFi Renaissance Incentive Program (DRIP) - #11 by DonOfDAOs
  7. N/A
  8. here: [SOS Submission] Gabriel – Strategic Objectives - #3 by DonOfDAOs
3 Likes

Title: Dispute

Delegate Name: paulofonseca

Reason for dispute (please detail): I believe my bonus points for attending the calls are not correct, since it says that I’ve only participated in 1 of the 2 by-weekly Open Governance Calls in May.

In fact, I’ve participated in both biweekly Open Governance Calls, even asking questions (as it’s typical of me) on both May 6th and May 20th.

Here is my face in the May 6th recording at 6 minutes 15 seconds asking a question.

And here is my avatar in the May 20th recording at 20 minutes 40 seconds also asking a question.

So, my bonus points should be updated accordingly.

Thank you!

Title: Dispute

jameskbh

I want to dispute the low score assigned to the comment below. I will share the evaluation criteria below only to make it easier to visualise the dispute basis.

As there is no translation from the four-level table to the 10-point score, is it reasonable to assume that each level equals 2.5 points?

Regarding relevance, the comment received 4 points, which corresponds to level 2. In the post, we were discussing the possibility of merging all SOS posts and presenting a unified proposal. I brought up the point that, in my opinion, we were lacking estimates of cost and funding for each topic within it. Without it, we would risk approving a goal that was not feasible. This positioning was backed by content from the original Mission, Vision and Purpose post. I want to request a reassessment of my current score.

Regarding depth of analysis, the comment also received 4 points (level 2, acceptable). I would like to request a reassessment of my current score, based on the same points raised previously and the concept I outlined in my comment (strategic planning), specifically regarding the current structure (MVP and SOS), which lacked important definitions before moving to execution. L2Beats reinforced that in their comment.

Regarding Timing, Clarity and Impact, I understand that they are related to the previous items, but I also want to request a review. Specifically of “Impact”, as 2 points equals level 1.

Thanks in advance!

Title: Dispute

Delegate EzR3aL

Reason for dispute (please detail):
So I get these points as delegate feedback for one comment I made.

Relevance: 4 people quoted me and/or build their answer up on my comment in the proposal.
Depth of analysis: Not sure tbh what you expect here.
Timing: I made the comment 2 days after the proposal was posted and have been the 5th person to comment.
Clarity & Communication: I think I made it pretty clear what the source of the problem is about. Even with an example.
Impact: Again, 4 people quoted me and said that I have been saying whats the problem is about. But not relevant to you?

Title: Dispute

Delegate Name: Event Horizon DAO

Reason for dispute (please detail):

The rationales we’ve been providing have been consistently detailed and clear.

  • While the most common rationale for ArbOS Version 40 Callisto was along the lines of “no objection on my side” including SeedGov’s own rationale, Event Horizon provided the following detailed response:

  • On the Watchdog Grand Misuse Bounty Program again, many rationales from top delegates were a paragraph at most, Event Horizon provided a detailed and clear explanation of why we voted as we did including a detailed response for how similar proposals may be improved going forward. This is not merely a comment on length, but on content. Our rationales are extensively detailed and clear.


  • For the DRIP proposal, we highlighted, not only our overall rationale, not only the pros and the cons, not only proposed improvements, but also a full fledged debate with conviction scores, conviction deltas post debate, and an overall conclusion.

There are several other examples of the same level of elaboration by our delegation but the overall point should be clear. We struggle to see how this level of response is worth not even a single point.

In the Delegate Feedback, we’re grateful that SEEDGov has noticed that “Event Horizon has made significant efforts to upgrade the rationales and to add pre-vote feedback.” However, they cite a lack of “tangible impact” without specifying what that looks like. Several compensated delegates get by with “No objection” rationales, yet our extensive, curated, and quantified rationales broken down by points in favor, points against, debate, and conviction score do not qualify. It’s unclear what counts. Do rationales need to be liked? Replied to? This was never specified. What is clear is that there seems to be an inconsistent application of the rubrick.

The feedback then goes on to say that given the recent proposal, which Event Horizon co-authored, to reduce our delegation so that the DAO could focus less on our delegation size and more on what we ship for the DAO, we should not be included in DIP because it is experimental. This is puzzling. Delegates, including Event Horizon, voted on that proposal to reduce our delegation. Delegates also voted in favor of continuing Event Horizon. Delegates, crucially, did not vote on that proposal to cut support for our efforts. Event Horizon’s forum contributions ought to be assessed on their own merits. Bringing in this proposal, which ratified the DAO’s support of this experiment, is irrelevant and not a part of the DIP criteria.

Once we remove this proposal from the picture, it strikes us as a challenge to justify the assessment that our highly detailed responses are worth exactly the same as not posting at all. We believe that a fair reassessment of our comments, on their own terms, should result in a significantly higher score. Beyond that reassessment, any further clarity is appreciated.

Given Event Horion rightfully deserves some delegate feedback points, the following should apply:

  1. [RFC] Proposal to Adjust the Voting Power of the Arbitrum Community Pool & Ratifying the Agentic Governance Pivot - #3 by EventHorizonDAO
  2. [Constitutional] AIP: Constitutional Quorum Threshold Reduction - #29 by EventHorizonDAO
  3. [Non-Constitutional] Invest in Builders & Ignite ARB Demand with q/acc - #15 by EventHorizonDAO
  4. No Comments
  5. Agentic Governance Initiative [AGI] & Agentic Governance Initiative [AGI] - #5 by EventHorizonDAO & Agentic Governance Initiative [AGI] - #26 by EventHorizonDAO
  6. DeFi Renaissance Incentive Program (DRIP) - #72 by EventHorizonDAO
  7. No Comments
  8. No Comments

Finally, Event Horizon has been leading the Agentic Governance Working Group to co-create the future of ai governance with the community and delegates.