diff options
Diffstat (limited to 'spec/hspow-spec/v1-equix.md')
| -rw-r--r-- | spec/hspow-spec/v1-equix.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/spec/hspow-spec/v1-equix.md b/spec/hspow-spec/v1-equix.md index 025af48..f49086a 100644 --- a/spec/hspow-spec/v1-equix.md +++ b/spec/hspow-spec/v1-equix.md @@ -1,4 +1,4 @@ -# Onion service proof-of-work: Version 1, Equi-X and Blake2b +# Onion service proof-of-work: Scheme v1, Equi-X and Blake2b ## Implementations {#implementations} @@ -82,7 +82,7 @@ Thus the effort is communicated explicitly in our protocol, and it forms part of ## Parameter descriptor {#parameter-descriptor} This whole protocol starts with the service encoding its parameters in a `pow-params` line within the 'encrypted' (inner) part of the v3 descriptor. The [second layer plaintext format](../rend-spec/hsdesc-encrypt.md#second-layer-plaintext) describes it canonically. The parameters offered are: -- `type`, always `v1` for the algorithm described here +- `scheme`, always `v1` for the algorithm described here - `seed-b64`, a periodically updated 32-byte random seed, base64 encoded - `suggested-effort`, the latest output from the [service-side effort controller](./common-protocol.md#service-effort) - `expiration-time`, a timestamp when we plan to replace the seed. |