Skip to content
This repository was archived by the owner on Feb 1, 2024. It is now read-only.

Commit c6d5e23

Browse files
yoni-wolfywolf
authored andcommitted
Update 0000-delete-prefix.md
Signed-off-by: ywolf <yoni.wolf@intel.com>
1 parent ea46e13 commit c6d5e23

1 file changed

Lines changed: 9 additions & 2 deletions

File tree

text/0000-delete-prefix.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ Addition to validator.proto:
9797
# Drawbacks
9898
[drawbacks]: #drawbacks
9999

100-
1. This will need to be implemented in every sawtooth SDK.
100+
1. This will need to be implemented in every Sawtooth SDK.
101101
2. Once implemented it will be difficult to deprecate because of our
102102
commitment to backward compatibility.
103103
3. This requires transaction processor developers to understand the risk of
@@ -119,11 +119,18 @@ list of all addresses. This address could be huge and it needs to be changed
119119
for almost every transaction, while the need to delete all the addresses in
120120
the list is very rare.
121121

122+
Instead of adding a new API for delete prefix that will get list of addresses
123+
prefix, an alternative would be to extend existing delete API to support both
124+
list of addresses prefix and list of full address.
125+
The validator would then need to distinguish each element of the list as
126+
between a full 70 character address as a single address or something less than
127+
70 as a prefix.
128+
122129
# Prior art
123130
[prior-art]: #prior-art
124131

125132
Access address by prefix is a key capability of radix tree.
126-
This RFC intends to take advantage of sawtooth design to use a radix tree for
133+
This RFC intends to take advantage of Sawtooth design to use a radix tree for
127134
storing the global state.
128135

129136
# Unresolved questions

0 commit comments

Comments
 (0)