Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #4826

Closed (moved)
Open
Created Jan 05, 2012 by Roger Dingledine@arma

Write proposal for improved consensus voting schedules

Sebastian suggests that we revise the schedule for consensus voting such that there's a cutoff after which we discard votes from the original authority. So phase 1a is to publish your vote to every authority, phase 1b is to ask every authority for votes you're missing, and during phase 1b we won't accept phase 1a votes.

The goal here is to avoid consensus failures that occur when an authority uploads a vote during phase 1b, and some authorities end up thinking everybody knows it, yet some don't know it.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None