hyperledger / hyperledger/fabric-x-evm
Validate Full Ledger Replay Recovery
- Dominant language
- Go
- Stars
- 12
- Forks
- 18
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 23
Description
Validate that the Gateway can be completely destroyed and recreated from scratch by replaying the entire Fabric ledger without any data loss or manual intervention. Implement and test a recovery procedure where a new Gateway instance starts with an empty database, connects to the Fabric network, and synchronizes the complete blockchain history from genesis to the current block. Verify that after synchronization completes, the Gateway has identical state to a Gateway that has been running continuously, including all blocks, transactions, logs, and indexes. Test this recovery process with ledgers of various sizes to ensure it scales appropriately. Document the recovery procedure and expected synchronization time. This capability is critical for disaster recovery and enables operational flexibility in managing Gateway deployments.
---
**Quarter:** Q3
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by locating the Gateway startup, Fabric ledger synchronization, and persistence entry points, then identify how an empty database can replay history from genesis. Done means a recreated Gateway matches a continuously running one across blocks, transactions, logs, and indexes, with tests for different ledger sizes and recovery documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100