Websocket transaction observables failing due to fee breaking rename #74
Description
- Expected behavior and actual behavior.
The expected behavior is to have the newly added maxFee replacing the fee field of transactions. This will be implemented in #53.
Yet, to provide with base cow compatibility, it is important that DTOs can be read with the fee field being deprecated.
Current cow upgraded network nodes include the maxFee field instead of fee field and this breaks compatibility in places where the fee value is used directly, like in UInt64 initializations.
- Steps to reproduce the problem.
- Convert an account to multisig
- Initiate a Multisig Transfer (Aggregate Bonded)
- Send a cosignature transaction
- Specifications like the version of the project, operating system, or hardware.