status-im/specs
2
0
Fork 0
mirror of https://github.com/status-im/specs.git synced 2025-02-10 21:26:21 +00:00
Code Issues Projects Releases Wiki Activity

Minor fix of backtick

Browse Source
This commit is contained in:
Samuel Hawksby-Robinson 2020-09-08 16:53:47 +01:00
parent 0348720fd2
commit 4ed839959d
No known key found for this signature in database
GPG Key ID: 64CF99D4A64A1205
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/draft/6-payloads.md
View File

@ -261,7 +261,7 @@ message is supposed to be displayed last in a chat. This is where the basic algo
as it's only meant to order causally related events.
The status client therefore makes a "bid", speculating that it will beat the current chat-timestamp, s.t. the status client's
Lamport timestamp format is: `clock = `max({timestamp}, chat_clock + 1)`
Lamport timestamp format is: `clock = max({timestamp}, chat_clock + 1)`
This will satisfy the Lamport requirement, namely: a -> b then T(a) < T(b)