Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C censorship-analysis
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 26
    • Issues 26
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • censorship-analysis
  • Issues
  • #40013
Closed
Open
Created Mar 09, 2021 by Gaba@gaba🦋Owner

Task 4.3 Explore the parameter space in a Salmon reputation design

This step happens after #40012

The question here is to understand better how broad or narrow is the range of workable parameters.

For example, what rates of discovery vs rates of fresh bridges should be workable and what rates should be unworkable?

(If we need more fresh bridges than we can get, that is an unworkable system.)

Edited Jun 03, 2021 by Roger Dingledine
Assignee
Assign to
Time tracking