A core node keeps its neighbor connections healthy and watches each one for misbehavior. Only misbehavior that can be attributed to an authenticated peer leads to disconnection and blacklisting; low or missing traffic affects a connection's health (and may trigger replacement) but never causes a ban.
Two principles hold throughout this document:
MaxCore, even under attack. This bounds the worst-case bandwidth an adversary can force on the node.Symbols from the earlier draft are renamed to self-describing identifiers; an appendix maps the old notation to the new names.
round — the base time unit (see Blend Protocol).epoch — the protocol time scope for participation, quotas, nullifiers, and maintenance. Sessions are not used, per ‣.Window — the length of each connection's moving observation window, in rounds. Window = 30.ExpectedRate — the expected number of validly-signed messages received on one healthy connection per round. It defaults to the Blend per-round message-release upper bound until a tighter fan-out figure is available.window_count(c) — the number of messages on connection c that passed TLS and signature checks during the trailing Window rounds. A count, not a rate; TLS and signature failures never increment it.MinCount = 3 × ExpectedRate — the lower edge of the healthy band.MaxCount = Window × ExpectedRate — the upper edge of the healthy band.CoreConns — open core-to-core connections, including handshakes that have reserved a slot.MinCore, TargetCore, MaxCore — the minimum, target, and maximum core-to-core connections, with MinCore < TargetCore < MaxCore.HealthyCore — the number of currently healthy core-to-core connections.Reserved — reserved but not-yet-established handshake slots.