More tests: Honey Badger

[afck]

The HoneyBadger tests currently contain an oddly specific "faulty shares" test: Should that be moved to ThresholdDecrypt tests instead? (See #400.)

Apart from that, we need to ensure that the RandomAdversary doesn't almost exclusively send completely nonsensical messages (e.g. with huge epoch numbers), but uses random distributions that are more likely to uncover bugs.

Let's also evaluate whether additional message ordering strategies would make sense (FIFO, LIFO, different "node speed" distributions)—always with the restriction that all messages must eventually be delivered, of course.

[whereistejas]

Hi @afck and @igorbarinov ! Is this issue still open for someone to work on? If yes, I would love to work on this.

I tried to read through the codebase to look for a solution to solve the second issue regarding RandomAdversary since it looks easier to tackle. If I'm not wrong we need to start at this point:

hbbft/hbbft_testing/src/adversary.rs

Line 553 in d52be00

impl<D> Adversary<D> for RandomAdversary

Please, correct me if I'm wrong.

[afck]

I'm not sure anyone is currently actively maintaining this repository, sorry.