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

June Participants

For the April iteration of the program, 79 participants enrolled, 66 of whom met the regular requirements to qualify.

You can see the full list here.


Parameters Breakdown

Snapshot Voting

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

  1. Adjust the Voting Power of the Arbitrum Community Pool & Ratify the Agentic Governance Pivot
  2. Wind Down the MSS + Transfer Payment Responsibilities to the Arbitrum Foundation
  3. Reallocate Redeemed USDM Funds to STEP 2 Budget
  4. Updating the OpCo Foundation’s Operational Capability
  5. Let’s improve our governance forum with three proposals.app feature integrations
  6. Arbitrum Treasury Management Council - Consolidating Efforts
  7. [Constitutional] AIP: Remove Cost Cap on Arbitrum Nova

Tally Voting

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

  1. DeFi Renaissance Incentive Program (DRIP)

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

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 June, 6 proposals were considered:

  1. Entropy Advisors: Exclusively Working with the Arbitrum DAO, Y2-Y3
  2. Proposal: Adjust AGV Council Compensation to Reflect Role-Based Governance Commitments
  3. Arbitrum Research and Development Collective V2 - Extension
  4. Arbitrum Treasury Management Council - Consolidating Efforts
  5. Updating the OpCo Foundation’s Operational Capability
  6. Proposal: Extend AGV Council Term and Align Future Elections with Operational Cadence

To get the multiplier a delegate needed:

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

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

For 20% (1.20) = At least 5 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.


June Results

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

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

  • Tier 1: 1 delegate. (4.54%)
  • Tier 2: 5 delegates. (22,73%)
  • Tier 3: 16 delegates. (72,73%)
Delegate TIER PUSD
Tekr0x.eth 1 6,718.92
L2Beat 2 5,032.20
Jojo 2 5,000.34
MaxLomu 2 4,341.72
Lampros DAO 2 4,286.75
Tane 2 4,219.29
TempeTechie 3 3,205.39
BlockworksResearch 3 3,203.57
GFXLabs 3 3,149.00
Tamara 3 3,143.19
olimpio 3 3,127.75
Gauntlet 3 3,127.00
Camelot 3 3,126.82
Griff 3 3,125.84
GMX 3 3,117.50
Reverie 3 3,106.00
Areta 3 3,075.00
Bob-Rossi 3 3,070.78
CastleCapital 3 3,064.03
StableLab 3 3,049.43
AranaDigital 3 3,035.00
404DAO 3 3,008.51
$79,334.03

The total cost destined for the delegates this month would be $79,334.03.

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.

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 15 Bonus Points:
    We would like to highlight two “extraordinary” contributions:

  • Tekr0x received 20 Bonus Points: During the analysis month, the delegate continued contributing to the Arbitrum Gaming Ventures initiative through the coordination of Welcome to the “Next Level” - A New Playtest Series for the DAO with the AGV. For this reason, we have awarded 10 Bonus Points.

    Also, for the organization of the Delegates Dinner during ETHcc, we have awarded another 10 points.

  • LamprosDAO received 20 Bonus Points for their notable contribution with the Orbit Chains Dune Dashboard Initiative this month. We encourage the delegate to keep expanding the dashboard.

  • TempeTechie received 15 Bonus Points: During the analysis period, the delegate actively contributed to the ETHMilan initiative by coordinating a Delegates’ Dinner and volunteering at the booth.

  • StableLab received 5 Bonus Points for their post-mortem in the [CONSTITUTIONAL] Register the Sky Custom Gateway contracts in the Router proposal.

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.

Delegate Suspension

During June, a particular situation arose involving the @cp0x delegation, who posted a tweet related to the Arbitrum Gaming Ventures (AGV) initiative.

The tweet included an image that could be interpreted as AGV stealing funds from the ArbitrumDAO. This type of accusation—especially when not supported by proper due diligence—undermines the collaborative and constructive spirit of the Arbitrum DAO, while also damaging the reputation not only of the individuals involved in the proposal but of Arbitrum as a whole.

As Program Manager, SEEDGov has the responsibility to mediate in such cases, particularly when the party involved is a delegate potentially eligible for incentives under the program.

The first step we took was to gather feedback from different stakeholders, Arbitrum Aligned Entities, and delegates who have a greater or lesser correlation with the AGV and all of them expressed the need to take disciplinary action against the delegation.

We then organized a meeting with the individuals behind the delegation to hear their side of the story and allow them to reflect on the situation. In that discussion, the delegation acknowledged that the image could be interpreted in an unintended and potentially harmful way. In order to avoid multiple interpretations and prevent escalation into debates over imagery, while recognizing that a significant portion of the community may have perceived reputational harm, the tweet was deleted.

