feat(13-WAKU2/STORE): add ephemeral flag to wakuMessage

This commit is contained in:
rymnc 2022-09-06 17:46:42 +05:30
parent f0e1f74c4f
commit 3369ad7513
No known key found for this signature in database
GPG Key ID: C740033EE3F41EBD
2 changed files with 7 additions and 0 deletions

View File

@ -21,6 +21,8 @@ As such, they are required to be *highly available* and in specific have a *high
The high uptime requirement makes sure that no message is missed out hence a complete and intact view of the message history is delivered to the querying nodes.
Nevertheless, in case that storage provider nodes cannot afford high availability, the querying nodes may retrieve the historical messages from multiple sources to achieve a full and intact view of the past.
The concept of "ephemeral" messages exists while using `13/WAKU2-STORE` as well. Any `WakuMessage` that has the ephemeral flag set to true will not be added to the store, thereby reducing the amount of one-time use messages on disk. While the node SHOULD not store messages with the ephemeral flag set to true, they MAY do so for archival.
# Security Consideration
The main security consideration to take into account while using `13/WAKU2-STORE` is that a querying node have to reveal their content filters of interest to the queried node, hence potentially compromising their privacy.

View File

@ -38,6 +38,10 @@ The `timestamp` field MAY be filled out to signify the time at which the message
This field holds the Unix epoch time in nanoseconds.
Omitting it means the timestamp is unspecified.
The `ephemeral` field MAY be filled out to signify the transient nature of the message.
Omitting it means the message is permananent, and must be added to the store.
See [13/WAKU2-STORE](/spec/13) for more details.
## Payloads
Payloads are implemented using [protocol buffers v3](https://developers.google.com/protocol-buffers/).
@ -50,6 +54,7 @@ message WakuMessage {
string contentTopic = 2;
uint32 version = 3;
sint64 timestamp = 10;
bool ephemeral = 31;
}
```