SPO

Medusa Development Support

pool1vc8j...0uhpech9
https://adawallet.io

This pool allows us to sustain and improve our free services and provide you with the best user experience. Our pool has high uptime, good ROI and equipped with low-latency auto-recovering system.

Badges (2)

Pool Voice
Silver
Hard Fork Ready

Forum activity (0)

No forum posts yet.

Governance record

Participation29%Voted on 12 of 42 concluded actions
Votes with rationale42%5 of 12 votes with rationale
Voting pattern
12votes
  • Yes4 (33%)
  • No7 (58%)
  • Abstain1 (8%)

No vote changes

Voting history (12)

YesHard Fork to Protocol Version 11 ('van Rossem' Hard Fork)Decided epoch 644No rationale publishedEnacted2mo ago
YesReforming Treasury GovernanceDecided epoch 643No rationale publishedClosed2mo ago
NoCardano Budget Process Framework (facilitated by Intersect)Decided epoch 623View rationaleClosed6mo ago

No, no, no - once again, no. Monopolizing the budget is a terrible idea. It was a bad idea last time, and it is a bad idea now. No. We know where this leads - 90% of the funds will go to 9,000 promises from IOG (with a very low completion rate), and the remaining 10% will go to “Raid the Treasury”-style proposals, which are largely useless for the network. No.

NoNet Change Limit of 300 Million ADA for Epochs 613–713Decided epoch 618No rationale publishedClosed6mo ago
NoCardano GovTool Budget - 12 months full active maintenance and developmentDecided epoch 574View rationaleClosed1y ago

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.”

Show 7 moreShow less
NoTempo for Cardono Governance - Maintenance & Development Budget for 2025Decided epoch 576View rationaleClosed1y ago

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 $20,000 per month for infrastructure, 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.”

No2025 Net Change LimitDecided epoch 554revotedHistoryNo rationale publishedClosed1y ago

Earlier votes

No1y agoSuperseded

NoSet 2025 Net Change Limit of 300M ADA, 2026 Net Change Limit of 250M ADADecided epoch 553View rationaleClosed1y ago

Please provide some research and math proving that it is necessary, effective, and healthy for the network and users.

AbstainDefining the Cardano Vision and Roadmap for 2025 and beyondDecided epoch 549View rationaleClosed1y ago

We can't vote for the URL because its content may change at any time in the future, but our votes cannot.

YesHard Fork to Protocol Version 10 ("Plomin" Hard Fork)Decided epoch 537No rationale publishedEnacted1y ago
YesShould K increased?Decided epoch 521No rationale publishedClosed1y ago
No15f82a365bdee483a4b03873a40d3829cc88c048ff3703e11bd01dd9e035c916#0Decided epoch 514No rationale publishedClosed1y ago