-
Notifications
You must be signed in to change notification settings - Fork 711
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
Blob tx and loading #589
Labels
comp:FVM
Component: FuelVM
enhancement
New feature or request
epic
An epic is a high-level master issue for large pieces of work.
Comments
Dentosal
added
enhancement
New feature or request
comp:FVM
Component: FuelVM
epic
An epic is a high-level master issue for large pieces of work.
labels
Jun 20, 2024
This was referenced Jun 24, 2024
8 tasks
Dentosal
added a commit
that referenced
this issue
Jul 31, 2024
Work towards #589. The VM PR FuelLabs/fuel-vm#780 contains a working implementation. To allow contracts larger than the contract size limit, and to allow upgradability, we'll be adding a new tx type that's just a bunch of bytes, and opcodes to load subsections of that. A *blob* will be like a contract, but without state or balances, allowing it to be quite a bit cheaper. The new instructions `BSIZ` and `BLDD` and the new blob mode for `LDC` closely follow how `CSIZ`, `LDC` and `CCP` work, but only operation on blob data. ### Before requesting review - [x] I have reviewed the code myself
Voxelot
pushed a commit
to FuelLabs/fuel-core
that referenced
this issue
Aug 1, 2024
Work towards FuelLabs/fuel-specs#589. Spec PR FuelLabs/fuel-specs#592. Adds support for Blob transactions, which are inserted into the onchain database column called `Blobs`. Also updates fuel-vm to 0.56.0, which introduces the new tx type. Work-in-progress, still needs: - [x] Regenesis support - [x] Tests ## 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 - [x] I have created follow-up issues caused by this PR and linked them here ### After merging, notify other teams - [ ] [Rust SDK](https://github.com/FuelLabs/fuels-rs/) - [ ] [Sway compiler](https://github.com/FuelLabs/sway/) - [ ] [Platform documentation](https://github.com/FuelLabs/devrel-requests/issues/new?assignees=&labels=new+request&projects=&template=NEW-REQUEST.yml&title=%5BRequest%5D%3A+) (for out-of-organization contributors, the person merging the PR will do this) --------- Co-authored-by: Ahmed Sagdati <37515857+segfault-magnet@users.noreply.github.com> Co-authored-by: segfault-magnet <ahmed.sagdati.ets@gmail.com>
All sub-tasks are done=) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
comp:FVM
Component: FuelVM
enhancement
New feature or request
epic
An epic is a high-level master issue for large pieces of work.
Tracking issue for
Blob
transactions and related opcodes.As discussed with the client team on 2024-06-20, to allow contracts larger than the contract size limit, and to allow upgradability, we'll be adding a new tx type that's just a bunch of bytes, and opcodes to load subsections of that. The whole thing reminds contracts and
LDC
a bit, but blob won't have state or balances, and the corresponding load instructions will be slightly different.Implemented in:
The text was updated successfully, but these errors were encountered: