Treasure Delegate Communication Thread

After consideration Treasure’s Arbitrum Representative Council (ARC) would like to share the following feedback on the proposal:

Multisig Support Service (MSS) Elections

We have divided our vote into two sections. The thinking behind this is because the top 3 nominees will have increased responsibilities and duties, that the vote for these nominees should hold a greater weight. The top 3 candidates have received 12.1% each of our vote, while the remaining 9 received 7.1% of our vote. We have picked the following candidates:

  1. Alex Lumley
  2. JoJo
  3. Xavier Finlayson
  4. Frisson
  5. Castle Labs
  6. Cattin
  7. Ultra
  8. Den Technologies Inc
  9. Sinkas
  10. Disruption Joe
  11. Lindsey Winder
  12. 404 DAO
1 Like

The ARC’s vision on historical incentive programs and its future

Treasure’s Arbitrum Representative Council (ARC) would like to share our vision on the current state of incentive programs, more specifically all STIP variants and the LTIPP, and our vision of what an ideal future incentive program would look like. The reason we are sharing this now, is because we want to reflect and state our opinion on the state of incentive programs and to encourage having an open discussion about this topic before any new incentive proposals go live. We will first share some historical context of pain points that we experienced, to then be able to give recommendations towards a system of incentives that is more data-driven, and has a higher degree of accountability and flexibility.

Proposal Voting
When looking at the STIP we believe that the approval structure of STIP proposals is fundamentally flawed. The expectation placed on delegates to conduct detailed analyses of user incentive programs and to vote on each proposal is unrealistic and counterproductive. The STIP-Bridge tried to solve this issue by introducing the ‘optimistic voting mechanism’, but our concerns
that it could lead to a higher degree of passive acceptance by delegates (while still placing the review burden on them), proved to be true. In fact, there were only two delegates (Seed Latam and L2BEAT) that challenged the proposals of projects and exclusively did so on the basis of the ARDC recommendations. This not only means that the delegate basis that challenged projects was very small, but also that the ones that did choose to challenge proposals did so on the basis of an external body of review. Effectively, the review of proposals during the STIP.B (the challenge) has largely been outsourced to a single entity (the ARDC), and arguably so has part of the possible blame that could come at the cost of challenging a proposal; as can also be seen by the argumentation for the challenge given by these delegates, such as: ‘our posting of the challenge is not a statement as to whether or not this application should be funded, but merely an administrative act to solicit delegate input’ and ‘Following the ARDC recommendation’. The conclusion we take from this, is that a more streamlined voting process should not come at the cost of proper review.
Besides the time intensive and possible political pressure reviewing proposals puts on delegates, there is also the matter of expertise. If we want to grow Arbitrum, we need incentives to grow with it. Expecting all delegates to have subject matter expertise on all verticals and sectors within Arbitrum is an unrealistic ask. For this reason, the council and advisor structure were introduced in the LTIPP. Although this is definitely an improvement to all STIP voting mechanisms, there is still not enough flexibility and room to iterate on incentive structures for specific sectors; but also, more generally.

Data collection
The data collected and provided through STIP rounds proved to be insufficient to use for incentive structures that have come after it, and there is not enough research done on STIP data to measure the effect of the STIP on network growth. This is especially worrisome considering that the top 10 wallet addresses that received incentives through the STIP have gotten a combined 18.43% (6.22 million $ARB) of all the incentives, and the top 100 wallets 44.83% (15.43 million $ARB). Some projects took it upon themselves to provide data on their STIP incentivization, which is also problematic considering it will lead to data being used differently by projects and therefore making them less comparable to each other, and other non-incentivized projects.
We have data that we do not effectively use, while also continuing to fund incentive programs and iterating on them merely on an experiential and theoretical basis. We need data and analyses, to be able to compare and iterate on incentive structure mechanisms. Analyses on STIP and LTIPP metrics should be done, these analyses should be debated by the DAO and referred to for the creation of future incentive programs.

Election structure
For the sake of decentralization and democracy within the DAO, we think that all major positions should be voted for by the DAO. This becomes ever more important if we want to grow the DAO, and delegate more responsibility away from current DAO delegates towards representatives with subject matter expertise. In relation to the previous incentive structures, this means that roles such as the PM and the Data Provider would become electorally decided.

Feedback structure
The creation of the council and advisors for the LTIPP has been a significant improvement from having a ‘direct DAO democracy’. Advisors have been helpful in analyzing and iterating on proposals together with relevant parties. Yet, a communication divide seems to have impacted the advisors’ ability to ascertain clarity on the (approval) requirements of the council. Partly, because the evaluation criteria in the rubric were qualitative and therefore subjective in nature. For instance, there was a lack of clarity regarding what types of incentive mechanisms could or could not be used. The reason that seems to be at the cause of this is that this was a reaction to the STIP rules being too stringent, and therefore inhibiting projects’ abilities to create innovative and project/vertical specific incentive designs.

