Set syavar rent_epoch at new update time #3398
Draft
+34
−14
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.
Problem
When we create new sysvar, we make sure that it is rent exempt. But we don't set it rent_epoch to
RENT_EXEMPT_EPOCH
. Instead, we are relying on rent collection code to do that.In the future, after we skip the rewrite, we will also disable rent collection. Therefore, we can't rely on the rent collection code to set
rent_epoch
.In this PR, we set
rent_epoch
toRENT_EXEMPT_EPOCH
at the time of new sysvar update time.Note that this won't affect existing sysvars since they have already all have rent_epoch set to u64::MAX. But it is a "must-have" for disable rent collection code.
A quick scan of all sysvars on mainnet shows that all of them are rent exempt and have
rent_epoch
set toRENT_EXEMPT_EPOCH
.Summary of Changes
Fixes #