-
Notifications
You must be signed in to change notification settings - Fork 241
SIMD-0392: Relaxation of post-execution min_balance check #392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
t-nelson
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a few nits, but lgtm assuming we choose to go the grandfather route. i'm not totally sold that the disruption will be so big a deal
|
Hi, checking in on the status of the SIMD. Is it ready for another round of reviews? (If yes, I suggest requesting re-reviews from folks.) Has there been any testing on a local cluster to mimic a rent increase, esp w.r.t. stake accounts? |
|
|
spl-token, spl-token-2022, and p-token have no issues, we would do similar to stake program and hardcode the maximum rent. im not aware of any programs other than these and stake that are affected. we can start the change process whenever this is accepted we should also put that maximum in the simd, maybe under "new terminology" or "proposed changes" |
95ae824 to
f6041a9
Compare
brooksprumo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks good to me! Some nits/questions:
brooksprumo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. I defer to @2501babe for all stake-related considerations.
when/where was this decided? |
When this proposal is merged, I guess. If there are alternatives you still think may be better then we can discuss them here. |
|
it's in the discussion #399 (comment) |
We can continue the discussion there if you prefer. I believe I was the last person to comment on the topic (ref). |
| - `legacy_rent_per_byte`: the fixed rent-exempt per-byte rate used prior to this | ||
| proposal. | ||
|
|
||
| ``` | ||
| acc_size = ACCOUNT_STORAGE_OVERHEAD + acc.data.len; | ||
| // 6,960 lamports on mainnet-beta | ||
| legacy_rent_per_byte = LAMPORTS_PER_BYTE_YEAR * EXEMPTION_THRESHOLD | ||
| legacy_min_balance = legacy_rent_per_byte * acc_size | ||
| ``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this be part of the calculate_min_balance calculation? I don't see this legacy_min_balance used anywhere else in this proposal - am I missing something?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you're not missing anything, I just included this to show how the min balance is currently calculated with references to the relevant constants in case people weren't familiar. Not really relevant to the rest of the content.
No description provided.