Want to gauge sentiment before a formal proposal, and will probably use this as the template for the actual proposal down the road.
I think the 5K $RADAR minimum for Dappradar Pro is very low. With the current price at around $0.012 it is worth ~$60. At the ath price around $0.05, it’ll be worth around $250. Some dex analytics tools with the similar hold-for-premium-services structure require holding amounts worth more than this.
Dappradar already provides a very unique service without any alternative competition. Dappradar Pro has various current and planned perks for users, and also provides the Pro Support service extremely beneficial to project teams themselves.
So I believe the minimum $RADAR holding requirement should be increased drastically to an amount that would accurately reflect the current and near-future value of the Pro services. This would generally serve two purposes: (1) increase token value by requiring more $Radar to be held by Dappradar users and therefore decreasing the practically available supply in circulation; and (2) encourage more contribution and governance participation by requiring users to have more at stake financially.
Although this can be done in various ways, below are two suggestions that can be implemented separately or in combination.
- Increase the minimum requirement universally for all Dappradar Pro services. (could be 10K, 20K, 50K etc.). This could revisited and adjusted by the community periodically (e.g. monthly) to keep it reasonable. Some benefits of this approach would be:
- more $Radar being held by users of the protocol so, not really but practically, more is removed from circulation;
- users being more invested in the health and development of the Dappradar Ecosystem; and
- further encouragement into participation in Dappradar Governance.
- Set a different minimum requirement for Pro Support specifically for listing-related help. Project teams are more likely to need prioritized assistance with listings, whether it is updating the information displayed or submitting the correct contracts. Project teams are also financially more capable than the average user. So for listing-related Pro Support, the minimum could be a realistically higher number (100K, 1M, 5M etc.). Pro Users would still get Pro Support for everything else. And the contribute-to-earn spirit is protected since all users would still get listing-related support, just would not be prioritized to the same extent which they usually don’t need anyway. The benefits would be similar, but maybe on a different scale:
- More $Radar held;
- Project teams themselves having a stake in the heath and development of the Dappradar Ecosystem; and
- Project teams being encouraged to participate in Dappradar Governance; and
- In the likely event that $Radar price increases a lot, and it becomes expensive to get this service, those projects who showed support for the Dappradar Ecosystem early on will have been fairly rewarded by not having to pay that high cost.