CodeChain-io / CodeChain-io/codechain-indexer
Improve stability
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
The current indexing process is a serial process.
downloading block > saving block info > saving transaction info > saving UTXO info > saving address info > saving address's balance info > ... etc
The problem is, the whole system is broken if a single process goes wrong. For example, saving the balance info should not affect the UTXO data and its API, but, the next block will not be downloaded if the balance logic is broken.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by tracing the indexing sequence described in the issue and identify how failures in each saving step affect block downloading; done means independent data-saving failures no longer stop unrelated indexing or its API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, blockchain, data
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100