Proposal - Delegate Incentive Program (DIP)

Hey @cp0x !

Thanks for your thoughtful message and for taking the time to walk through each of the stated goals. Let us address each of the points raised, one by one.

When this proposal was approved, it was under the assumption that the DAO would continue growing in both delegates’ participation and responsibilities. The target of “50 delegates” was meant in the context of having 100+ contributors competing for those spots.

With the DAO’s shifting priorities and reduced operational burden for delegates, we believe this original goal may no longer be fully aligned with the current context. It’s important to note that this proposal was approved nearly 9 months ago, and naturally, in a fast-moving environment like crypto, some expectations become outdated.

Also, SEEDGov does not control delegate activity nor the overall level of engagement in the DAO. Therefore, in months with less activity, a smaller number of incentivized delegates is not only expected — it’s also reasonable. Otherwise, we’d be distributing funds just for the sake of it.

Regarding the numbers: as shown in the May report, 78 delegates applied to the program — up from 61 in October. That’s a 27.86% increase in registered participants over the first 7 months of the program.

While not all delegates are actively contributing, engagement — measured by participation in the program — has indeed increased. Many delegates may be passive or less active due to uncertainty in rewards, which is something we’re actively addressing. But in terms of total applicants, the program is growing.

This might be a misunderstanding: the Average TP Rate is calculated only among rewarded delegates, not all applicants. Including all applicants would be misleading, especially since many towards the bottom of the ranking are no longer active in the Arbitrum DAO.

Between November and May, the average TP rate among rewarded delegates was 79.23%, with 19,411.62 points awarded across 245 rewards. So this KPI can be reasonably considered met.

That said, we agree the DIP needs new KPIs that better reflect the DAO’s evolving context, and we plan to introduce updated metrics in future iterations.

This has been formally met. And based on the rationale provided and the data in our midterm report, we believe the changes achieved their intended goals. Naturally, we welcome feedback to continue refining them.

On Operational Execution

Let us provide context on some of the delays:

  • November: All delegates had to go through compliance, which delayed payments.
  • January: Limited team availability due to holidays pushed results and payments.
  • May: Payments were executed on June 26, though the public thread hasn’t yet been updated — we apologize for the oversight.

A few additional considerations:

  • When we originally set that timeline, it was admittedly optimistic. This was the first time we would fully assess contributions (beyond mere comment-counting), and we weren’t sure how long it would take.
  • Even after adding individual reports — a major additional workload — we’ve maintained similar delivery times.
  • There’s a 4-day dispute period, and SEEDGov no longer controls payments directly — the AF now manages execution, which adds 1–2 days of buffer.
  • The phrasing used was “expected” rather than “guaranteed”, acknowledging some flexibility in timelines. We believe it’s more important to ensure accurate and fair assessments than to optimize purely for speed.

We aim to address all disputes within four days, collectively. Most of the examples cited fall within that range or are slightly beyond it.

As for follow-ups, we often choose not to engage in extended back-and-forth after providing a final decision, especially when the dispute involves subjective parameters. Once a judgment has been made and communicated clearly, the conversation has, by definition, concluded.

We truly appreciate the feedback and the spirit in which it was delivered. We also welcome any additional questions or clarifications in private — especially related to metrics — as we believe it’s important to avoid the spread of inaccurate data.

Thanks again for the engagement and commitment to improving the program.

Warm regards,

SEEDGov

1 Like