[Access] add config to limit script execution range - v0.33 #5282
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.
Backports: #5075
Limit the block range an AN will use for executing scripts and getting accounts when configured to use local data.
This is a stop-gap solution for node upgrades before #5040 is completed.
Usage:
When a cadence/fvm upgrade is planned: after the stop height is known and before it is reached, add the
--script-execution-min-height
flag passing the stop height and update the AN to the new version. This will cause the AN to stop locally executing scripts for any height below the stop height.When running a "historic" node, set
--script-execution-min-height
to the first block supported by the current version--script-execution-max-height
to the last block supported by the current versionThe node will then locally execute scripts for blocks between the heights (inclusive), and fall back to ENs for the rest.