commit 381699215439305d47edb1a9a8db09b561151dea Author: David Goulet dgoulet@torproject.org Date: Fri Jul 1 16:07:40 2016 -0400

prop250: Update SRV construction to reflect the upstream code

Signed-off-by: David Goulet dgoulet@torproject.org --- proposals/250-commit-reveal-consensus.txt | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/proposals/250-commit-reveal-consensus.txt b/proposals/250-commit-reveal-consensus.txt index d386dcb..e88d784 100644 --- a/proposals/250-commit-reveal-consensus.txt +++ b/proposals/250-commit-reveal-consensus.txt @@ -317,7 +317,7 @@ Supersedes: 225

HASHED_REVEALS = H(ID_a | R_a | ID_b | R_b | ..)

- SRV = SHA3-256("shared-random" | INT_1(REVEAL_NUM) | INT_1(VERSION) | + SRV = SHA3-256("shared-random" | INT_8(REVEAL_NUM) | INT_4(VERSION) | HASHED_REVEALS | PREVIOUS_SRV)

where the ID_a value is the identity key fingerprint of authority 'a' and R_a @@ -331,9 +331,6 @@ Supersedes: 225 To maintain consistent ordering in HASHED_REVEALS, all the ID_a | R_a pairs are ordered based on the R_a value in ascending order.

- Because the number of reveals (REVEAL_NUM) is using a 1 byte value, it - imposes a hard limit of 255 authorities participating in the protocol. - 3.4. Bootstrapping Procedure

As described in [CONS], two shared random values are required for the HSDir