With transaction operations, the compatibility layer formerly handed control
to the legacy xmrwallet code, which handled the writing and parsing of
transaction files.
Now control is returned to the caller, which takes care of all transaction file
operations. This allows for the inclusion of metadata required to properly
display transaction details and results in more integrated program flow and a
more consistent user experience.
The legacy code transparently handles the new transaction file format, so that
backwards compatibility is maintained.
The transaction version has been bumped. Offline installations must be upgraded.