Cardano GovTool Budget - 12 months full active maintenance and development
13 SPOs voted · 2 with a rationale · 2 re-voted unchanged
Open a row to read the rationale.
- YesNo rationale
- YesRevotedHistory
Earlier votes
Yes1y agoSuperseded
- YesRationale
Although SPO votes are not considered for budget info actions, the ledger nonetheless allows SPOs to vote on all info actions. This vote is submitted to the chain in order to maintain the pool voting record. For detailed DRep rationales regarding the associated proposals see transaction hash: ffe6487f7472f80ce86dad43a3ab13081d129e32acb222d81fc5b2fcba712310.
- NoNo rationale
- NoNo rationale
- NoNo rationale
- YesRevotedHistory
Earlier votes
Yes1y agoSuperseded
- YesNo rationale
- YesNo rationale
- YesNo rationale
- NoRationale
As a developer and DevOps specialist, I believe the requested amount is significantly overestimated and does not reflect the actual needs of a project of this type.
I also run an independent node and indexer. The Medusa cluster consists of 5 servers: one server running cardano-db-sync with 12 cores and 64 GB of RAM; three servers running cardano-node, providing redundancy and data to the db-sync, each with 8 cores and 24 GB of RAM; and a frontend server with 4 cores and 4 GB of RAM. Each server is connected to a reliable 2 Gbps channel.
The cluster operates stably and without interruption, serving around 600 unique users per day on average, with peaks reaching 1,000 at epoch boundaries. While that may not sound like a lot, wallet synchronization happens continuously, and in reality, the cluster processes tens or even hundreds of thousands of requests daily — even when users take no active actions after logging in.
I pay around $100 per month in total for this infrastructure.
You are requesting approximately $27,500 per month for infrastructure and maintenance(I’m not even considering the other items or amounts — only this one), based on the current exchange rate.
Even if all 948 DReps registered in the Cardano network — and we both know that’s objectively impossible — accessed your service and voted, it wouldn’t produce even 1% of the load my cluster handles. That’s assuming they all logged in and voted on the same day, which is also highly unrealistic. Voting events are infrequent and spread over time. Yes, nodes and db-sync do operate between voting periods as well — but so do mine, even when nobody is accessing them. Three nodes and one db-sync — all for $100 per month.
So my answer is “NO.”
- YesNo rationale
- YesNo rationale