aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAndrey Kislyuk <kislyuk@gmail.com>2017-03-07 03:26:43 -0800
committerKarissa McKelvey <karissa@users.noreply.github.com>2017-03-07 12:26:43 +0100
commitb067b326ed7b0f47915251e4870686d4dff51aac (patch)
treec1352d87c3f9368808f411c4cfc42f15098a42a8
parent7ec501ca268d21c562245f2cb234232afefc7355 (diff)
downloaddat-docs-b067b326ed7b0f47915251e4870686d4dff51aac.tar.gz
dat-docs-b067b326ed7b0f47915251e4870686d4dff51aac.zip
Fix typo (#47)
-rw-r--r--papers/dat-paper.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/papers/dat-paper.md b/papers/dat-paper.md
index 0f40700..cb9a4d8 100644
--- a/papers/dat-paper.md
+++ b/papers/dat-paper.md
@@ -123,7 +123,7 @@ Once a duplex binary connection to a remote source is open Dat then layers on it
Content integrity means being able to verify the data you received is the exact same version of the data that you expected. This is imporant in a distributed system as this mechanism will catch incorrect data sent by bad peers. It also has implications for reproducibility as it lets you refer to a specific version of a dataset.
-Link rot, when links online stop resolving, and content drift, when when data changes but the link to the data remains the same, are two common issues in data analysis. For example, one day a file called data.zip might change, but a typical HTTP link to the file does not include a hash of the content, or provide a way to get updated metadata, so clients that only have the HTTP link have no way to check if the file changed without downloading the entire file again. Referring to a file by the hash of its content is called content addressability, and lets users not only verify that the data they receive is the version of the data they want, but also lets people cite specific versions of the data by referring to a specific hash.
+Link rot, when links online stop resolving, and content drift, when data changes but the link to the data remains the same, are two common issues in data analysis. For example, one day a file called data.zip might change, but a typical HTTP link to the file does not include a hash of the content, or provide a way to get updated metadata, so clients that only have the HTTP link have no way to check if the file changed without downloading the entire file again. Referring to a file by the hash of its content is called content addressability, and lets users not only verify that the data they receive is the version of the data they want, but also lets people cite specific versions of the data by referring to a specific hash.
Dat uses SHA256 hashes to address content. Hashes are arranged in a Merkle tree, a tree where each non-leaf node is the hash of all child nodes. Leaf nodes contain pieces of the dataset. This means that in order to verify the integrity of some subset of content only the top most common ancestors of the leaf nodes that contain that content must be fetched. For example to verify all content in a Merkle tree the top level node of the tree can be used. Due to the behavior of secure cryptographic hashes the top hash can only be produced if all data below it matches exactly. If two trees have matching top hashes then you know that all other nodes in the tree must match as well, and you can conclude that your dataset is synchronized.