PrivCount proof of concept with existing statistics

[teor]

Let's implement a proof-of-concept implementation of PrivCount that adds some noise to existing relay statistics, and then aggregates them.

This proof of concept will help us answer open questions, find bugs and unexpected issues, and get started on the metrics analysis. (But it doesn't need to be secure, because the stats are already public for each relay.)

[teor]

We want to create a local proof of concept with counters set to 0 and 1. Then we want to create a minimal viable product with the relay bandwidth statistic. (If we want to show Guard, Middle, and Exit bandwidth, we'll need to make this statistic a histogram.)

Some of our detailed planning is here:
https://trac.torproject.org/projects/tor/wiki/org/meetings/2018MexicoCity/Notes/PrivCount

[nickm]

Tor 0.3.6.x has been renamed to 0.4.0.x.

[teor]

This can be a parent task

[teor]

These tasks are on the 0.4.1 roadmap for PrivCount and Sponsor V.

[teor]

Let's review these tickets at the next meeting using our 041-proposed process.

They're on the roadmap, so the review should focus on ticket size and team capacity (and sponsor expectations).

[teor]

The points for this ticket are for the remaining sub tasks that we haven't created yet,

[teor]

These PrivCount tickets are on the 041 roadmap, we accepted their points estimates in 041 without discussion.

[teor]

This is a parent task, it has no points.

[teor]

This is a parent ticket, I'm not sure it makes sense for it to have an owner

[nickm]

Move privcount tickets to 0.4.2

[nickm]

Move privcount tickets from 0.4.2 to "Unspecified"; mark as new.