Handle double spending transactions #1
Description
It may be the case that two simultaneous proposals happen to have one or more identical boxes in their inputs. So one of them gets approved sooner and its associated tx will be mined. So now the other proposal's tx is invalid anyway, however, it may be the case that some commitments are already generated for the proposal. This case should be handled somehow!