aboutsummaryrefslogtreecommitdiffstats
path: root/notes/spec_todo.txt
diff options
context:
space:
mode:
Diffstat (limited to 'notes/spec_todo.txt')
-rw-r--r--notes/spec_todo.txt9
1 files changed, 9 insertions, 0 deletions
diff --git a/notes/spec_todo.txt b/notes/spec_todo.txt
index b361f70..ad05c69 100644
--- a/notes/spec_todo.txt
+++ b/notes/spec_todo.txt
@@ -1,15 +1,24 @@
Things that were underspecified in the spec/whitepaper:
+- nonce: 24 or 32 bytes? (impl is 24, spec says 32)
- endianness of magic (big-endian)
- uppercase/lowercase of algorithm name (inconsistent in one place)
- what if there is only a single chunk/entry in a register tree? then a leaf
acts as a root?
+- unclear where protobuf schema actually lives...
+- "append only" is mentioned many times, but need to write "back in" to merkel
+ tree on many occasions
+- inconsistent message names between .proto and whitepaper
"You can use the byteOffset property in the Stat meta- data object to seek into
the right position in the content for the start of this chunk." => unnecessary,
node.js specific?
+"If you are sharing multiple hypercores on the same port you can use this event
+to wait for the remote peer to indicate which hypercore they are interested inj"
+
+
Clarify: appending to tree SLEEP results in writes into middle of file (for
root nodes). This seems not-great for performance (can't bulk-write). Better to
cache or work in RAM then batch commit?