issues : 36
Great issue: Resolve Durability TTL Mismatch for Pruning
Description
The PRUNE_GRACE_PERIOD is 30 days, which is identical to the TTL_HIGH_THRESHOLD. If a market is not frequently bumped, its persistent data might expire exactly when the pruning window opens, causing admin functions to fail or findings "MarketNotFound".
Requirements and context
- Increase the high TTL threshold to 60-90 days.
- Ensure market data lives safely through and beyond the pruning grace period.
Suggested execution
- Fork the repo and create a branch:
git checkout -b fix/issue-36-ttl-alignment
- Update the state durability settings.
Implementation changes
- Modify
types.rs (around line 148) to extend the persistent storage TTL.
Test and commit
- Verify that market data remains accessible even after 30 days of inactivity.
Example commit message
fix: extend persistent storage TTL to safely cover pruning grace period
Guidelines
- Data availability during lifecycle transitions.
- Timeframe: 24 hours.
issues : 36
Great issue: Resolve Durability TTL Mismatch for Pruning
Description
The
PRUNE_GRACE_PERIODis 30 days, which is identical to theTTL_HIGH_THRESHOLD. If a market is not frequently bumped, its persistent data might expire exactly when the pruning window opens, causing admin functions to fail or findings "MarketNotFound".Requirements and context
Suggested execution
git checkout -b fix/issue-36-ttl-alignmentImplementation changes
types.rs(around line 148) to extend the persistent storage TTL.Test and commit
Example commit message
fix: extend persistent storage TTL to safely cover pruning grace period
Guidelines