fix: extend storage TTL on every invoice save#6
Merged
Conversation
Soroban persistent storage entries expire if TTL is not extended. Recurring and long-lived invoices risk becoming inaccessible. Set min_ttl=100_000 ledgers, max_ttl=6_307_200 (~1 year at 5s/ledger) on every save_invoice call. Closes #5
MarcusDavidG
added a commit
that referenced
this pull request
Jun 19, 2026
fix: extend storage TTL on every invoice save
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #5
Problem
Soroban persistent storage has TTL that expires unless explicitly extended. Long-lived and recurring invoices risk becoming inaccessible after ~4 months without any interaction.
Fix
Call
extend_ttlinsave_invoiceon every write:min_ttl: 100,000 ledgers (~6 days)max_ttl: 6,307,200 ledgers (~1 year at 5s/ledger)Testing