in 0.13.1 we changed the definition of compiled_class_hash, specifically for Sierra 1.5.0 classes (i.e. code compiled with the new 2.6.0 compiler)
This means that current declaration code in SDKs won’t be able to declare classes compiled with 2.6.0
The relevant change is the addition of the bytecode_segments_length to the CASM class, which affects how the bytecode hash is computed (instead of one large chain-hash, it is a chain hash of function hashes, where functions code is determined by the locations in the new field). You can see the pythonic reference implementation here.
in 0.13.1 we changed the definition of compiled_class_hash, specifically for Sierra 1.5.0 classes (i.e. code compiled with the new 2.6.0 compiler)
This means that current declaration code in SDKs won’t be able to declare classes compiled with 2.6.0 The relevant change is the addition of the
bytecode_segments_lengthto the CASM class, which affects how the bytecode hash is computed (instead of one large chain-hash, it is a chain hash of function hashes, where functions code is determined by the locations in the new field). You can see the pythonic reference implementation here.