Should K increased?
134 DReps voted · 21 with a rationale · 3 changed their vote
Open a row to read the rationale.
Changed votes: 1 to yes, 2 to no, together voting with 1.1M ₳ of voting power.
- No275.2K ₳No rationale
- Abstain263.3K ₳No rationale
- No252.7K ₳No rationale
- Yes236.8K ₳No rationale
- No236.8K ₳Rationale
See https://luminapool.io/drep for my reasoning behind this vote.
- Abstain189.8K ₳No rationale
- Yes185K ₳No rationale
- Yes171.6K ₳No rationale
- Yes166.5K ₳No rationale
- No161K ₳No rationale
- Yes151.8K ₳No rationale
- Yes150.4K ₳No rationale
- Yes136.8K ₳No rationale
- Yes127K ₳No rationale
- Yes126.4K ₳No rationale
- Abstain112.3K ₳No rationale
- No108.3K ₳No rationale
- Yes99K ₳No rationale
- Yes93.7K ₳No rationale
- No74.5K ₳Rationale
The proposal is merely suggestive of whether or not to proceed, lacking real clarity. The evidence provided is unconvincing and appears promotional. If possible, please provide more compelling evidence and reasoning for future proposals.
- No56.4K ₳No rationale
- No56.1K ₳Rationale
Raising k damages the stability of the ecosystem in many ways, but the primary reason is operational resilience of block producing nodes. With a larger k, the profitability of running a pool goes down, as the total epoch rewards remain the same, but are distributed to a larger set of block producers. At the same time, running a node doesnt get cheaper, meaning the majority of pools have even tighter margins than they already have, leading to a decrease in quality of node setups (cheaper).
- Yes40.6K ₳No rationale
- Yes26.7K ₳No rationale
- Yes20.7K ₳No rationale
- Yes14.8K ₳No rationale
- Yes13.6K ₳No rationale
- Abstain10.9K ₳No rationale
- No9.2K ₳No rationale
- No6.8K ₳No rationale
- Yes3.4K ₳No rationale
- Yes1.1K ₳No rationale
- Abstain0 ₳No rationale
- Abstain0 ₳No rationale