Three essential objectives: open-sourcing all components of the PoolTool platform, eliminating ads ,and funding operations for a year.
Much of the technology we have developed would be useful to other developers in the ecosystem. And making it open source the community can build features on top of pooltool more easily
This is the total amount allocated to Open source PoolTool.io and sustain for 1 year
The pooltool platform includes the following innovative tools:
Our unique approach to many of these challenges will provide a useful template for others. In addition it will allow a broader set of the community to contribute and extend the capabilities of pooltool.
The challenge is to support effective and impactful projects and initiatives to build and support the SPO Ecosystem and Community. PoolTool has already been instrumental in this providing a centralized GUI for pool operators to monitor pool performance and status. However opening up the source code will provide examples and more importantly a framework for others to contribute their ideas to expand on our rich user interface
As we embark on open source perhaps one of the best metrics will be the number of forks of the pooltool assets. I'm confident that our live stake processing and reward processing along with the memoryless ledger state processing are highly coveted by many in the community and will see immediate uptake. ,
But an even more exciting opportunity is around expansion of the metrics we collect as part of the block submissions. We have already tossed around ideas to collect more extensive information.
Within one month of approval we will move everything to a public repository and invite developers to view and contribute to the platform. The month will be used to add a reasonable level of documentation to the platform to make it easier to understand and replicate.
We own all this technology and it has been developed over the years. Aside from some cleanup required to document aspect of what we have done, the code is ready to deploy.
Running and maintining the infrastructure for a year is what we have been doing so far. Mike has been handling all the website requirements and Leon has been handling the pooltool app project for both android and IOS. Both resources are avaliable to continue to work on this project.
The goal is to give the project back to the community and as mentioned above I will consider this to be a success if we start to see other projects using our technology or building on the pooltool platform.
We will be looking for 50+ forks of the pooltool github repository.
For the sustaining aspect of this proposal we would probably need to have an SLA to measure our uptime. Thus far we have not put that type of infrastructure in place. Pooltool uptime (meaning on tip) has been excellent over the last two years and I don't expect anything to change there once its sustained by the community. However, if necessary we could commit to an SLA of 95% uptime. (meaning on tip within 10 blocks of the tip (normally we target 6))
All code will be transferred to public repositories within 1 month of project approval by Catalyst
Platform will continue to be operational on mainnet for one year after catalyst funds approved.
Due to the ongoing sustaining nature of the project its probably easiest to split each month into a separate milesone.
Milestone 1: Month 1 - code release and first month of sustaining
Milestone 2: Month 2 - 2nd month of sustaining
Milestone 3: Month 3 - 3rd month of sustaining
Milestone 4: Month 4 - 4th month of sustaining
Milestone 5: Month 5 - 5th month of sustaining
Milestone 6: Month 6 - 6th month of sustaining
Milestone 7: Month 7 - 7th month of sustaining
Milestone 8: Month 8 - 8th month of sustaining
Milestone 9: Month 9 - 9th month of sustaining
Milestone 10: Month 10 - 10th month of sustaining
Milestone 11: Month 11 - 11th month of sustaining
Milestone 12: Month 12 - 12th month of sustaining
Milestone 1: All pooltool source code will be released to a public repository on github. deliverables are outlined above.. In addition, Pooltool will continue to be operational
Milestone 2 through Milesone 12: Pooltool will continue to be operational and maintained on the latest node release.
Our labor rates are normally $150 per hour for engineering labor, but for PoolTool we will reduce this to $100 per hour in the hopes that ADA appreciates and/or because we value the community and this project.
Sustaining PoolTool consists of three aspects.
1) firebase storage and delivery - Currently $350 per month, targeting $250 per month
2) AWS EC2, API, Dynamo DB, Lambdas - Currently $850 per month, expecting $750 per month
3) Ongoing node upgrades and maintenance and support - 5 hours per month
We already have some active effort in place to cost reduce the platform as outlined. This will be completed well before Fund 10 finishes. I'm not listing this as a dependency because if we are unable to reduce the monthly costs to $1000 for servers we will cover the difference.
With the current ADA exchange rates this works out to 3333 ADA per month for servers and 1666 ADA per month for maintenance labor. For a total of 5000 ADA per month. This work will primarily be handled by Mike but the apps require a little effort occasionally as well so I'd expect Leon to be involved. 5000 * 12 = 60000 ADA
We have also allocated 1 month to push the repository to open source. We could do this without any effort but there is some documentation and cleanup we should to to make it easier for others to build and extend our codebase. We have allocated 45 hours to do this work between Mike and Leon. At an rate of just over 333 ADA /Hour this works out to 15,000 ADA.
Given the years of contributions to the community and the tools developed, 75,000 ADA to both fund the platform for a year and get it ready for open source should prove highly beneficial to the community.
I'd estimate that the reward processing alone represents 2 months of effort for an engineer over the years when you consider the reverse engineering of the haskell code, and the methodologies to extract the necessary parameters from the node (note, not all information is avaliable in db-sync to perform these calculations)
On the ongoing server costs I could probably break down some additional detail:
With the fund denominated in ADA there is risk associated with exchange rates since our server costs will be USD denominated.
Mike - PoolTool website and backend(python) and infrastructure development. Mike will handle basically everything except the pooltool ios apps.
Leon - The pooltool app has been maintained by Leon for the last year and I'd expect some documentation to be completed as part of this and a little maintenance of the apps over the next year.