Conclusion
To address these issues, we propose the establishment of a professional, well-funded structure dedicated to overseeing, refining, and promoting best practices for user incentive programs on an ongoing basis. This entity would function similarly to for instance OpCo, AVI and the GCP. The Easy Incentive Program (EIP) is a solid piece of infrastructure that could in part set us on our way to achieve this vision. Namely, the proposed dApp has the ability to create ‘program categories with independent budgets, councils, and applications.’ Working towards the creation of independent incentive programs means that:

  1. Incentive programs can be created independently and approved through a DAO vote, but can also be wound-down without it impacting the overarching incentive structure altogether. This gives the DAO more control and flexibility on what to fund and when, thus being able to continuously keep incentivizing based on market needs (i.e. data-driven).
  2. Increased competition will improve the effectiveness and ROI of incentive programs. By having multiple concurrent incentive programs, the DAO can learn and iterate way faster on the effectiveness of various incentive structures and programs. In turn, this way the DAO is also able to reward the most effective members within an incentive program, as well as reward and pursue effective incentive programs as a whole.
  3. There is a more viable argument for the DAO to delegate power and agency towards independent councils. Projects applying for incentives will benefit from this, because the team reviewing their proposals will have more subject matter expertise and will thus be able to help them perfect their incentive proposal better than a ‘general’ council. Delegates can be relieved of having to review individual proposals and merely have to review these independent incentive programs for the same reason that more confidence can be placed in these subject matter experts, but also because there are actual implications to how an incentive program is being ran (i.e. the incentive program as a whole can be reviewed by the DAO, held accountable and have their budget be adjusted accordingly). This puts more responsibility in the hands of the council in having specific incentive programs succeed.
  4. There is more freedom for incentive programs to create their own rules. The STIP showed to be too stringent in its rules to be able to nurture innovation, while the freedom in the LTIPP caused the advisory and council bodies to not be able to sufficiently create and communicate objective measures for feedback and review. Smaller and more independent councils create the ability to create tailor made forms of review and approval, such as a more objective and clearcut rubric.
  5. It removes direct conflicts of interest for delegates and builders within Arbitrum. A lot of the delegates within the DAO are also building their own projects on Arbitrum, and have a responsibility to both their own project and Arbitrum. In terms of a general incentive proposal, the projects with a larger delegate base will always have an enlarged influence and can therefore impede on innovation by attracting more incentives towards them and/or less towards possible competition or other (especially newer, and developing) verticals. By creating independent incentive programs, contrary to the general incentive programs, there is a collective interest to create a successful incentive program to be able to continue to receive funding.

Independent incentive programs can cause chaos if not done right, and have delegates lose oversight of what is going on. For this reason, an overarching oversight committee and data provider(s)/analyst(s) should be instated. The oversight committee should be responsible for general oversight, an advisory body for the setup of new incentive programs, communication between the DAO and the incentive programs and other administrative tasks. The Data Provider is there to collect and provide data, processing this data and standardizing this data across projects and councils, to be able to accurately inform the oversight committee and the wider DAO on projects’ and councils’ effectiveness on a data-driven basis.

edit: tagging @GFXlabs @404DAO @WintermuteGovernance @coinflip @JoJo @seedlatam @CastleCapital @Matt_StableLab @paulsengh for visibility.

2 Likes

Improving Predictability in Arbitrum DAO’s Operations - [FOR - Improving Predictability]

We support the “Improve Predictability” initiative, believing it will streamline governance, alleviate pressure on delegates, and ensure smoother, more coordinated operations. While we acknowledge potential coordination challenges in implementing this proposal, we consider it a worthwhile endeavor.

Conversely, we oppose the proposed “Approval Process.” This process introduces gatekeeping, increasing pressure on delegates through pre-proposal support requests without significantly enhancing the overall procedure. We share the concerns that smaller participants may be overlooked, potentially impacting the inclusivity and fairness of the governance process.

Subsidy Fund Proposal - FOR

We are voting FOR this aligned initiative aligned with our expressed sentiment during Snapshat. The adjustments and inclusion of a buffer all seem reasonable, and we are still in overall alignment with the direction of travel for this initiative.

Gitcoin strongly supports the ARC’s vision for the future of incentive programs on Arbitrum. The proposed shift towards independent, data-driven incentive programs aligns well with our mission of building and supporting open source ecosystems.

We have been working with @lindsey @Matt_StableLab and the respective teams at Hedgey/StableLab and look forward to seeing how this tool can provide value to not only the LTIP but the wider ecosystem of incentive programs across Arbitrum DAO.

