-
Notifications
You must be signed in to change notification settings - Fork 69
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
Allow non privileged inline actions larger then 4KiB #1614
Comments
Please don't have non-working configuration options. Remove the configuration option entirely. |
I agree. We should just remove the option. It is a breaking change but we are allowed to do that in Leap 5.0 since it is a major version bump. The change should also have a test that, while respecting the max inline action depth, creates many inline actions each with a size of 512 KiB just to confirm the Leap software handles it as expected even with the |
…action_size limit and add new test for 512k limit
…d-inline-action-size Remove max-nonprivileged-inline-action-size option
Remove
max-non-privileged-inline-action-size
option and the associated checks in the code. Add a test.There is a 4 KiB limit on inline action size if the sender is not a privileged account. There isn't a business need for this constraint, and it makes our EOS-EVM integration more difficult. We cannot easily change the limit because it is subjectively enforced and we need to convince the whole network to change that config option. Instead we should update the code to no longer enforce this option.
Tasks
The text was updated successfully, but these errors were encountered: