[FEATURE] Reuse flow-go libraries
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16
- Forks
- 8
- Avg merge
- 5d 55m
- Merged PRs (30d)
- 1
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by mapping the Rosetta code for event parsing and execution result ID generation against the corresponding flow-go libraries. Done means identifying and adopting flow-go implementations wherever possible across the codebase, but the issue does not name specific files or tests, so the scope must be established first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100