celestiaorg / celestiaorg/go-header
Recover from panics on verification code paths
Open
- Dominant language
- Go
- Stars
- 21
- Forks
- 33
- Avg merge
- 5d 20h
- Merged PRs (30d)
- 7
Description
We should harden the library against user bugs that may cause panic and crash the node.
Contributor guide
Research direction
Start by locating the verification code paths in the Go library; no file, entry point, or test is named. Clarify which user-triggered panic cases are in scope, then verify that each is handled without crashing the node.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100