@@ -24,7 +24,7 @@ Fields can be treated as raw (already hashed values) by setting the option `proo
24
24
string value_b = 2 [
25
25
(proofs.exclude_from_tree) = true
26
26
];
27
- bytes value_c = 3[
27
+ bytes value_c = 3 [
28
28
(proofs.hashed_field) = true
29
29
];
30
30
}
@@ -38,7 +38,7 @@ Nested, repeated, and map fields will be flattened following a dotted notation.
38
38
repeated Document fieldB = 2;
39
39
repeated string fieldC = 3;
40
40
map<string, Document> fieldD = 4 [
41
- proofs.key_length = 4
41
+ ( proofs.key_length) = 4
42
42
];
43
43
map<uint64, string> fieldE = 5;
44
44
}
@@ -141,10 +141,9 @@ The respective JSON for the proof would be:
141
141
}
142
142
143
143
There are a few things to note:
144
- * When calculating the hash of the leaf, the dot notation of the property,
145
- the value and salt should be concatenated to produce the hash.
146
- * The default proof expects values of documents to be salted to prevent rainbow table lookups.
147
- * The value is included in the file as a string value not a native type.
144
+ - When calculating the hash of the leaf, the dot notation of the property, the value and salt should be concatenated to produce the hash.
145
+ - The default proof expects values of documents to be salted to prevent rainbow table lookups.
146
+ - The value is included in the file as a string value not a native type.
148
147
149
148
Compact Salt Slice
150
149
When you do processing for a document, if you want to save the salts, you can provide
@@ -165,7 +164,7 @@ with the SaltsLengthSuffix option.
165
164
166
165
Custom Document Prefix
167
166
168
- Library supports adding a prefix to the document path by setting up TreeOption.ParentPrefix to the desired value.
167
+ Library supports adding a prefix to the document path by setting up ` TreeOption.ParentPrefix` to the desired value.
169
168
170
169
171
170
*/
0 commit comments