-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Upgradable Wasm bytecode #1754
Labels
Comments
This was referenced Apr 3, 2024
This was referenced Apr 10, 2024
xgreenx
added a commit
that referenced
this issue
Apr 15, 2024
Related issue #1754 Updated the upgradable executor to fetch the state transition bytecode from the database when the version doesn't match a native one. This change enables the WASM executor in the "production" build and requires a `wasm32-unknown-unknown` target. The executor has a `VERSION` constant that must be updated when the behavior of the state transition function is changed. That constant is used to decide what executor to use(WASM or native). ## Checklist - [x] New behavior is reflected in tests ### Before requesting review - [x] I have reviewed the code myself
crypto523
added a commit
to crypto523/fuel-core
that referenced
this issue
Oct 7, 2024
…e `ApplicationHeader` (#1767) It is a preparation of the public types for the next changes: FuelLabs/fuel-core#1754 FuelLabs/fuel-core#1753
crypto523
added a commit
to crypto523/fuel-core
that referenced
this issue
Oct 7, 2024
Related issue FuelLabs/fuel-core#1754 Updated the upgradable executor to fetch the state transition bytecode from the database when the version doesn't match a native one. This change enables the WASM executor in the "production" build and requires a `wasm32-unknown-unknown` target. The executor has a `VERSION` constant that must be updated when the behavior of the state transition function is changed. That constant is used to decide what executor to use(WASM or native). ## Checklist - [x] New behavior is reflected in tests ### Before requesting review - [x] I have reviewed the code myself
crypto523
added a commit
to crypto523/fuel-core
that referenced
this issue
Oct 7, 2024
Closes FuelLabs/fuel-core#1753 Closes FuelLabs/fuel-core#1754 Closes FuelLabs/fuel-core#1546 The change upgrade `fuel-vm` to `0.49` introducing `Upgrade` and `Upload` transactions. Supporting these transactions allows the upgrade of consensus parameters and state transition functions for the whole network. The change adds basic e2e tests. More advanced use cases will be tested in the FuelLabs/fuel-core#1622. ## Checklist - [x] Breaking changes are clearly marked as such in the PR description and changelog - [x] New behavior is reflected in tests ### Before requesting review - [x] I have reviewed the code myself ### After merging, notify other teams - [x] [Rust SDK](https://github.com/FuelLabs/fuels-rs/) - [x] [Platform documentation](https://github.com/FuelLabs/devrel-requests/issues/9)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: