Also voted Yes.
Thanks for raising this here @anon10525910.
Also voted Yes.
Thanks for raising this here @anon10525910.
the short answer is no I manually calculate 5% of circulating supply and track progress for each vote. IIP-49
did surpass quorum.
Fwiw, there is a card in Engineeringâs Trello board related to making quorum/progress against it more visible.
It is not in the current sprint, though I am noticing that the # of requests for this visibility is increasing
The narrative around eng and developer resourcing is that everyone at Set Labs is basically full time on Index Coop. I have heard this countless times over the last few months.
When the community has sought further insight into who is working on what and how long these tasks are expected to take - Set Labs has failed to provide any meaningful insight. The community flagged concerns around poor communication in the past with Set Labs working on the FLI product months before sharing this with Index Coopâs community.
Fast forward to now, Index Coop has not been able to bring products to market quickly and Set Labs has been flagging engineering/developer workload as a concern. What is abundantly clear, is engineering work scopes flow through a Set Labs process which determines what gets prioritised.
The recent launch of TokenSets on Polygon is a clear example of Set Labs with holding information from the Index Coop community. To me this is a clear signal to the market that Set Labs is trying to kick start the individual trading platform initiative that failed to gain traction on L1. What this does is creates additional engineering/developer drain on the same few resources. Looking past the resource constraints, this is not very honest or transparent behaviour on Set Labs behalf given Index Coop products have been largely on pause and now BEDs listing coincides with post Polygon Launch
Further to the above @setoshi frames Index Coop as a Customer. Not a partner, not a 28% owned subsidiary but as a Customer. If Set Labs was a contractor, then we would should have a contract in place with T&Cs - that is how traditional business conduct operations.
I am also concerned that this framing implies Set Labs will monetise the relationship with Index Coop. After-all, contractors are paid for a service and replaced when performance is suboptimal or expensive. This is the nature of customer / client relationship. A partnership is different, but Index Coop is the same as Ember Fund in this context.
Whilst on the broad topic of trust, appears Set Labs is selecting its words carefully and mis portraying the truth to no only Index Coop but to other major partners.
I would like to believe Set Labs but in light of the above concerns, I am finding it increasingly challenging to do so.
Conversations with Set show that this was not intentional. While it did affect ICâs Polygon rollout we are working to establish the appropriate channels to ensure that such miscommunications do not happen again. Set has been a great partner and look forward to continuing to work with them and expand ICâs suite to Polygon.
I understand that tensions are currently high throughout our community on a few key issues.
Specifically:
These conversations involve every major stakeholder in the Coop ( including us, DeFi Pulse, and Set Labs). Our current incentive structure and tokenomics clearly need work in order to fully align incentives across the community. I big factor in this frustration from the community is the reality that the core contributors (including FT and WG leaders and all Gold Owls) collectively own <2% of the protocol even when accounting for FT vesting contracts. For example, total protocol ownership for all FT contributors combined equals 0.6% over two years of work.
I highlight the above to illustrate that there are very real issues and frustrations shared across all parties, myself included. My loyalty does not lie with SET Labs or DFP. I did not walk away from a normal life for either party, I walked away because I love our community and community members. Seeing our protocol thrive, and our community succeed has been the proudest thing I have ever been part of.
We as a community are ready and capable of having these conversations without attacking our dragging stakeholders through the mud. Everyone including SET and DFP is giving their heart and soul to this project. That is a basic reality. SET Labs doesnât need to front-run or monetize their relationship with Index Coop, they have a big enough stake that the further success of our protocol will generate far more revenue for them long-term than by charging us some future fee. To suggest that they have some nefarious plan is quite frankly ridiculous.
BD specifically asked for BED to be pushed back so that it would not launch on the same day as Sushiswapsâ Trident announcement. While the roll out of Tokensets on Polygon came as a surprise, that clearly was not meant to frontrun the Polygon rollouts that @oneski22 has been working so hard on for the past few months.
We can pick can snipe at any of the three legs of our collective tripod as much as as we want - but I promise you this will get us no-where. I am all for having frank and public discussions around the future of our protocol, but we need to have these discussions from a position of mutual respect and trust.
Here are a few actions that are completely unacceptable when having these conversations and we need to stop doing as a community.
Insulting other community members or working groups. We cannot have positive forward conversations if we are constantly sniping each other. If anyone wants to do that - they are more than welcome to go and join one of the million toxic chat rooms that exist across the internet.
Negotiating based on threats. I understand that emotions often run high and people can feel that their perspective is not being heard. But if every time we encounter some issue or friction people run around yelling that they âare about to leave the communityâ it becomes very difficult to have any kind of conversation.
Adopting an us-vs-them mentality. If we start this kind of thinking our cohesive team will quickly degrade into progressively smaller groups fighting increasingly more petty battles. Losing happens when we devolve into a zero-sum organization with community members fighting community members, WG fighting WGs, and stakeholders fighting stakeholders. If we donât figure out a way for SET - DFP - INDEX to work together and collaborate, we wont get anywhere.
Attacking other community members. If you would not say it to that community members face, donât F****** say it. This may be the hardest rule of all and no-one is perfect. But we canât establish the trust needed to succeed as a protocol if we canât trust each other.
Over the past few months I have had rewarding conversations with @setoshi @asoong and @scott_lew_is @Etienne. After each conversation, I come away absolutely blown away by their respective levels of knowledge and passion for DeFi. But my biggest takeaway from all four is their level of passion for Index Coop. All major stakeholders share a common belief that we are building something truly incredible with Index Coop and want to see it succeed. This shared belief in the strength of the protocol and what we have accomplished so far is a common foundation that we all need to rally around.
Couldnât have said it better myself.
This one hits home. This has been the approach a few folks chose to take recently. Itâs counter productive, it damages everyoneâs morale, takes focus away from key priorities and itâs not going to get you what you want. What kind of leader or partner negotiates based on threats? We are all here for the same reason - make DeFi products accessible to anyone and build the next BlackRock. Letâs not lose sight of that.
Do want to acknowledge this criticism and we need to have the Set Engineering <> IC communication be better understood.
Would also like to highlight that the Coop has the funds and capacity to hire an engineering team. Itâs a question of doing the work. Part of this conversation needs to be community members very clearly understanding that they have the agency fix these problems.
Calling out that this is being prioritized by the EWG. That proposal is worth a read.