[FEATURE] Reuse flow-go libraries #76
Description
Issue to be solved
Currently, this Rosetta implementation rewrites a lot of code such as event parsing, execution result id generation etc. which has already been implemented in the flow-go repo.
To make the solution easy-to-maintain and resilient against changes to the the flow data model, code from flow-go repo should be used as much as possible.
This issue is to comb through the code base as switch to using flow-go repo code wherever possible.
Suggest A Solution
No response
What are you currently working on that this is blocking?
No response