When implementing data API, is balance tracking a must have?
By balance tracking I mean this:
- the current implementation correctly displays the balance of the given address at the given height.
- not all state changes that move value (coins) are represented via rosetta operations.
Hence query balance will work correctly, but doing an input/output calculation on the operations spawned when querying all transactions via data API will not represent the correct balance contained in the state.