Browse Source

hashes and checksums are different things

The term "hash checksum" doesn't quite make sense. A thing is either a hash, or
a checksum
Ali Yahya 11 years ago
parent
commit
7002281659
1 changed files with 1 additions and 1 deletions
  1. 1 1
      papers/ipfs-cap2pfs/ipfs-cap2pfs.tex

+ 1 - 1
papers/ipfs-cap2pfs/ipfs-cap2pfs.tex

@@ -191,7 +191,7 @@ Notation: data structures and functions below are specified in Go syntax.
 
 \subsection{Identities}
 
-Nodes are identified by a \texttt{NodeId}, the cryptographic hash\footnote{Throughout this document, \textit{hash} and \textit{checksum} refer specifically to cryptographic hash checksums of data.} of a public-key, created with S/Kademlia's static crypto puzzle~\cite{baumgart07}. Nodes store their public and private keys (encrypted with a passphrase). Users are free to instatiate a ``new'' node identity on every launch, though that loses accrued network benefits. Nodes are incentivized to remain the same.
+Nodes are identified by a \texttt{NodeId}, the cryptographic hash\footnote{Throughout this document, \textit{hash} and \textit{checksum} refer specifically to cryptographic hashes of data.} of a public-key, created with S/Kademlia's static crypto puzzle~\cite{baumgart07}. Nodes store their public and private keys (encrypted with a passphrase). Users are free to instatiate a ``new'' node identity on every launch, though that loses accrued network benefits. Nodes are incentivized to remain the same.
 
 \begin{verbatim}
       type NodeId Multihash