The transaction format defined in ZIP 230 defined the enableZSA flag to be the third bit (when going from LSB to MSB) in the flagsOrchard byte - i.e., after enableSpendsOrchard and enableOutputsOrchard.
This ZIP has now been withdrawn in favour of ZIP 229, which has an additional enableCrossAddress flag at that position. Therefore, we need to move enableZSA to be the bit after enableCrossAddress.
This has to be done as part of the ZSA transaction format, so this is an open issue until there is more clarity on how that is to be specified (in the spirit of ZIP 248: Extensible Transaction Format, for example)
The transaction format defined in ZIP 230 defined the
enableZSAflag to be the third bit (when going from LSB to MSB) in theflagsOrchardbyte - i.e., afterenableSpendsOrchardandenableOutputsOrchard.This ZIP has now been withdrawn in favour of ZIP 229, which has an additional
enableCrossAddressflag at that position. Therefore, we need to moveenableZSAto be the bit afterenableCrossAddress.This has to be done as part of the ZSA transaction format, so this is an open issue until there is more clarity on how that is to be specified (in the spirit of ZIP 248: Extensible Transaction Format, for example)