`CHUNK_SIZE` setting about consensus-specs HOT 4 CLOSED

My gut feel is to make the chunks in shard blocks small, maybe 32 bytes. Any reason 256 bytes was chosen @vbuterin?

from consensus-specs.

There are three chunk sizes that could be considered "special":

• aligned with hash function block size - this helps make good use of the hash function itself in terms of entropy and avoiding arbitrary padding
• aligned with hash output size - this would help make all nodes in the tree have the same size, after chunking
• aligned with the largest tree_hash_root output - all inputs have to pass through this function, so using the same here makes it easier to avoid arbitrary-length buffers in the tree hashing code

from consensus-specs.

I'm ok with 32 bytes.

Sorry, I remembered that my original reason for wanting 256 bytes was erasure coding efficiency, but then I remembered that hash tree chunk size and erasure code chunk size do not need to be the same. So 32 byte shard chunks it is.

from consensus-specs.

closing via #344

from consensus-specs.