From SEEDGov’s perspective, while the action itself represents a serious lack of respect towards key stakeholders and contributors within the community, the delegation’s acknowledgment of the mistake and subsequent correction serve as mitigating factors in determining the final disciplinary action. We recognize that the @cp0x members demonstrated a willingness to reflect on their actions.

With all this in mind, SEEDGov has decided to suspend the cp0x delegation for two months (June and July), during which they will not be eligible for any incentives under the program. As of August, they are welcome to continue participating in the program, with the understanding that should a similar situation occur again, the Program Manager reserves the right to take any action deemed appropriate.

Disclaimer: As Program Manager, SEEDGov is committed to fostering a healthy, respectful, and constructive environment. Under no circumstances is our intention to censor anyone. All delegates are encouraged to express critical views on any discussion or proposal, provided it is done respectfully and constructively, and without unwarranted accusations—especially those implying criminal conduct.

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

User 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: Curia

Reason for dispute:We noticed that only one of our feedback submissions was counted for the June DIP on the Karma dashboard. We believe another piece of feedback we provided during that period should also be considered. Would it be possible to take another look? Let us know if you need any links or details from our side. Thanks!

1 Like

Title: Dispute

Delegate name: jameskbh

I want to start by saying that my take on governance is to try to provide value in the processes & proposals where I can contribute to a better outcome.

I want to dispute the low score given to my comment on Entropy Advisors: Exclusively Working with the Arbitrum DAO, Y2-Y3 post. As my current understanding is that each evaluation focuses on the value added to a specific proposal, I base my case on that.

The current score is:

Relevance: 3
Depth of Analysis: 3
Timing: 3
Clarity & Communication: 3
Impact: 2

This score is on a scale from 1-10, and, AFAIK, it is correlated with the previous scale, from 1-4 (The picture below)

The current score (3s and 2s) would be the equivalent of (1 (low) and 2 (acceptable)) on the table above, as a means of comparison.

As my comment was:

  • quoted by other delegates and helped to shape the change regarding an important part of the proposal;
  • acknowledged as a notable contribution in the Delegate Feedback Reporting (image below);

I believe the current score does not reflect this reality, and the impact, relevance, depth of analysis and timing components of it should be reviewed.

Thanks in advance!

2 Likes

Title: Dispute

User name: Jose_StableLab (StableLab)

Reason for dispute (please detail):

Thank you SEEDGov for the June 2025 Results of the DIP. For this month, we are surprised StableLab didn’t qualify for the incentives. Particularly, as after the Sky engineering team discovered the incorrect payload value inputted in the Cancelled Sky’s USDS custom gateway Proposal, StableLab coordinated with the Tally team the UI labelling of the Proposal as “Canceled” and mobilised all delegates to vote against it. Shortly after, we published the Post Mortem, including an analysis on the missteps that led to the publication of an incorrect payload for the Proposal.

It is difficult for us to justify how this thorough delegate efforts were overlooked in June’s evaluation for StableLab Incentives. In this case, the Post Mortem post did not make it to neither as top monthly StableLab’s contributions nor bonus points. We consider this post has had major measurable impact in exposing the risks associated with the custom gateway governance process. Proofs of this impact are that the Tally team has already corrected the Submission UI widget to correctly flag failed simulations as a result of our report (image), improving the overall governance security for the Arbitrum ecosystem.

In addition, we believe our thorough communications regarding the complexity and risks of the process has sparked delegate concerns, leading to the proposal to create a Maintenance Upgrades Working Group to discuss a solution to this problem and create a streamlined custom gateway governance procedure that can reduce complexities and risks.

When StableLab initially approached SEEDGov regarding the Delegate Incentive Program, they emphasized the view that delegates do not necessarily need to contribute to all topics but need to be active and professional in their areas of expertise. We are, however, confused how is this vision true when StableLab’s area of expertise - Governance Facilitation - is blatantly overlooked for Delegate Incentives when carried out professionally and diligently, leading to the deployment in Arbitrum One of one of the most critical assets in the industry, USDS, while raising and helping fixing security issues for an also critical DAO governance procedure.

We believe these efforts, particularly the Post Mortem post, should be appropriately evaluated when considering StableLab’s June compensation.

3 Likes

Title: Dispute

Delegate name: todayindefi

We were on many governance calls this month under the screen name Brook, but didn’t get bonus points for that attendance.

We’ve already sent a direct message and SeedGov has acknowledged they will look into this, just replying here as well for the public record to show our participation.

1 Like

Title: Dispute

Username : tane

Reason for Dispute :

We are submitting this dispute regarding the June 2025 Delegate Incentive Program (DIP v1.6) results, particularly concerning the evaluation of our contribution to the following proposal:

