crypto-org-chain / crypto-org-chain/cronos-store
memiavl/multitree replay sequentially
Open
- Dominant language
- Go
- Stars
- 0
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
multitree.go replays sequentially via CatchupWAL, we may can use asyncchronous changelog
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading multitree.go and tracing how CatchupWAL currently replays changes sequentially. Clarify the intended asynchronous changelog approach and define completion as replay no longer depending on sequential processing while preserving the existing store behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- database
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100