diff options
| author | Bryan Newbold <bnewbold@robocracy.org> | 2018-03-14 22:45:58 -0700 |
|---|---|---|
| committer | Bryan Newbold <bnewbold@robocracy.org> | 2018-03-14 22:45:58 -0700 |
| commit | deb2cf2bdec1eecbeed0231de088f44936d28e57 (patch) | |
| tree | 7309140ad46ba7d7b1ea59d2ce3bf4116e9ac17d | |
| parent | 6ed881f01d340310a8ce28db05ba4dd0705ad9f0 (diff) | |
| download | dat-deps-deb2cf2bdec1eecbeed0231de088f44936d28e57.tar.gz dat-deps-deb2cf2bdec1eecbeed0231de088f44936d28e57.zip | |
confirmed all-zero hashing key
| -rw-r--r-- | proposals/0000-hyperdb.md | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/proposals/0000-hyperdb.md b/proposals/0000-hyperdb.md index 8c054f9..19f1d5d 100644 --- a/proposals/0000-hyperdb.md +++ b/proposals/0000-hyperdb.md @@ -564,12 +564,6 @@ mafintosh mentioned this might be in the works. Does this DEP need to "leave room" for those changes, or should we call out the potential for future change? (Probably not, should only describe existing solutions) -Should all-zeros really be used for path hashing, or should we use the -hypercore feed public key? It certainly makes implementation and documentation -simpler to use all-zeros, and potentially makes it easier to copy or migrate -HyperDB content between hypercore feeds. Referencing the feed public key breaks -abstraction layers and the separation of concerns. - There are implied "reasonable" limits on the size (in bytes) of both keys and values, but they are not formally specified. Protobuf messages have a hard specified limit of 2 GByte (due to 32-bit signed arthimetic), and most |