A small side note: if you followed along with the original TCP FASTOPEN design doc discussion, you may be worried that it is not always safe to enable TCP_FASTOPEN for your storage node. You no longer need to worry about that! We figured out how to make it always safe. Clients that try to use TCP_FASTOPEN will always concurrently try a normal TCP dial, so that at least one will succeed. The node also knows how to effectively “debounce” the incoming connections if both succeed.
In fact, there is now a substantial benefit to enabling TCP_FASTOPEN - if it is enabled, your node has a better chance of winning upload races.