aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRobin Vobruba <hoijui.quaero@gmail.com>2022-05-04 12:03:49 +0200
committerRobin Vobruba <hoijui.quaero@gmail.com>2022-05-04 12:03:49 +0200
commit543e7b78f5eb443a80e0c4e8edd4a954646f9663 (patch)
tree3c79d1c8b358ae3a7213d1e27873db0af038482d
parent33c670271c4d02816f9052852bf802789d7a7f64 (diff)
downloadgit-bug-543e7b78f5eb443a80e0c4e8edd4a954646f9663.tar.gz
model: Adds link explaining nounce (wikipedia)
-rw-r--r--doc/model.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/model.md b/doc/model.md
index f0d39f76..94528bc3 100644
--- a/doc/model.md
+++ b/doc/model.md
@@ -21,7 +21,7 @@ An `Operation` is a piece of data including:
- an author (a reference to another entity)
- a timestamp (there is also 1 or 2 Lamport time that we will describe later)
- all the data required by that operation type (a message, a status ...)
-- a random nonce to ensure we have enough entropy, as the operation identifier is a hash of that data (more on that later)
+- a random [nonce](https://en.wikipedia.org/wiki/Cryptographic_nonce) to ensure we have enough entropy, as the operation identifier is a hash of that data (more on that later)
These `Operation`s are aggregated in an `OperationPack`, a simple array. An `OperationPack` represents an edit session of a bug. As the operation's author is the same for all the `OperationPack` we only store it once.