Wind Tunnel scenario - Countersigning performance

[abe-njama]

• Two-party countersigning
• Neutral neighborhood countersigning

[ThetaSinner]

We care about measuring two things:

1. Time to completion
2. Failure rate

Need to choose how this gets set up:

• Either we split agents between initiation and signing
• All agents can do either and agents will randomly initiate countersigning

Possibly we actually want to do both. Because both are valid use-cases. So perhaps this issue should be 4 cases, rather than 2?

[ThetaSinner]

• Consider making the scenarios configurable so that we can try them out in different ways and understand what we need to test.
• Two-party could be more than two parties, should be testing between enzymatic and non-enzymatic
• HoloFuel uses non-enzymatic countersigning so we should prioritise that
• Check MM header for the channel about countersigning, has details about when to use which type of countersigning and might help with designing scenarios
  • Countersigning decision tree
• Split issue up:
  • Two-party, non-enzymatic (keep in this task, as a priority)
  • Others in new issues later

[ThetaSinner]

The two-party, non-enzymatic case is done so I'm going to put this back into ready and unassign myself. There is no current plan to test other use patterns for countersigning