github/consensus-specs
1
1
Fork 0
mirror of https://github.com/ethereum/consensus-specs.git synced 2026-02-02 07:24:56 -05:00
Code Issues Packages Projects Releases Wiki Activity

use raw SHA256 as message-id

Browse Source
This commit is contained in:
blacktemplar
2020-09-09 15:02:47 +02:00
parent 88cdc5bc80
commit 9cbc7c37f4
1 changed files with 1 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
specs/phase0/p2p-interface.md
View File

@@ -246,9 +246,8 @@ Likewise, clients MUST NOT emit or propagate messages larger than this limit.
The `message-id` of a gossipsub message MUST be:
```python
message-id: base64(SHA256(message.data))
message-id: SHA256(message.data).
```
where `base64` is the [URL-safe base64 alphabet](https://tools.ietf.org/html/rfc4648#section-3.2) with padding characters omitted.
The payload is carried in the `data` field of a gossipsub message, and varies depending on the topic: