You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -34,7 +46,7 @@ So why is designing a blob store for BLAKE3 hashed data so complex? What are the
34
46
35
47
The job of a blob store is to store two pieces of data per BLAKE3 `hash`, the actual data itself and an `outboard` containing the flattened hash tree that connects each `chunk` of data to the root hash. Data and outboard are kept separate so that the data can be used as-is.
36
48
37
-
While the [bao] crate stores tree hashes all the way down to ≤ 1024 byte BLAKE3 `chunks`, we store the outboard only down to 16 KiB `chunk groups` to reduce the outboard size.
49
+
While the [bao] crate stores tree hashes all the way down to ≤ 1024 byte BLAKE3 `chunks`, we store the outboard only down to 16 KiB `chunk groups` to reduce the outboard size.
38
50
39
51
## In memory store
40
52
@@ -126,7 +138,7 @@ This is not the end of the world, but it does mean that we need to keep the data
126
138
127
139
# Blob lifecycle
128
140
129
-
There are two fundamentally different ways how data can be added to a blob store.
141
+
There are two fundamentally different ways how data can be added to a blob store.
0 commit comments