diff options
Diffstat (limited to 'spec/hspow-spec/v1-equix.md')
| -rw-r--r-- | spec/hspow-spec/v1-equix.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/spec/hspow-spec/v1-equix.md b/spec/hspow-spec/v1-equix.md index 77b7f95..025af48 100644 --- a/spec/hspow-spec/v1-equix.md +++ b/spec/hspow-spec/v1-equix.md @@ -140,8 +140,8 @@ The specific choice of nonce is entirely up to the client, so parallelization ch ## Client sends its proof in an INTRO1 extension {#intro-ext} -Now that the client has an answer to the puzzle it's time to encode it into an INTRODUCE1 cell. -To do so the client adds an extension to the encrypted portion of the INTRODUCE1 cell by using the EXTENSIONS field. The encrypted portion of the INTRODUCE1 cell only gets read by the onion service and is ignored by the introduction point. +Now that the client has an answer to the puzzle it's time to encode it into an INTRODUCE1 message. +To do so the client adds an extension to the encrypted portion of the INTRODUCE1 message by using the EXTENSIONS field. The encrypted portion of the INTRODUCE1 message only gets read by the onion service and is ignored by the introduction point. This extension includes the chosen nonce and effort in full, as well as the actual Equi-X proof. Clients provide only the first 4 bytes of the seed, enough to disambiguate between multiple recent seeds offered by the service. @@ -154,7 +154,7 @@ When a service receives an INTRODUCE1 with the `PROOF_OF_WORK` extension, it sho If it's not enabled, the extension SHOULD BE ignored. If enabled, even if the suggested effort is currently zero, the service follows the procedure detailed in this section. -If the service requires the `PROOF_OF_WORK` extension but received an INTRODUCE1 cell without any embedded proof-of-work, the service SHOULD consider this cell as a zero-effort introduction for the purposes of the [priority queue](./common-protocol.md#intro-queue). +If the service requires the `PROOF_OF_WORK` extension but received an INTRODUCE1 message without any embedded proof-of-work, the service SHOULD consider this message as a zero-effort introduction for the purposes of the [priority queue](./common-protocol.md#intro-queue). To verify the client's proof-of-work the service MUST do the following steps: |