dez1337

The idea: Use the correct type internally (e.g. long for uint64), but offer getter and setters for the next bigger type (e.g. BigInteger). This would make sure that the toByteArray()...

[jOOU](https://github.com/jOOQ/jOOU) to the rescue?

Seems to be fully implemented with Jackson 2.9.2

A review of the validation fields is also required afterwards. Beside that it is required to know which fields are optional and which fields need to be present

Operations have been added but the tests are missing. This is postponed to 0.4.2

Check usage of "AccountName" type

1 and 2 are fixed for 0.4.1, but the third point makes more sense when all simplified operations return an AppliedOperation. This requires #76 to be completed. --> Postponed to...

Received no response from users -> Postponed to 0.4.2

Tests and a code cleanup are missing...

Waiting for the following Jackson Issue to be fixed: https://github.com/FasterXML/jackson-databind/issues/1152