Add CAP-78 - Host function for performing limited TTL extensions #1828
Conversation
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
anupsdf
reviewed
Dec 18, 2025
core/cap-0078.md
Outdated
|
|
||
| ## Simple Summary | ||
|
|
||
| Add a way to limit the maximum TTL extension for persistent contract data entries. |
Contributor
There was a problem hiding this comment.
Should contract code and contract instance entries also have this fine-grained control?
Contributor
Author
There was a problem hiding this comment.
Good catch, I've been too focused on the extension semantics and forgot that we need a different function for instance/code. FWIW code is probably the biggest offender in terms of the rent fee spikes, so we definitely want to support it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.