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.
Release v0.20.0
The release brings a couple of new breaking changes from the
fuel-vm 0.35.0
with bugfixes. Check the description of the VM release for more details.The
fuel-core
release mostly improved the internal codebase but also brought some breaking changes:Trigger::Hybrid
PoA block trigger mode. OnlyTrigger::Instante
andTrigger::Interval
are available for block production now. The main mode for testnets and mainnet will beInterval
.OpaqueReceipt
and theReceipt
type doesn't have theraw_payload
field anymore.Receipt
type got two new variants:Mint
andBurn
. The corresponding opcodes emit these new events.AssetId
is derived fromContractId
and additional nonce. So theContractId
andAssetId
can't be the same anymore.What's Changed
fuel-core
during benches by @xgreenx in Use production configuration forfuel-core
during benches #1227CheckedTransaction
from transaction pool in the executor by @xgreenx in ReusedCheckedTransaction
from transaction pool in the executor #1249fuel-vm
to0.35.0
version by @xgreenx in Bumpfuel-vm
to0.35.0
version #1256New Contributors
Full Changelog: v0.19.1...v0.20.0