It’s rather disappointing that you miss that the much bigger problem here is that this proposal only goes through because of the vote of people who will financially directly benefit from it. It’s frankly baffling that people seem to be ok with this. For anyone caring about arbitrum, it should be the top concern
1 Like
Thinking quickly, one approach to avoid overburdening the delegates could involve using the LTIPP process, but with faster iterations where advisors can assist in refining proposals and filtering those that met the previous STIP criteria. Then, the council could have a selection phase, similar to the current one but with shorter timelines. In this scenario, protocols wouldn’t need to submit a new proposal; they could use their previous submission and collaborate with advisors on the incentive distribution. The process should be short-lived.
This would be to merge the STIP with the LTIPP and avoid having 2 separate processes.
2 Likes
They voted their proposal in favor 
Maybe good signaling is not tolerated here who knows
2 Likes
First of all thanks to SavvyDAO for the proposal. As ITU blockchain delegation committee we do not support this proposal. The reason for this is simply the same with @tnorm and @pedrob.
The monitoring report of STIP has not been served yet. Also, LTIPP has not started. So this funding method’s success is not proved yet. We also think SavvyDAO failed to adequately defend the proposal since not being responsive enough to previous discussions.
Because of these reasons, we propose an update on this proposal that would also include the other necessary additions based on the outcomes of the previous grant programs in the most optimum way possible. Until then, we are voting against this proposal.
4 Likes
3 Likes
I’m casting my vote against this proposal, expressing concern over the ongoing trend of DAO dependency. It’s crucial for projects within our ecosystem to evolve organically and foster innovation independently. While moderate support is beneficial, the current model raises questions about sustainability and the over-reliance on grants. I encourage all independent delegates to consider the broader implications of such consistent, significant grants on both the ecosystem’s growth and the ARB token’s stability. It’s essential to explore diverse growth strategies beyond grant dependency.
2 Likes
The Princeton Blockchain Club will be abstaining from the STIP-Bridge vote at this time.
We’ve been mulling over this proposal for a while, and are split over the current implementation details.
The L2 environment continues to get more competitive by the day, so we’ve been voting in favor of funding previous grant and incentive programs. Supporting strong Arbitrum-native teams and incentivizing users to use top protocols on the chain is key.
However, we would like to see more analysis of STIP results before the onchain vote. We might be overspending significantly on ineffective uses of ARB, and would like to make informed decisions in the optimistic voting process.
2 Likes
Michigan blockchain voted against the proposal. We thought that the only major difference between this and the LTIPP was that the LTIPP would not be available to those who participated in the original STIP. The LTIPP does what this program intends to do, and it covers what we did poorly in the STIP. It sounds like we are throwing unnecessary money to keep the funded protocols afloat. Large spending isn’t justifiable only as a way to compete with other L2 protocols and move people to ARB.
2 Likes
Seeing that the Snapshot vote is passing with success, we can refine the next steps for the STIP-Bridge.
I believe this is a good idea, and it will allow to reduce the burden for delegates and add clarity to projects.
First thoughts on what I would like to see in the template:
-
Impact of the STIP: most reports I have seen focus on the outcome of the distribution “1000 $ARB distributed to 100 wallets”. We should focus on a second layer: what were the consequences? What
value was created? How much was retained after the incentives ran out? -
Lessons learned: how would you run the program again? What would you change? How can you make it more efficient?
-
Sustainability: will you always need ARB incentives? At what point does your activity become self sustainable
5 Likes
Our delegation voted AGAINST this proposal because, same as others, we’re concerned about how rushed this was and the fact that it feels like taking one step back instead of building on what we could get from the LTIP. Personally, I think that by rushing an incentives program, we risk giving incentives to protocols that might not be used efficiently - this could end up harming innovation throughout the ecosystem, similar to what happens in nations that subsidize certain sectors heavily.
Also, on this:
I simply think it’s always going to be the case - the market is clearly heated and other chains will start launching their tokens; so I don’t think that simply injecting more tokens won’t change this, nor will it really give us much of a competitive advantage vs other ecosystems, since many will be doing the same. What I think we should do is double down on protocols that, through their innovation, will help us compete, and not based on whether they qualified for other incentive rounds.
4 Likes
Thank you for highlighting the pressing need to address the unprecedented competitive pressures facing the Arbitrum ecosystem. The introduction of significant incentive programs by Layer 2 network competitors poses a real threat to our existing protocols.
To maintain our edge, it’s crucial that we leverage operational data to inform targeted funding strategies. Allocating resources where they’re most needed, based on specific user metrics and consumption patterns, will ensure that our projects remain committed to Arbitrum. This proactive approach is essential for sustaining network growth, user engagement, and overall ecosystem stability in such a dynamic market environment.
Moreover, while STIP Bridge is instrumental in retaining these integral projects, it’s essential to emphasize that the true value of Arbitrum isn’t solely reflected in operational metrics or fund allocation. We must also focus on empowering the arb token and enhancing its utility to reinforce the network’s position in the market.
Let’s continue to monitor operational data closely and align funding initiatives with our strategic goals to ensure the continued success of the Arbitrum ecosystem.
UPDATES FOR TALLY PROPOSAL (notes on updates made April 10th):
Feedback from successful Snapshot vote and how it was addressed in the updated proposal.
Concern 1)
We don’t yet have an understanding of which protocols were and were not successful in STIP
Updated Solution
To address this, performance audits have been integrated into the proposal. These audits, conducted by OpenBlock Labs, will provide transparent insights into how effectively protocols utilized their STIP grants.
Concern 2)
The proposed format is too passive and may lead to indiscriminate fund distribution. We need more infrastructure and quality checks.
Updated Solution
We have updated the proposal to include a much more robust infrastructure. First OBL will be providing audits. Second, the advisors from the LTIPP program will be available to work with protocols to improve their incentive mechanisms and determine appropriate amounts of ARB to request from the DAO. Finally, a PM role has been created to help facilitate the program and provide a point of connection between the delegates, advisors, protocol, foundation, and data providers.
Concern 3)
This is the same as STIP we didn’t use what we learned the first time.
Updated solution
This proposal has a few notable differences compared to STIP.
First, this pool of protocols has already been somewhat vetted by the community as they were selected initially. However, they now have had the opportunity to showcase how effectively they can use incentives. The OBL audits along with the data the community will provide will give us more insights into which protocols can successfully use incentives making it easier for delegates to choose which protocols to extend.
Second, STIP was the first time protocols applied for funding and there were strict rules for what they could use the ARB for. This led to many applicants having poor incentive mechanisms as they were unsure how to apply to one of these programs. Now, they will have the opportunity to work with the advisors who helped the LTIPP come up with exciting new incentive ideas. This will help the STIP protocols put forward better applications.
Finally, this program trials optimistic funding. Even with the council in LTIPP, there are still 77 snapshot votes. This is not sustainable for the DAO. This bridge allows us to test an optimistic approach in a more controlled environment to see if it is something we should explore using in the full long-term program
All Updates to the Proposal
- Performance audits have been included to give the community a better understanding of how protocols utilized their STIP grants.
- The advisors from LTIPP will be assisting Bridge protocols to help answer questions and improve their applications
- A program manager has been added.
- A small operational budget has been included to onboard the advisors and pm as well as cover any unforeseen costs such as additional audits. As this budget was not included in the original Bridge Snapshot vote, we will not use any of these funds until an additional snapshot is passed that determines how these funds should be used.
- More clarity has been added regarding the posting of Addendums
- More clarity has been provided on the challenge process and optimistic process
- The timeline has been updated
- The possibility of extension in case of a delay to the full long-term program
4 Likes
Are all applications expected to be submitted in ARB and not in USD?
After careful consideration, I voted FOR this proposal on Tally. The concerns that led me to vote ABSTAIN at the temp check stage have largely been addressed via the addition of STIP performance audits, LTIP advisors, and the program manager role. I’m happy that protocols who qualified for STIP will have the opportunity to qualify for incentives again during this period.
2 Likes
I’ll be voting against this proposal on behalf of the ARB holders who have delegated their voting power to me. After carefully reviewing the proposal and the community feedback provided, I have decided to vote against this proposal at the tally stage. My decision is based on the following key considerations:
Firstly, there appears to be a lack of comprehensive data and analysis on the actual impact and effectiveness of the previous STIP program. Without a thorough evaluation of the outcomes and learnings from the initial STIP, it is difficult to assess whether a similar approach is the best strategy going forward. A deeper analysis is needed to understand the true impact of the STIP program on the ecosystem’s condition, both with and without incentives. This information would be crucial in determining the merits of the proposed approach.
Secondly, the upcoming LTIPP distribution of millions ARB in incentives raises questions about the necessity of this additional proposal. As a community member pointed out, the LTIPP is expected to address the concerns of competing against other L2s and retaining users. Disregarding the rationale behind the LTIPP and focusing solely on the fear of current STIP participants losing their user base may not be the most prudent approach.
Furthermore, the proposal appears to primarily benefit the protocols that previously participated in the STIP program, potentially limiting the inclusivity and overall effectiveness of the incentive strategy. A more inclusive approach that considers the needs and contributions of a broader range of ecosystem participants would be more aligned with the goal of sustainable growth.
Given the lack of comprehensive data on the STIP program’s efficacy, the upcoming LTIPP distribution, and the concerns around the exclusivity of the proposed approach, I cannot support this proposal in its current form. I believe it is essential to prioritize a thorough evaluation of past incentive programs and align the proposed strategies with the broader goals and long-term sustainability of the ecosystem. Until these concerns are adequately addressed, I will be voting against this proposal at the tally stage.
1 Like
I have seen the commitment of the team behind the development of this proposal but also their commitment to generating adequate results for the ecosystem.
Yes, it is true that I agree with my colleagues above and some clarifications on the impact of STIP and direct connection (also based on the learnings from this) with LTIPP would have been ideal but at this crucial stage of the market it is important to continue promoting the protocols that impact directly to the ecosystem.
Now, it is ideal to see results, impact reports and clarity for future possible programs.
I vote FOR on this proposal.
1 Like
As the originators of the proposal, Savvy DAO has voted FOR this proposal.
Our reasoning is clearly stated above in the proposal.
See delegate thread here: Savvy DAO - Delegate Communication Thread - #21 by SavvyDAO
2 Likes
Thanks @SavvyDAO for putting together the proposal and navigating through the discussions and feedback from the delegates.
We vote FOR the proposal on Tally because the proposal has been updated with additional commitments from the LTIPP advisors and promised program manager role as well as the data and audit reports by OBL for us to evaluate the results by the STIP and optimistically approve the additional fundings.
1 Like
I will be maintaining my “Against” vote for reasons notes above
While I am appreciative of some of the feedback being taken into consideration for Tally vote, I do not believe the core issue I have raised was addressed - why should we extend the STIP to run alongside the LTIPP when we can just roll these funds into a more comprehensive 2nd LTIPP round? Because of this my initial concerns still stand. The LTIPP has had some faults to learn from, but I believe it has largely been a step forward from the STIPP round and to just extend those who previously passed a STIP round (yes, I acknowledge subject to Snapshot vote) is a step back.
Two positive ideas I want to take from the proposal however, as I acknowledge there has been a lot of work and thought put into this proposal and there are good take aways here.
- Optimistic voting: I’d be curious to see this in action for a future grant round. While 77 votes is still a lot, the council did reject a lot of applicants. So I think there was some success in that change to the process, but the Optimistic voting method probably would reduce the DAO Delegates voting responsibility even more. As I’d imagine you’d be looking at maybe only a handful of contested votes. In hindsight I think the LTIPP trial round would have been a good opportunity to test this.
- Possibility of Extension: I think something like this is a little more palatable for myself then the current STIP-Bridge proposal. I would be more open to STIP/LTIP extension if there seems to be indication the next grant round is going to happen quickly in order to remain competitive in the space, and if this does end up being the case I would recommend putting forth this same proposal but inclusive to all the STIP / LTIPP rounds.
This Princeton Blockchain Club is voting FOR the STIP-Bridge on Tally.
Admittedly, we’re still iffy on bridge proposal. Our concerns in the Snapshot vote were mostly addressed though. There’s the OpenBlock Labs performance audits, and the PM role now, which hopefully reduces some wasteful grants.
Having a trial for optimistic voting on a grants program is kinda nice. STIP and LTIPP-size votes are pretty grim to get through. Was easier in the LTIPP though due to the council screening / feedback, but was still massively time consuming.