Opened 7 months ago

Last modified 3 months ago

## #29266 new defect

# PrivCount proof of concept: round results to hide usage over time

Reported by: | teor | Owned by: | |
---|---|---|---|

Priority: | Medium | Milestone: | Tor: 0.4.2.x-final |

Component: | Core Tor/Tor | Version: | |

Severity: | Normal | Keywords: | privcount, 040-unreached-20190109, 041-accepted-20190115 |

Cc: | amj703 | Actual Points: | |

Parent ID: | #27908 | Points: | 1 |

Reviewer: | Sponsor: |

### Description

We need to round the results to hide usage over time. We should work out how much to round each result, and how to implement the rounding.

Here is one possible scheme:

- we want to round the result to the closest multiple of N
- each tally reporter rounds their blinded subtotal to the closest multiple of N
- the final un-blinded result is rounded to the nearest multiple of N (plus an arbitrary value between 0 and N, due to the unblinding), as long as at least one Tally Reporter is honest

## Child Tickets

### Change History (5)

### comment:1 Changed 7 months ago by

Points: | → 1 |
---|

### comment:2 Changed 7 months ago by

Sponsor: | → SponsorV |
---|

### comment:3 Changed 3 months ago by

Milestone: | Tor: 0.4.1.x-final → Tor: 0.4.2.x-final |
---|

### comment:4 Changed 3 months ago by

Removing sponsor V as we do not have more time to include this tickets in the sponsor.

### comment:5 Changed 3 months ago by

Sponsor: | SponsorV |
---|

Removing sponsor from tickets that we do not have time to fit in the remain of this sponsorship.

**Note:**See TracTickets for help on using tickets.

Move privcount tickets to 0.4.2