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

Integration test for forkless updates #1622

Closed
xgreenx opened this issue Jan 24, 2024 · 0 comments
Closed

Integration test for forkless updates #1622

xgreenx opened this issue Jan 24, 2024 · 0 comments
Assignees
Labels
epic An epic is a high-level master issue for large pieces of work. upgradability

Comments

@xgreenx
Copy link
Collaborator

xgreenx commented Jan 24, 2024

No description provided.

@xgreenx xgreenx added the epic An epic is a high-level master issue for large pieces of work. label Feb 4, 2024
@xgreenx xgreenx self-assigned this Mar 13, 2024
xgreenx added a commit that referenced this issue Apr 16, 2024
Closes #1753
Closes #1754
Closes #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 #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](FuelLabs/devrel-requests#9)
xgreenx added a commit that referenced this issue May 29, 2024
…ss upgrades (#1895)

Closes #1622

The change adds integration tests for the forkless upgrade feature. The
tests verify that it is backward compatible and, where possible, forward
compatible.

The main idea is to use published `fuel-core` crates to produce blocks
with different state transition functions.

Tests are using Ignition testnet chain config as a main source to be
compatible with.


### Before requesting review
- [x] I have reviewed the code myself
crypto523 pushed 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)
sui319 added a commit to sui319/fuel-core that referenced this issue Feb 17, 2025
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
Labels
epic An epic is a high-level master issue for large pieces of work. upgradability
Projects
None yet
Development

No branches or pull requests

2 participants