Distributions should not be considered "complete" until they've been fully counter signed, executed, and confirmed successful. Running the instance locally results in a scenario where 25k txs could be "completed" in the sense that the operator has finished running their portion of the distribution, but the distribution itself is not yet completed.
Potential solution
We should differentiate when an operator has finished {submitting, signing, etc.} versus when the whole process is complete, e.g. all balances have updated, or transactions have been completed.
Questions
What should the specific status/states be messaged as to provide as much clarity as possible?
Issue
Distributions should not be considered "complete" until they've been fully counter signed, executed, and confirmed successful. Running the instance locally results in a scenario where 25k txs could be "completed" in the sense that the operator has finished running their portion of the distribution, but the distribution itself is not yet completed.
Potential solution
We should differentiate when an operator has finished {submitting, signing, etc.} versus when the whole process is complete, e.g. all balances have updated, or transactions have been completed.
Questions
What should the specific status/states be messaged as to provide as much clarity as possible?