Skip to content

feat: Implement State Footprint & TTL Management (Issue #6)#66

Merged
hman38705 merged 1 commit intosolutions-plug:mainfrom
Emmyt24:features/issue-6-state-footprint-ttl-management
Feb 24, 2026
Merged

feat: Implement State Footprint & TTL Management (Issue #6)#66
hman38705 merged 1 commit intosolutions-plug:mainfrom
Emmyt24:features/issue-6-state-footprint-ttl-management

Conversation

@Emmyt24
Copy link
Copy Markdown
Contributor

@Emmyt24 Emmyt24 commented Feb 24, 2026

closes #12

  • Add TTL constants for persistent storage management
  • Implement automatic TTL bumping on every bet placement
  • Add prune_market() function for archiving resolved markets
  • Track resolved_at timestamp for pruning eligibility
  • Set initial TTL on market creation
  • Extend market TTL to 30 days on each bet interaction

TTL Strategy:

  • LOW_THRESHOLD: ~1 day (17,280 ledgers)
  • HIGH_THRESHOLD: ~30 days (518,400 ledgers)
  • Markets can be pruned 30 days after resolution
  • Admin-controlled pruning for safety

)

- Add TTL constants for persistent storage management
- Implement automatic TTL bumping on every bet placement
- Add prune_market() function for archiving resolved markets
- Track resolved_at timestamp for pruning eligibility
- Set initial TTL on market creation
- Extend market TTL to 30 days on each bet interaction

TTL Strategy:
- LOW_THRESHOLD: ~1 day (17,280 ledgers)
- HIGH_THRESHOLD: ~30 days (518,400 ledgers)
- Markets can be pruned 30 days after resolution
- Admin-controlled pruning for safety
@hman38705 hman38705 merged commit 4322813 into solutions-plug:main Feb 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

State Footprint & TTL Management (Persistent Storage)

2 participants