-
Notifications
You must be signed in to change notification settings - Fork 673
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
Limit keys and values in storage, limit state part size #1805
Comments
@evgenykuzyakov The first two items are implemented by #1913 correct? |
@Kouprin the PR does not seem to be blocked anymore. Assigning it to you, so that you can merge and close it. Also lowered the priority to P1 since the initial assignment of P0 was incorrect, I think. |
@nearmax what is happened that you assigned this task on me? |
This issue is waiting for #1771 to be done, since you are the person working on it I assigned it to you. Once the PR is closed this issue should be closed too. |
This is not needed before the Mainnet, since we will be able to introduce this variable into config later, together with other new variables. Moving to Ice Box |
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. |
I believe we have all the limiters we need. Just need to investigate the upper bound for state parts. |
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. |
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. |
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. |
Boundary for state part size is tracked in #1786. |
max_state_part_overhead
, see Bounded state parts #1792 and using lzma to compress/decompress state_parts #1771The text was updated successfully, but these errors were encountered: