Small Toolchain dev
2 years ago
Executed
Hi to the whole Kusama & Polkadot community,
I would like to ask your support to aid operation and dev cost for a small toolchain that I'm building ( https://prostakers.com/tools ) for the next 1 year that includes:
- https://prostakers.com/1kv-kusama - 1kv current & next nominations
- https://prostakers.com/dashboard-kusama - 1kv dashboard
- https://prostakers.com/calc - planck calculator
- Development of 4th micro-service to periodically reach 1kv nodes (through standard polkadot service port) and report any communication issues via the originally declared 1kv email of the interested 1kv operator.
(est. delivery 1 month)(delivered on 2023/07/12)
Whoever finds it useful can vote for this proposal, also any requests and ideas are welcomed!
UPDATE 2023/07/12 : The 4th service implementation was completed, url: https://prostakers.com/monitor
Comments (5)
Requested
19.00K DOT
Proposal Passed
Summary
0%
Aye
0%
Nay
Aye (115)0.0 DOT
Support0.0 DOT
Nay (144)0.0 DOT
Hi there,
I appreciate the work you are doing with your toolchain and in general, I am always in support of similar projects. However, I'll be voting Nay on this proposal for a few reasons:
One Year Request: It's a large commitment to fund a project for a whole year, especially as a first-time proposal. I suggest starting with a shorter time frame.
Proposal Details: It is unclear how much work this involves and what the specific goals of the project are. Also, the amount of funding you are requesting isnt showing specific work rates or tasks.
Project Deliverables: It's hard to understand what the final product will be. Is it meant to be a nicer UI only?
Full dependence on 1kv frontend: Your project seems fully reliant on the 1kv frontend and it reads all the data from there. This full reliance on a single data source can be problematic, as demonstrated by the current situation where both the 1kv frontend and your Polkadot page seem to be unresponsive. This suggests that your tool serves only as an additional UI for the 1kv frontend.
I believe refining your proposal with more details and a clearer scope can influence my voting decision.
Best of luck!
@coinstudio
Hi thanks for your valuable comments, I fully understand your considerations, a few specific statements are the following:
The crawlers & UI run quite a few months now and I am planning to continue their operation for the next year as part of the website. Unfortunately I can not edit spending plan with this referendum.
I completely agree with this comment, although as most of the coding was already done I naively avoided these calculations and kept the budget low.
The first two urls are a nicer UI for the 1kv backend, and I was planning to populate them with a few more parameters.
Yes that is correct, a way to tackle this is to re-calculate several of the parameters using on-chain data, but I'm not sure if this is of any value as the nominations are made using only the 1kv backend collected data.
In addition with the improvements of the current UI's. I was planning the development of a 4th micro-service to periodically reach 1kv nodes (through standard polkadot service port) and report any communication issues via the originally declared 1kv email of the interested 1kv operator. I've now reflected these to the proposal description.
Thanks for taking the time to review this proposal!
Not sure how active you have been in 1KV so nay for today. I will review this and vote in harmony with Paradox.
@a9e3c96fb0a14945997ab872e
Of course, thanks for your comment.