Relax finalty-gated caches to F3 or finality calculator
- Dominant language
- Rust
- Stars
- 697
- Forks
- 200
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 65
Description
# Summary
Right now in finality-gated caches we use just whatever is set for the chain (900). This is okay but we can do better with F3 or finality calculator - we'd be able to fill the caches faster.
# Completion Criteria
- [ ] sweep through finality-gated caches and see where more relaxed restriction could be used; be skeptical, there might be places where we can't do it for some reason (can't think of any off the top of my head, though)
- [ ] implement the changes
- [ ] tests!
# Additional Links & Resources
Contributor guide
Research direction
Search the repository for finality-gated caches and existing uses of the chain's 900 finality setting; compare them with F3 or the finality calculator. Review each cache's safety assumptions, update only eligible restrictions, and add tests covering the relaxed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100