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

Larva

Hey!

As an internal policy, no action related to the DIP itself is incentivized. This has always been the case, and you can verify it as we have not even considered votes related to the program within the framework.

Tane

Federico’s comment ultimately contains an important suggestion based on their experience running similar programs, which we believe enriches the discussion.

The rationale you provided can be considered in-depth and contains a suggestion (although partially mentioned by @JuanRah):

“The program could evolve from a one-year initiative into a continuous support model. The allocated budget in this proposal could be reviewed after an initial six-month phase and then reused as needed.”

We have decided to assign some scoring to this comment, as you expanded JuanRah’s suggestion and demonstrated sufficient context when elaborating on the rationale.

In this case, the comment is mainly limited to follow-up questions. As we have mentioned before, this is not inherently bad, but it might be not enough to receive scoring (unless the question is particularly insightful or has an extraordinary impact).

It is important to note that obtaining scoring is challenging in a proposal like ArbOS Version 40 Callisto unless the delegate has a deep technical background and can provide observations aligned with that expertise. As can be seen in most comments, delegates generally do not have much to add beyond necessary due diligence questions before voting.

On the other hand, regarding the recommendations you mention—are you referring to this other comment? If so, it was posted just eight hours ago.

Ignas

In the image, we can see that the discussion is about the thread “AIP: Timeboost + Nova Fee Sweep.” Considering that the Snapshot vote on Approve the Nova Fee Sweep Action was part of the Agenda for Open Discussion of Proposals Governance Call on February 11 (and was not included in the agendas of the GRC meetings on February 5 or 7), it is very likely that the screenshot belongs to the February 11 call rather than the GRC on February 7.

As an additional note, in your other open tab, the text “January 28, 2025 - Open Discussion” can be partially read, further suggesting that the screenshot may not correspond to the date you mentioned.

As said above:

As an internal policy, no action related to the DIP itself is incentivized. This has always been the case, and you can verify it as we have not even considered votes related to the program within the framework.

The direction of your vote is not something we take into account when evaluating a rationale.

Regarding the budget, the fact that many delegates raised the same concern before you is precisely why we cannot assign scoring for it—insights must be unique and original.

On your last point, the Arbitrum Foundation already provided clarification in the initial comments:

The $100K per project functions as an estimate, meaning there is no commitment to spending that amount on each audit.

While the suggestion is constructive, note that it was previously mentioned by other delegates.

Also the thread in question is more about forming a working group rather than launching an airdrop:

We have noticed that many comments have overlooked this detail, which was clarified multiple times by the proposer.

Anyway, while reviewing your evaluation, we noticed that we didn’t apply the Presence in Discussions Multiplier (1.05x in your case) so your score has been updated.

EzR3aL

We refer you to a previous response that may be useful:

Now, two clarifications:

  • The discussions included in the Presence in Discussions Multiplier do not affect the eligibility of comments. Any comment in any forum discussion is eligible for scoring if it meets the parameters outlined in our evaluation methodology. This means that your comment can receive a score even if it was not made in one of the 11 proposals included in the multiplier.

  • The Arbitrum Audit Program thread was created on February 6:

JamesKBH

You’re absolutely right. We have updated the impact score to 7 in alignment with the other parameters.

1 Like