Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #7148

Closed (moved)
(moved)
Open
Created Oct 19, 2012 by Nick Mathewson@nickm🍬

Even better parameter voting protocol

Our current parameter voting protocol is backwards in how many voters need to exist for a parameter before we can vote for it. Right now we accept the parameter into the consensus if it has a majority of all authorities, or at least 3 authorities. But that fails when most authorities are abstaining: 3 rogue authorities could force the value of an unset parameter to whatever they want.

A stopgap solution (for which roger is writing a ticket) is for all authorities to vote on all parameters, and to have most/all authorities begin voting on any new parameter before we release software that looks for it.

But surely we can do better than that.

We need to write a little proposal for this before the little-proposal deadline to implement it in 0.2.4.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking