poanetwork
/
quorum
mirror of https://github.com/poanetwork/quorum.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update raft.md 

Adding documentation that the timestamp is in nanoseconds.
This commit is contained in:
Satpal 2019-04-29 15:15:49 +01:00 committed by GitHub
parent 78b689baea
commit 0281b26c8f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/raft.md
View File

@ -178,3 +178,7 @@ Additionally there could even be multiple minters running at the same time, but
### Can transactions be reversed? Since raft log entries can be disregarded as "no-ops", does this imply transaction reversal?
No. When a Raft log entry containing a new block is disregarded as a "no-op", its transactions will remain in the transaction pool, and so they will be included in a future block in the chain.
### What's the deal with the block timestamp being stored in nanoseconds (instead of seconds, like other consensus mechanisms)?
With raft-based consensus we can produce far more than one block per second, which vanilla Ethereum implicitly disallows (as the default timestamp resolution is in seconds and every block must have a timestamp greater than its parent). For Raft, we store the timestamp in nanoseconds and ensure it is incremented by at least 1 nanosecond per block.