Jon Zlotnik

#3287 would give us more insight into how much we need to reduce the message sizes by, and whether the current sizes are truly problematic. Note: the only message that...

According to issue #673 , we might want to have size checks as part of actual message validation and message building logic as part of a sanity check and safeguard...

Contextually invalid messages, on the level of layers, are not propagated. https://github.com/spacemeshos/go-spacemesh/blob/a09b57a6d7be625b78233fed8128dc2f02e21ef5/hare/broker.go#L146-L165 https://github.com/spacemeshos/go-spacemesh/blob/a09b57a6d7be625b78233fed8128dc2f02e21ef5/hare/broker.go#L246-L258 --- **Intra-layer contextual validity (i.e. level of rounds), however, is not addressed by the p2p message handler.**...

My train of thought here needs to be double checked, but here it is: Eligibility within the context of the message is validated by the broker and returns ValidationIgnore to...

The exploit previously described can be solved in two ways. If possible, both solutions should be implemented as they help in different ways. The first solution is definitely possible to...

This depends on how the leader is supposed to be selected. If the leader is selected by taking the lowest VRF output from the participating status nodes, then there’s no...

Leader selection does not need to change, but SVP validation should only happen once the final leader is ready to be selected. (as explained by @gavraz ) no need to...

Do we see the same memory consumption reported in this issue now that the scale codec is being used?

How will you detect this? And can you specify what you mean be the same committee? All committee members sign both certs?

#3449