CPS-0025? | Small pool disadvantage in VRF tiebreakers#1130
CPS-0025? | Small pool disadvantage in VRF tiebreakers#1130Cerkoryn wants to merge 5 commits intocardano-foundation:masterfrom
Conversation
rphair
left a comment
There was a problem hiding this comment.
thanks @Cerkoryn - very well formulated & written in my opinion; on agenda for introduction at next CIP meeting: https://hackmd.io/@cip-editors/126
| ## References | ||
|
|
||
| - https://github.com/IntersectMBO/ouroboros-consensus/pull/1548 | ||
| - https://hackmd.io/hX7q5s8JSKSP-j3525J0bA (Alexander Esgen) |
There was a problem hiding this comment.
HackMD allows authors & owners to set a URL "stub" as an alias in addition to the randomly generated default (e.g. how we generate the concise CIP meeting agenda links here: https://hackmd.io/@cip-editors) with the Share button when editing a page.
So @Cerkoryn if you're in a position to suggest this to the author (cc @amesgen) it may be possible to choose a more familiar name before that link circulates more widely through this CIP candidate (YMMV since it might also show the account name in a custom link, etc.).
Co-authored-by: Robert Phair <rphair@cosd.com>
Co-authored-by: Ryan <ryan.williams@intersectmbo.org>
|
With the amount of previous discussion on this issue, happy to see this formally become a CPS. |
rphair
left a comment
There was a problem hiding this comment.
Ditto on #1130 (comment) & please @Cerkoryn update the containing directory to CPS-0025 accordingly 🎉
rphair
left a comment
There was a problem hiding this comment.
(p.s. to #1130 (review))
This CPS is the result of this unintentional original design bug that used the "L" hash to settle ties, which gave a slight advantage to smaller pools. After the Vasil hard fork, the network switched to using the "B" hash instead, which removed that advantage and led to some consternation amongst many smaller pool operators.
To address this, a PR was submitted that attempted to revert the change here with the primary objective of trying to stimulate the discussion amongst the relevant parties. At the time it was unsure what the correct path should have been because the change from the L->B hash was not a CIP or a governance action, but a bugfix that might have flown under the radar of many of the SPOs it affected.
After discussion with @dcoutts it was decided that the proper path forward would be to write a CPS to properly define the problem first, since a technical solution to this would be more complex than simply reverting back from B->L hash, as the protocol was not intended to use the L hash for tiebreakers.
This CPS is the result of those discussions. My hope is that it will stimulate some ideas for a future CIP that can hopefully allow us to solve the problem in a more permanent way.
(Rendered)