@inaltoasinistra on our recent meeting has pointed out a possible "double-spend" type bug with versioning system. If we have a proof of more recent version spending outputs of proofs with different versions (having different commitment schemes), there will be no way to check that there is no another proof with the previous version spending some of the same outputs. In order to prevent this kind of attack we need to prohibit proofs to spend inputs having different version numbers.
@inaltoasinistra on our recent meeting has pointed out a possible "double-spend" type bug with versioning system. If we have a proof of more recent version spending outputs of proofs with different versions (having different commitment schemes), there will be no way to check that there is no another proof with the previous version spending some of the same outputs. In order to prevent this kind of attack we need to prohibit proofs to spend inputs having different version numbers.