summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFlorian Dold <florian@dold.me>2021-04-12 19:36:24 +0200
committerFlorian Dold <florian@dold.me>2021-04-12 19:36:24 +0200
commit1226c0dde2a8379f1ec0fad6099357dc3dcb60e5 (patch)
tree1175f18a7ffa9bb51f75199a2ccb7116f1878d45
parent1851c8f16ed73f8ca16be71577ed7dc7cf92b5df (diff)
downloaddocs-1226c0dde2a8379f1ec0fad6099357dc3dcb60e5.tar.gz
docs-1226c0dde2a8379f1ec0fad6099357dc3dcb60e5.tar.bz2
docs-1226c0dde2a8379f1ec0fad6099357dc3dcb60e5.zip
DD18 question
-rw-r--r--design-documents/018-contract-json.rst6
1 files changed, 6 insertions, 0 deletions
diff --git a/design-documents/018-contract-json.rst b/design-documents/018-contract-json.rst
index 2bc147b..7c62600 100644
--- a/design-documents/018-contract-json.rst
+++ b/design-documents/018-contract-json.rst
@@ -126,6 +126,9 @@ The hash of a member value ``memb_val`` with salt ``memb_salt`` is computed as f
salt: memb_salt,
});
+When encoding ``memb_salted_hash`` with base32-crockford, the resulting output
+must be upper-case.
+
Scrubbing
---------
@@ -165,3 +168,6 @@ Discussion / Q&A
forgetting a member. This would save storage. But to prove that a certain
forgettable info matches the contract terms, the prover would need to
also store/provide the salt.
+
+* What validations should the wallet do? Should the wallet ever accept
+ contract terms where fields are already forgotten?