“Proposal: Extend AGV Council Term and Align Future Elections with Operational Cadence”

Our feedback on this proposal was substantive, timely, and led to a direct modification of the proposal that was ultimately passed. We believe our contribution satisfies multiple high-level rubric criteria under the Delegate Feedback system.

However, based on the final DIP results, it appears that no points were assigned in connection to the comment on this proposal, despite it making the impact to the discussion.
Thus, we respectfully assert that our feedback meets these conditions for counting and should have been scored accordingly.

We kindly ask the Program Administrator to revisit the evaluation of our comment and consider updating the DF scoring to accurately reflect the documented impact.

Thank you for your attention to this matter.

1 Like

Thank you so much for the great report!!

Given the minimal engagement seen in recent governance activities:

  • @404DAO @Cole_404 only made a single comment throughout the month.

  • @Areta and @gauntlet were noted for having limited discussion participation, even if some contributions were relevant.

  • @KlausBrave ’s feedback was called out as lacking impact or clarity.

  • Only a few, such as @Tane , were recognized for meaningful, high-quality engagement and impact on governance outcomes.

, it’s increasingly likely that some of these delegates have shifted their focus towards their work in House of Stake at NEAR.

1 Like

Hey everyone!

Curia

Hi @Curia !

We reviewed your comment, but while it was extensive, we believe it mainly focused on requesting KPIs, budget details, suggestions about reporting, etc.

Overall, we don’t see how this comment contributed to or impacted the discussion — particularly since the main and most relevant concern you raised (Entropy’s discontinuity) was later addressed by the proposer.

Jameskbh

Hi @jameskbh

Thanks for the feedback. However, we respectfully disagree that the current scoring is inaccurate.

The quotes you received (at first glance) came from StableLabs, Entropy, and a self-quote within your rationale.

We want to note that although your comment was acknowledged in the report, the original idea of distributing the 15M ARB based on milestones came from Tané (the first comment in the thread). We decided to include your comment because it helped build consensus and because the first part of it also added value to the topic. That said, we maintain our current scoring.

StableLabs

Hi @Jose_StableLab !

When evaluating StableLab’s contributions to the USDS inclusion in the native Arbitrum bridge, we had initially considered scoring it in July, since the Tally vote concluded that month (this has been a common practice throughout the program). However, we failed to take into account that the post-mortem and everything you mentioned in the dispute occurred in June.

Given this, and taking into account StableLab’s previous engagement, we believe it is fair to assign 5 Bonus Points for June.

We’d like to clarify that the rest of the contributions related to the USDS inclusion will still be considered as part of the July evaluation.

TodayInDeFi

Hi @TodayInDeFi

According to the attendance records (both Huddle’s and our internal tracking), Brook is listed as an attendee of the OPEN DISCUSSIONS FOR PROPOSALS call on March 6, 2025. The delegation received 0.781 Bonus Points for this contribution.

Tané

Hi @Tane

We agree — your comment had a significant impact and was genuinely overlooked in our review. We’ve now assigned a score accordingly.

Thanks for raising this!


We’d also like to clarify that we received two additional private disputes:

  • In the case of @oni, we decided to assign a score to a contribution we had previously overlooked.

  • In the case of @404DAO, although only one comment was submitted, it was substantive and offered a distinct and genuine perspective — proposing that the ARDC be extended as a transition phase while acknowledging the need to revisit the applied model. While the original score didn’t qualify the delegation for Tier 3, we’ve decided to adjust the scoring after internal review.

    That said, we’ve noticed a decline in this delegation’s participation in recent discussions. We encourage 404DAO to increase engagement in the coming months by focusing on verticals where they feel they can add meaningful value.

2 Likes

Thanks for getting back to us and reviewing our comment.

We wanted to clarify that we do feel our feedback added value to the discussion. It went beyond just asking for KPIs or budget details. We raised points about how to evaluate outcomes from past initiatives like STEP and the staking working group, and how to define success for upcoming programs like DRIP. These questions are core to ensuring the DAO allocates resources effectively.

We also touched on how Entropy’s work aligns with broader DAO strategies like the SOS framework, and flagged topics around the delegate–service provider relationship and exclusivity.

One point we believe is particularly important is the question of continuity. We asked what would happen if the proposal didn’t pass. That’s a key consideration for delegates, and the fact that the proposal later addressed it shows it was worth raising. Questions like these help the community make better-informed decisions.

Title: Dispute

User name: WinVerse (DAOplomats)

Reason for dispute (please detail):
Thank you for putting this together, SEEDGov. We appreciate the time and effort you put into this. While our comment on ARDC V2 was overlooked, we are, however, unsure why our comment on the Entropy’s Y2-Y3 proposal was scored poorly, given it did make a considerable impact heading into Snapshot voting.

Here was our suggestion on a major aspect of their proposal – the 15M ARB structure.

And this was Entropy’s reply to the comment that ultimately led to them adjusting the 15M to include negotiating a milestone-based unlock with OAT in their proposal’s V2 update before the Snapshot vote.

It is difficult to come to terms with how this comment was scored poorly during the June evaluation for DAOplomats’ incentives. Saying it was discussed by Tane in the Delegate Feedback report is flawed. They gave a one-liner on going milestone-based with the 15M but focused their cost feedback on a breakdown of costs rather than the vesting, so it was neither discussed nor addressed by Entropy in their initial response to the comments. We consider our post had a measurable effect on the overall proposal, and seeing that it ultimately prompted a response from AJ on behalf of the OAT regarding negotiations with Entropy, it definitely should be looked into.

We believe our effort on Entropy’s Y2-Y3 proposal should be properly evaluated when considering DAOplomat’s June compensation.

Curia

While Entropy participated in the Staking Working Group, the initiative itself stemmed from a separate proposal: ARB Staking: Unlock ARB Utility and Align Governance. Our understanding is that Entropy mentioned the working group because they were involved, but they were not leading it — that role was carried out by the Tally team. As such, we don’t believe Entropy should be expected to evaluate the outcome of a working group they did not coordinate.

Regarding DRIP, it is a separate proposal that will have its own parameters for success. Entropy has already stated that they are responsible for the program’s execution, which makes it straightforward for the DAO to evaluate its performance and determine whether the allocated funds were effectively used.

Overall, we find that these points — while broader in scope — have limited direct relevance to the proposal at hand. The DAO will be able to assess the outcomes of any initiative in which Entropy serves as Program Manager or lead facilitator based on the specific metrics established in each case.

This is another area of concern from our perspective. The comment asks Entropy to explain how their work aligns with DAO-wide objectives — yet such objectives have not even been defined at this stage. It is difficult to expect alignment when the direction itself remains undefined.

We agree that this was a valid concern — in fact, we acknowledged it in our previous response. However, we do not believe this single point is sufficient to warrant a higher score for the comment overall.

DAOplomats

Hi @Winverse

Tané’s comment was simply one example. Jameskbh also raised the need to define clear milestones for the 15M ARB bonus proposed by Entropy:

In the case of DAOplomats, we acknowledged that your comment expanded on that idea with a concrete, novel suggestion, and that the rest of the post included some viable suggestions. That said, we respectfully disagree that the score provided was lower than what the comment merited. The final solution proposed by Entropy differs significantly from DAOplomats’ suggestion, and given the number of delegates who raised concerns about the bonus and requested milestone conditions, we believe it is an overstatement to characterize your comment as having had a “considerable impact” that would justify a higher score.

1 Like

Thank you for taking the time to provide a detailed response. We appreciate the effort you put into reviewing feedback and maintaining transparency in the DIP process.

That said, we want to clarify why we still believe our comment was relevant and deserved consideration.

While it is true that Entropy did not lead the ARB Staking Working Group, they did present it as part of their contribution in the proposal. Since they highlighted their involvement, we believe it is fair to ask how the initiative performed. Even if they were not the main coordinator, understanding the impact of initiatives they participated in helps the DAO evaluate the effectiveness of their work and determine whether an extended mandate is justified. This is particularly important when the DAO is being asked to approve a two-year engagement with an increased budget and token alignment package.

Similarly, while DRIP is a separate proposal, Entropy is responsible for its execution. Our questions about success metrics and evaluation were intended to ensure that the DAO can track performance and outcomes going forward. These questions are not outside the scope of this proposal. They are part of assessing how Entropy’s future work will be measured and how accountability will be maintained.

We also raised the topic of alignment with DAO-wide objectives, such as those discussed in the SOS framework. While we understand the DAO has not yet finalized these objectives, we believe that is exactly why this kind of question is important. If a contributor is requesting a long-term mandate, it is reasonable to ask how their work will align with the evolving strategic direction of the DAO. Our intent was not to critique the absence of a finalized plan, but to invite a forward-looking conversation.

Regarding continuity, we are glad this point was acknowledged. However, we do feel that the full set of questions we raised contributed to the quality of the discussion and encouraged more clarity in the final proposal. While not every question was addressed in detail, the comment was thoughtful, grounded in the proposal’s content, and aimed at helping the DAO make a more informed decision.

We are not trying to dispute the system, but we do want to understand how feedback like this focused on structure, outcomes, and alignment is evaluated within the DIP process.

We would really appreciate further clarity on how feedback is assessed so we can continue contributing in a way that is both helpful to the DAO and aligned with DIP expectations.

1 Like