Please describe your proposed solution.
This proposal aims to create a community of maintainers around an open source “SPO Spotter” solution to provide suggestions of Stake Pools to delegate to in different interchangeable ways.
The SPOtter approach is to break down the process of ranking Stake Pools according to your priorities. This process is composed of:
- Indexing the blockchain, obtaining all the SPO-relevant data particles (illustration 1) into a standard ‘SPOtter format’.
- From that data facilitate that the community develops different algorithms to process it according to different priorities.
- Provide an intuitive user interface to visualize and tweak the resulting SPO ranking/suggestions.
- Delegate to the SPOs directly from our platform.
- Share your views with friends and collegues.
Some possible examples of algorithm priorities are:
- To (randomly) prioritize Single Pool Operators
- To help pools that have been on the verge of minting blocks
- Simply to try to maximize your staking rewards.
SPOtter leaves the responsibility of that decision to the user.
Because algorithms are open-source, anyone can tweak them and generate variant algorithms, but the best of these are expected to accumulate more statistics of being used, making them more trusted. Also some algorithms may have a review by some reputable organizations, confirming what priorities the algorithm is enforcing.
Beyond providing this tool in our own web app, we can build towards providing it as a consumable service that can be consumed from any Cardano wallet. We can then build partnerships with wallets, SPO communities, and other entities.
Illustration 1 - SPO-relevant data particles (as currently viewed in wallets and block explorers:
How does your proposed solution address the challenge and what benefits will this bring to the Cardano ecosystem?
The current proposal will “make it easier for SPO Projects and developers to build on top of Cardano” in the sense that it will make it easier for SPOs to be sustainable.
It also may fall into ”Academic research and analytics on topics related to SPOs or SPO tooling
Developing SPO Standards”
How do you intend to measure the success of your project?
For the application side:
- Contributors to the open-source repository
- GitHub activity (Merges, Pull Requests, Issues solved)
- Features built and suggested
From the community side:
- Active Members in open discussion and collaboration
- Engagement and feedback on social media
Please describe your plans to share the outputs and results of your project?
45B will use it’s social media, blog and other media to promote:
- The call to action for the community to come build this solution
- Formal specifications as they mature
- The running solution, to make it available for use