2 Likes

After consideration, Treasure’s Arbitrum Representative Council (ARC) would like to share the following feedback on the Pilot for a Questbook Jumpstart fund for problem definition and DAO improvement

  • We believe there is clear value in a “Firestarter” style program that gives initiatives and ideas the lift they need to get off the ground.
  • A rigorous understanding of the problem areas should inform the identification of suitable Firestarter topic areas. Otherwise,
    1. Unsuitable initiatives are likely to be funded, OR
    2. There will be an overweighting towards initiatives a specific individual (i.e. the allocator) thinks are important which do no match broader needs within the DAO.
  • The Firestarters are widely regarded as one of PL’s most significant achievements in Milestone 1a, paving the way for the funding of several long-term programs within the DAO, such as STEP.
  • For Milestone 1B, the PL Firestarter initiative has attempted to introduce more rigour and decentralization in the allocation decisions. Nevertheless, due to the lack of a comprehensive process documentation or evaluation on Firestarters in either 1A or 1B, it is difficult to properly assess whether PL has developed a suitable long-term solution for the DAO in this area.
  • We would like to see either:
    1. The final Firestarter frameworks by RDAO and PL published compared side by side, evaluated, and the DAO be able to make a final decision on which framework it wishes to support long-term
    2. Have the efforts of both groups integrated into one single workstream.
  • For this reason, we voted FOR this program, not to indicate firm support for the proposal as written but aligned with our view that funding for “Firestarter” initiatives is clearly needed, and we are open to alternative service providers bidding to play this function.

Please see here for our reasoning on the GCP Council Nominations.

After consideration Treasure’s Arbitrum Representative Council (ARC) would like to share the following feedback on the Incentives Detox Proposal

Name aside, we are very aligned with the contents of the proposal and voted FOR.

:point_up_2:yes please

However, we disliked the framing of this as a detox. Detox implies the recovery from a harmful and damaging substance. Moreover, those recovering on a detox don’t usually dive right back in after cleansing their system. The ARC also noted that the term “incentives” is somewhat ambiguous when we actually are talking about direct user incentives.

These points aside, a structured long-term approach to user incentives is clearly needed, and this proposal moves us a step forward in the right direction.

Vote reasoning for Entropy Advisors: Exclusively Working With Arbitrum DAO

Vote resoning for ArbOS 31 Upgrades “Bianca”

Vote reasoning for Strategic Treasury Management on Arbitrum - #63 by CJ.Bzdewka
Vote reasoning for Team #6: An (EIP-4824 powered) daoURI for the Arbitrum DAO - #32 by Pepperoni_Jo3
Vote reasoning for Proposal to Temporary Extend Delegate Incentive System. - #22 by Pepperoni_Jo3
Vote reasoning for Should the DAO Default to using Shielded Voting for Snapshot Votes? - #37 by Pepperoni_Jo3
Ethereum Protocol Attackathon Sponsorship - #54 by X_0001

Vote reasoning for Delegate to Voter Enfranchisement Pool — Event Horizon

Vote reasoning for Delegate to a public access, public good citizen enfranchisement pool through Event Horizon - #108 by X_0001 MSS Amendment
Vote reasoning for Constitutional - Extend Delay on L2Time Lock - #46 by X_0001
Vote reasoning for STIP-Bridge Operational Budget - #32 by SmolPhil
Vote reasoning for AIP: Funds to bootstrap the first BoLD validator - #45 by X_0001

Treasure DAO concluding Arbitrum Delegate Goverance responsibility

The Treasure community voted recently voted to approve TIP-44: Launching Treasure L2 on ZKsync.

A summary of this proposal can be seen below :point_down:

The proposal from Matter Labs and the accompanying proposal issued jointly by both ZKsync Foundation and the Treasure core contributors revisits the ratified proposal TIP-36: Ecosystem Selection for the Treasure Chain (approved by TreasureDAO on February 21, 2024) to launch the Treasure L2 as the leading gaming chain on ZKsync’s Elastic Chain, instead of on Arbitrum Orbit.

Upon the conclusion of TIP-44, if passed, the ARC will pause its involvement with Arbitrum governance and encourage the community to redelegate their ARB tokens to another qualified delegate.

As a result, Treasure DAO will conclude its participation in Arbitrum Governance and will abstain from voting on any proposals that go live after the passing of TIP-44. While individual ARC members are welcome to continue their engagement, they will do so in a personal capacity. We encourage those who have delegated tokens to reassign their delegation to another active delegate.

Treasure has had an incredible journey with Arbitrum and I, along with the rest of the ARC members, have been honoured to participate in the ecosystem and believe the Arbitrum DAO is on the right track to continue to pioneer, evolve and succeed for long into the future.