zec
/
zips
mirror of https://github.com/zcash/zips.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Add reference to [BCGGMTV2014] when discussing an example of an incorrect security claim. 

Signed-off-by: Daira Hopwood <daira@jacaranda.org>
This commit is contained in:
Daira Hopwood 2022-01-19 18:00:06 +00:00
parent 4ef578706b
commit 24cfab0b55
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
protocol/protocol.tex
View File

@ -3752,9 +3752,9 @@ In this respect the abstractions play a similar rôle to that of a type system (
add a form of redundancy to the specification that helps to express the intent.
Each property is a claim that may be incorrect (or that may be insufficiently precisely stated to
determine whether it is correct). An example of an incorrect security claim occurs in the \Zerocash protocol:
the instantiation of the \noteCommitment scheme used in \Zerocash failed to be \binding at the intended
security level (see \crossref{internalh}).
determine whether it is correct). An example of an incorrect security claim occurs in the \Zerocash protocol
\cite{BCGGMTV2014}: the instantiation of the \noteCommitment scheme used in \Zerocash failed to be \binding
at the intended security level (see \crossref{internalh}).
Another hazard that we should be aware of is that abstractions can be ``leaky'': an instantiation may impose
conditions on its correct or secure use that are not captured by the abstraction's interface and semantics.