Skip to content
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

Execution parameters in dynamic protocol state #6893

Open
janezpodhostnik opened this issue Jan 15, 2025 · 0 comments
Open

Execution parameters in dynamic protocol state #6893

janezpodhostnik opened this issue Jan 15, 2025 · 0 comments
Assignees

Comments

@janezpodhostnik
Copy link
Contributor

janezpodhostnik commented Jan 15, 2025

Problem Definition

Execution parameters need to move into the dynamic protocol state.

Execution parameters is the following data:

  • execution component version
  • cadence component version
  • execution effort weights
  • execution memory weights
  • execution memory limit

Benefits:

  • This simplifies the programs cache, because it has an easier job with invalidation when execution parameters change and the execution parameters no longer need to be in the cache
  • It removes the need to read this settings in the FVM. The read of execution parameters currently has a lot of special casing code (because you need some execution parameters to read the execution parameters)
  • Enables us to remove addresses hardcoded in FVM (fvm/systemcontracts/system_contracts.go, executionParametersAddressTestnet & executionParametersAddressMainnet) because they would no longer be needed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants