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

Klaus Brave

To begin with, we would like to clarify that the mere act of producing a podcast about Arbitrum does not automatically qualify for Bonus Points; rather, the impact it generates is the determining factor.

To expand on the criteria, we could say that there are three key items to consider when analyzing these types of contributions:

  • Does it feature a key stakeholder?
  • Did it achieve strong engagement metrics on social media?
  • Would you say it had a tangible impact on the DAO by influencing other delegates’ decisions?

In this particular case, we believe both podcasts featured relevant stakeholders for the DAO, but we are unable to observe metrics that support strong engagement.

This leaves us with the final question:

Would you say it had a tangible impact on the DAO by influencing other delegates’ decisions?

Since this is a somewhat tricky question, any impact should be clearly documented.

Regarding the first podcast, we have no elements to support such a claim.

Regarding the second podcast, the only potential evidence we have is the following statement:

First, we would like to clarify that Paulo’s comment was published on May 10th, which places it outside the evaluation window for the month under review.

Additionally, this statement raises a few questions:

  • @PauloFonseca, are you in a position to confirm that this podcast had a significant influence on the depth and clarity of your later comment?
  • Finally, @KlausBrave, could you confirm that you will not request retroactive compensation from the DAO or any DAO-funded program for the production of these podcasts?

We want to emphasize that, considering the monthly nature of the DIP and the fact that we haven’t yet had the opportunity to thoroughly evaluate Paulo’s comment, any determination regarding the impact of this particular podcast will be made during the May review.

Thank you for pointing that out! It has been corrected.

EzR3al

While @Ministrodolar has already provided some insights into the assessment of your comments, we’d like to clarify that we, as PMs, want to avoid penalizing delegates based on technicalities or rigid structures.

We understand that the subjective nature of this parameter can be confusing, particularly in edge cases like this, where many delegates are clustered around the 60–65 point range. Part of this work unfortunately involves making the tough call of leaving some contributors without compensation in a given month.

As outlined in the report, we now observe two differentiated categories of delegates/contributors participating in the program:

  • Those with a significant amount of voting power, who may also contribute to the DAO’s daily operations beyond voting. These individuals are key to maintaining governability by helping proposals reach quorum.
  • Those with lower voting power, whose voting activity contributes less to reaching quorum, and for whom this program focuses more on rewarding their contributions to discussions rather than voting itself.

In that regard, there are cases where the sum of a delegate’s voting power and their contributions throughout the month does not generate sufficient impact to justify compensation under this program.

That said, this does not mean that “small” delegates have no chance of earning incentives. In fact, the data shows the opposite: 17 out of 30 compensated delegates this month had less than 1M ARB in Voting Power.

For those who haven’t been able to meet the 65-point threshold recently, we’ve provided various suggestions for improvement. From our perspective, the small delegates who are succeeding should serve as benchmarks for both the quality and time commitment required. That’s why we encourage anyone below the threshold to double down on their efforts and look to those successful cases for guidance.

Finally, since it’s related to this dispute, we’d like to address Paulo’s question:

Indeed, the criteria for classifying a comment as valid or invalid follow a subjective and strategic approach. In general, we try to only consider the best contributions from each delegate to avoid situations like those raised by cp0x and Tane in our thread [DIP v1.5] Delegate Incentive Program Questions and Feedback. This criterion is applied uniformly to all delegates.

Tane

While the comment may meet the requirements to be considered valid, there are a number of reasons we took into account for not including it in the assessment:

  • The first suggestion, focused on an optimistic governance system similar to Lido’s Easy Track, is relevant and adds value to the discussion, but we had already assigned a score for a comment that included this same suggestion in the thread [Non-Constitutional] Service Provider Utilisation Framework.
  • Another factor to consider is that, due to the nature of the discussion and the low level of controversy surrounding the proposal, it is difficult to have any real impact on it. We understand that the suggestions go beyond the discussion itself, but it’s important to note that very few delegates received scoring in this thread.
  • Lastly, if there were a factor that we believe would justify considering the comment as valid, it would be the second suggestion related to the cap implemented in the DIP. As we’ve mentioned before, including the first suggestion in the assessment would (from our perspective) mean rewarding the same suggestion twice.
  • That said, we should also consider that if we had to score this comment based on what was stated above, we believe it would receive a lower score than the comments already included. This would result in a disadvantage rather than a benefit for Tane, in line with what you yourselves expressed in this comment.

While from our perspective this comment represents a due diligence task involving a series of questions to better understand the proposal, we generally find it difficult to quantify the value it brings to the discussion. We’ll go point by point to explain our position:

  • First of all, we don’t fully understand the claim about potential conflicts of interest. It might make sense if the committee members were part of specific protocols, but in this case, we’re talking about three “Arbitrum Aligned Entities” with no specific affiliation to any ecosystem protocol. In this sense, it might have been helpful to elaborate further on this argument.

  • As for the subsequent questions, we believe that public reporting is already implied in the inclusion of the Evaluation Partner role.

    From this excerpt, two things are clear:

    • The Evaluation Partner must deliver periodic reports
    • The Evaluation Partner must develop a public dashboard tracking all relevant metrics
  • In this particular case, other delegates had already asked about the metrics used to determine the program’s performance. (In fact, the comment right before Tane’s includes a question along those lines.)
  • As we’ve mentioned above, the proposal already included the creation of a public dashboard by the Evaluation Partner. In this case, we suggest reviewing the proposal details in depth before making comments.
  • We acknowledge that this is an interesting question. However, given that the committee will have a degree of discretion, it’s reasonable to expect that protocols that fail to fulfill their co-marketing obligations will no longer receive incentives. That said, considering the rest of the comment, we don’t believe this is enough to assign a score (especially not one that wouldn’t negatively affect the rest of the assessment).

We appreciate the detailed justification provided in this particular case. We’ll go through it point by point once again:

  • After a second review, we believe the dispute regarding Relevance is valid, and as such, we have updated that score to 7.

  • Regarding Timing, it’s not only about the number of days or the phase of the discussion (RFC, Snapshot, or Tally), but also when the contribution is made relative to the level of engagement the proposal/topic has already received. In this case, Tane’s comment is the 30th out of 34, which—while not inherently negative—is an indicator that the contribution comes “relatively” late in a discussion where several other delegates have already provided substantial feedback. That’s why some of the alternatives mentioned by Tane in this comment—such as strategic delegation of DAO Treasury ARB to active delegates, ARB staking, and direct interventions on platforms like LobbyFi (dialogue, control, or bans)—had already been discussed to varying degrees.

    This doesn’t mean we didn’t take into account the pros and cons analysis they included, but the relative value of that input is lower compared to the suggestion related to NEAR.

Once again, we appreciate the feedback you’ve shared with us. We’ll now proceed to analyze the final suggestions.

This is a somewhat tricky factor, as impact per se is difficult to quantify, although there are a number of elements we’ve been taking into consideration:

  • Impact on other delegates and their decision-making (e.g., being quoted by others).
  • Impact on the proposer and whether the suggestions led to changes in the proposal. (This also depends on the proposer, although we’ve noticed that well-reasoned suggestions with strong arguments tend to be taken into account.)
  • Timeliness of the feedback (related to the overall timing).
  • Expertise/background of the person providing the feedback. (If the person is an expert in the subject being discussed, their input will clearly carry more weight.)
  • Voting Power of the delegate (it’s well known that a delegate with higher VP is more likely to influence a proposal through their suggestions, as the proposer needs their support).

We may be overlooking something, so we welcome suggestions to expand or improve this criterion.

In this case, we are open to suggestions from the community. Our perspective on how to adjust Timing and Clarity in the Community so that they do not become gameable factors in the assessment can be found in the Bible 1.6, and we have also explained it previously here:

Good suggestion! Perhaps we could add some examples to the Bible. For now, we suggest using the comments with the highest score in this parameter as a benchmark.

We hope this response has addressed your dispute. Best regards!

Ignas

In this paragraph, we do not understand the statement “there is no allocation directly aimed at incentivizing users.” The very purpose of an incentive program is precisely to make the use of certain primitives more attractive to users. This is the point where we usually ask for a deeper analysis so that your argument carries more weight.

This suggestion had already been made previously.

We acknowledge that the suggestion is not bad; in fact, there have been several cases of protocols matching incentives (such as Curve). However, the large number of precedents regarding this suggestion indicates that it is not particularly novel.

In fact, this response from Entropy in the thread suggests that this possibility has already been considered (although not specifically as a way to reduce costs). It is worth clarifying that, so far, we have not found a reasonable and well-argued justification—neither in this comment nor elsewhere—explaining why the costs are high:

For the moment, this type of contributions (X threads) are out of the scope of the program.

Staking was mentioned by six other delegates prior to this comment.

Regarding the implementation of mechanisms like veTokenomics, while the suggestion is “novel” in the context of the discussion (i.e., no one else had mentioned it as an alternative), it lacks a solid rationale explaining why it represents a good option for the DAO. Therefore, the currently assigned scoring already reflects that it is merely a suggestion in the style of a “strategic direction,” since without a strong foundation or deep analysis of its benefits, the potential impact is limited.

cp0x

We understand this point. In fact, the reason we assigned scoring to this comment is because we believe you raised a valid point. However, to achieve a higher score in the depth of analysis parameter, we think you should have included all the research you mention directly in the comment. The fact that we are learning about this investigation through your dispute suggests that the comment could have been more thorough and revealing than it was—and therefore could have scored better across most parameters, including impact.

We remind you that, as an internal policy, any contribution related to the DIP is not considered in the assessment to avoid conflicts of interest. This is clearly stated in the Bible.

Honestly, it’s difficult to understand your point here, as the proposed framework does not refer at any point to the Arbitrum Audit Program but simply establishes an example scenario where the DAO requires an audit of a recently developed cross-chain messaging infrastructure component:

We think that the comparison made lacks relevance since the fund allocation mechanism is different. The proposed framework doesn’t seem designed to allocate large amounts of funds but to provide small amounts in specific proposals that do not justify undergoing the full governance process.

Well, in this case we will go point by point of the comment:

This question is fine, although it has been asked previously by other delegates.

Here, while we understand your suggestion, you have not provided sufficient evidence that vesting is an alternative that guarantees long-term capital retention. As we expressed to DonPepe in his report, the question remains: what prevents users from leaving once the vesting period has ended?

Again, there is not enough evidence to support this assertion. Comparing it to LTIPP does not guarantee that the total amount allocated was appropriate nor that funds were distributed efficiently.

Additionally, assumptions are made about the token’s price action (which has increased by 30% since this comment).

It is a valid question although somewhat difficult to answer without knowing the Distribution Partner.

It is already specified beforehand that the Evaluation Partner will provide a public dashboard to track the progress and results of the seasons:

In this case the proposer replied that it would not be beneficial to establish a limit.

This is your opinion and we respect it, but from our perspective, it is not a rewardable action.

In summary, out of the 7 items, two suggestions lack solid justification, one question was already asked by another delegate, one question whose answer was already in the proposal content, one expression of opinion regarding season cancellations, and one valid question about distribution (although still unanswered). Considering all the above, we do not believe this comment had enough impact on the discussion or the outcome of the proposal.

Regarding the GRC, we have not been able to find you in the Attendance Report that we usually share in the Monthly Framework. If you have any evidence that contradicts the report, please share it with us through this channel or privately if you prefer.

Zeptimus

Regarding this comment, we would like to emphasize that the reason we do not believe comments in this thread should be incentivized is because the participants are acting as Builders rather than delegates. Incentivizing people to comment in this thread would, in a way, undermine its original purpose.

Requesting success metrics (KPIs) and stronger accountability mechanisms are generally standard questions and/or contributions. In this case, besides pointing out their absence, there is no deeper analysis provided. In general, it is expected that a delegate is able to offer a more thorough analysis in order to receive compensation.

What would have truly enriched the discussion is if you had provided examples of the types of accountability mechanisms you would apply or metrics that could work within the framework proposed by Gabriel.

The same applies to the third suggestion — of course, we all want to improve the value proposition of the $ARB token, but it is not as simple as just stating it.

It’s worth mentioning that you have received 48 points for those tasks, which corresponds to what a delegate with your Voting Power should receive considering the framework.

It is also worth mentioning that the DAO has approved a degree of subjectivity in the assessment because the previous framework did not consider the quality of comments, which increased the potential for gaming the program (and therefore the noise in the forum).

We understand that not getting incentives may be frustrating, but as we stated in the report, especially delegates with low Voting Power need to make extra efforts to justify compensation of (at least) $3,000, since their impact on the DAO’s quorum objectives is considerably low.

In your personal case, to be honest, we do not see that the contributions made during April had sufficient impact to justify compensation from Arbitrum DAO.

Paulo Fonseca

We understand that what you refer to as a ‘secret meeting’ was not an official ArbitrumDAO event. Beyond the fact that some matters discussed there may have ended up reflected in the Vision, we do not see that this piece of information you bring into the discussion in your comment has a significant impact on the DAO.

This was already clarified in the report; our position remains unchanged.

As you rightly mention in that thread, the Telegram chat does not belong to the DAO, and in that same thread, a member of the Arbitrum Foundation can be seen stating that the matter did not warrant going through the usual governance process. Therefore, no comments in this thread have received any scoring.

Here subsequent events tell us the opposite:

  • Tamara (who participated in this initiative as a contributor) mentions that it wouldn’t be a good idea:

  • Later, Entropy confirms this by consolidating the communication roles into a single one.

We understand your point; indeed, since the comment was not very deep or detailed, the reason for its inclusion lies precisely in the fact that other delegates used the same argument later on.

That said, comparatively speaking, we believe the score assigned to your comment is consistent when observing the scoring of other comments deemed valid in this thread.

We have no evidence to corroborate such a claim; in fact, the election results indicate that Pedro was not elected. We also do not consider retroactive compensation based on a rationale to be appropriate. In any case, the decision to include Pedro as the fourth member of the OAT was made by the three existing OAT members, who have that authority by mandate.

This dispute was addressed in a timely manner. If anything has changed since then (for example, if the holding has been delegated to the null address), please let us know.

LobbyFi is not eligible for not voting in the Security Council elections, and zer8 is not eligible due to insufficient voting power.

It is worth clarifying that for your contributions related to ETH Bucharest, you have received a total of 45 points in 3 months, which represents the highest amount of points this program has assigned for an individual initiative.

It is also important to note that without the Bonus Points awarded this month, the compensation would have been $0 instead of $4,243. Together with the points awarded during February and March (which allowed you to reach Tiers 1 and 2), this represents, in our view, a sufficient monetary compensation.

Finally, we remind you that this contribution is a direct consequence of an inefficiency within the DAO, since a budget and sponsorship were approved for an event without an appropriately compensated Lead to carry it out. In this regard, expecting this program to fully fill that gap as a 100% representative of reality is an unfair expectation.

web3citizenxyz

This rationale has received 13.6 points versus the 10 points that were typically assigned to all the rationales in a month under the previous framework. We agree that it is a good rationale; however, considering its low potential impact and the points mentioned above, we believe the scoring awarded in this case is consistent.

As we have stated in the report, the main suggestion revolves around a point that has been mentioned on multiple occasions, which from our perspective, does not add value to the preceding comment nor to the discussion at hand. We maintain our position on this matter.

This is another comment for which we have justified exclusion. We observe an analysis regarding whether it is possible to mitigate the effects of LobbyFi (an issue that, as you rightly point out, has already been analyzed by several delegates) and finally some questions; however, these questions have not led to further engagement from other delegates.

Curia

We will provide a rationale for the score assigned in this case:

  • Concerns regarding long-term sustainability or the budget size had not only been widely mentioned but also lacked a solid argument.
  • Regarding the large number of requested details, the proposer has made it clear that a rigid program could harm the ultimate goal.
  • As for accountability, it is worth noting that the proposer has arranged for the creation of an Evaluation Partner, and furthermore, the suggestion, despite being well justified, had no impact on the proposal.
  • The shared rubric is the main reason why this comment received a score.

Having said all this, comparatively speaking, we believe the score assigned to your comment is consistent when observing the scoring of other comments included as valid in this thread.

We do not see any elements to support the claim that “there was a suggestion that strengthened the proposal,” as no changes were made to the proposal based on this comment.

Paulo Fonseca

Thank you for letting us know; the link was incorrect. It has now been fixed. It was supposed to be the link to the JoJo report, which has always been public.

That said, since this is not the first time you have disputed another delegate’s scoring, we want to make it clear that we will not allow disputes to become a perverse mechanism where delegates target each other through the DIP (not saying this is your case, we just want to prevent this). For this reason, we will no longer process disputes regarding the scoring of third parties.


Having addressed all disputes and more than four days having passed since the report submission, we hereby consider the dispute period closed.

Thanks everyone for your feedback!