You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Other than in the very specific binary_agreement_mitm, the tests currently only use an adversary that randomly reorders messages but doesn't send any.
We should add a general test where the attacker not only reorders, but also creates random messages. Those shouldn't be "completely random", of course: E.g. the epoch should usually be the current one (otherwise they just get ignored), or maybe sometimes ±1. (Configurable as proptest parameters?)
And the boolean value should probably either be random, or the opposite of the correct node's input. Or the opposite of the current coin value, if known?
Ideally, we should come up with different kinds of simple attack strategies that are most likely to uncover bugs.
Not sure if this should replace the existing test, or be added to it.
The text was updated successfully, but these errors were encountered:
Other than in the very specific
binary_agreement_mitm
, the tests currently only use an adversary that randomly reorders messages but doesn't send any.We should add a general test where the attacker not only reorders, but also creates random messages. Those shouldn't be "completely random", of course: E.g. the epoch should usually be the current one (otherwise they just get ignored), or maybe sometimes ±1. (Configurable as proptest parameters?)
And the boolean value should probably either be random, or the opposite of the correct node's input. Or the opposite of the current coin value, if known?
Ideally, we should come up with different kinds of simple attack strategies that are most likely to uncover bugs.
Not sure if this should replace the existing test, or be added to it.
The text was updated successfully, but these errors were encountered: