We are AstarHood, an anonymous voice within the ecosystem, inspired by the legendary Robin Hood. Our mission is to ensure that Astar’s dApp Staking system remains a powerful tool for fostering innovation and growth, reserved for projects that bring true value to the ASTR token and the broader ecosystem.
Proposed Action
Based on our research, we have identified several projects that we believe are underperforming or inactive within the dApp Staking system. We would like to open this discussion with the community to gather opinions on whether these projects should be delisted and whether this process can be implemented via a batch call for efficiency.
Based on our previous actions we found out that delisting is happening at a very low pace because of discussion, voting, etc… while if community approved, I would like to create a batch call with maybe 2 projects at ones?
Projects Under Review for Delisting
The following projects have been flagged as potentially not meeting the current standards for active and valuable participation in the Astar ecosystem:
InsureDAO
Grabber
XO
…
Call to Action
We invite the community to share their thoughts on the following:
Should delisting be implemented via a batch call for efficiency?
Are there any additional projects or criteria we should consider?
Your feedback is crucial to ensuring that this initiative reflects the shared values of our ecosystem. Together, we can build a stronger, more resilient Astar Network.
I believe a batch delisting would save time and be efficient… however, just as the listing process went through a voting phase, I think it would be democratic for delisting to follow the same approach, giving teams the opportunity to justify or explain to the community why they didn’t meet the expected metrics.
I know it will be more labor-intensive, but I believe it’s the fair approach—walk the talk, always.
In the future, we can establish a batch delisting model, but I think it’s important to set clear parameters for this to happen.
I agree with @pitcoin777 . I understand very well the desire to delist all together for efficiency, but it seems to me that it would be better to have a similar process for listing and delisting.
However, since resources are finite, we may be able to batch them together if the projects are in similar situations, for example. Whatever it is, I think we should avoid making it sloppy for each project by batching them together.
Note that I cannot make a decision about the batch call for delist, so I will defer to the developer.
I agree with the others, I think it makes more sense to delist one project at a time, also giving each team time to respond (even if it almost never happens). If the delisting proposal includes more projects, I think following the comments will become more complicated.
Hi, @AstarHood, thank you for your hard work of research and your enthusiasm for keeping the ecosystem clean and healthy.
Personally I have seen little or no activity of these protocols which you have under review, however the above mentioned by @pitcoin777 makes all possible sense.
I would like to see a more efficient way where we could see the returns of the projects.
I can confirm that batch delisting is possible and can be executed by the community council to make the process faster.
However, I still encourage to have separated discussions on each project and doing polls using the discussion section on Subsquare to get the opinion of the community before executing those delisting.