Reth’s new change
#28322 handles a small operational issue: when an eth handshake status message cannot be decoded, the log records the message length and a short prefix instead of outputting the full payload, aligning with the existing approach to logging exception messages. When investigating node connection failures
$ETH , this information usually answers “how much was received, and what did the beginning look like?” The complete raw data may not be suitable for unlimited inclusion in routine logs. This describes a change in error-log output, not a change to handshake validation rules or a claim that all connection problems have been resolved. The PR page status is closed; this alone does not establish that it was merged into an official release.