With the current spec, we have versioning system for blueprints, but not for the protocol. However, in the future we can have compatibility-breaking changes in the protocol (like the structure of the contract headers, proofs, or to the function for defining which Tx output is used for P2C commitments) and it can't be done without the proper versioning system.
With the current spec, we have versioning system for blueprints, but not for the protocol. However, in the future we can have compatibility-breaking changes in the protocol (like the structure of the contract headers, proofs, or to the function for defining which Tx output is used for P2C commitments) and it can't be done without the proper versioning system.