Avoid state transition use under different contract/schema #99
Labels
*consensus*
Issues affecting distributed concensus
question
Further information is requested
*security*
Issues affecting safety/security (include undefined behaviours)
Milestone
Ensure that it is impossible to construct an attack where a state transition from one contract is re-interpreted under a different contract or scheme. Consider adding commitment to the contract id into the contract nodes (state transitions and state extensions)
The text was updated successfully, but these errors were encountered: