Feat/account factory ttl extension#369
Merged
Jambox11 merged 2 commits intoJun 28, 2026
Merged
Conversation
|
@marshalfleet Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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
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.
Pull Request Description
Summary
Implemented TTL extension on account factory write operations to ensure account-related registry entries remain available and correctly maintained during runtime interactions.
Changes Made
Added TTL extension logic to account factory write paths
Updated relevant storage operations to refresh TTL when state is modified
Ensured TTL updates occur consistently with existing persistence patterns
Added safeguards for stale, missing, or invalid storage states
Followed existing contract patterns for storage management, validation, and security
Updated documentation where storage behavior or APIs changed
Runtime Behavior
Account factory writes now refresh the associated TTL automatically
Prevents valid account registry data from expiring unexpectedly after active writes
Maintains existing behavior for unaffected read-only operations
Testing
Added tests covering:
TTL extension during successful write operations
Storage updates with refreshed expiration
Handling of stale or invalid states
Existing account factory behavior without regressions
Verified contract tests pass
Confirmed CI checks complete successfully
Acceptance Criteria Covered
TTL extension implemented on account factory writes
Runtime state persistence updated where required
Behavior covered by tests
Documentation updated where APIs changed
Stale/disconnected/invalid states handled gracefully
No regressions in related account factory flows
Closes #227