const MAX_CONCURRENT_START_EXCHANGES: usize = 10_000;Expand description
Ceiling on the per-session term of start_protocol_channel_capacity.
A session contributes to this channel only while its Start exchange is in flight — a handful of
messages between initiation and establishment — after which it is silent apart from PIX, which
the commitment term already covers. So the queue depth tracks concurrent handshakes, not the
total number of sessions the node may manage, and maximum_managed_sessions (validated up to
100 000) is the wrong quantity to size a pre-allocated ring from.