Anders Konring

Might be missing something but it is not clear to me why this cannot be handled in a simple manner on the Hotshot side like this: https://github.com/EspressoSystems/HotShot/pull/2892

Thanks for the feedback. I've rebased on top of the (refactored) `main`. Let me know if more changes should be considered. Awaiting @nyospe response here: https://github.com/EspressoSystems/jellyfish/pull/561#discussion_r1572693686 before moving forward.

Took the first steps here: https://github.com/EspressoSystems/jellyfish/pull/533 The PR draft replaces `payload_chunk_size` with `erasure_code_rate` and adapts test. The approach is described above; the real rate is the reciprocal of `erasure_code_rate` (usize:...

Using `RAYON_NUM_THREADS` as a proxy for locally confirming the effect of increasing the number of accessible CPUs. Justification: Since Rayon is the primary (parallelization) workhorse in the VID disperse computation...

All findings documented in this Notion document: https://www.notion.so/espressosys/VID-Optimization-2-CPU-cores-666dfb5c4ae04e9c9b306c210af803a9