v0.27.0

Version v0.27.0

Added

• #1898: Enforce increasing of the Executor::VERSION on each release.

Changed

• #1906: Makes cli::snapshot::Command members public such that clients can create and execute snapshot commands programmatically. This enables snapshot execution in external programs, such as the regenesis test suite.
• #1891: Regenesis now preserves FuelBlockMerkleData and FuelBlockMerkleMetadata in the off-chain table. These tables are checked when querying message proofs.
• #1886: Use ref to Block in validation code
• #1876: Updated benchmark to include the worst scenario for CROO opcode. Also include consensus parameters in bench output.
• #1879: Return the old behaviour for the discovery_works test.
• #1848: Added version field to the Block and BlockHeader GraphQL entities. Added corresponding version field to the Block and BlockHeader client types in fuel-core-client.
• #1873: Separate dry runs from block production in executor code, remove ExecutionKind and ExecutionType, remove thread_block_transaction concept, remove PartialBlockComponent type, refactor away inner functions.
• #1900: Update the root README as fuel-core run no longer has --chain as an option. It has been replaced by --snapshot.

Breaking

• #1894: Use testnet configuration for local testnet.
• #1894: Removed support for helm chart.
• #1910: fuel-vm upgraded to 0.50.0. More information in the changelog.

What's Changed

• feat: Support block and header versions gql by @bvrooman in #1848
• Updated croo opcode benchmark to depend on the contract size by @xgreenx in #1876
• Return the old behaviour for the discovery_works test by @xgreenx in #1879
• Weekly cargo update by @github-actions in #1880
• Separate production from dry runs in executor & Cleanup all execution paths :) by @MitchTurner in #1873
• Use ref instead of owned Block in validation by @MitchTurner in #1886
• Weekly cargo update by @github-actions in #1893
• ci: fix typos programmatically by @sdankel in #1890
• feat: Preserve message proofs post-regenesis by @bvrooman in #1891
• chore: update README fuel-core run options by @K1-R1 in #1900
• Weekly cargo update by @github-actions in #1903
• chore: Make snapshot command members pub accessible by @bvrooman in #1906
• Use testnet configuration for local testnet by @xgreenx in #1894
• Enforce increasing of the Executor::VERSION on each release by @xgreenx in #1898
• Bumped the version of the fuel-vm to 0.50.0 by @xgreenx in #1910
• Release v0.27.0 by @xgreenx in #1912

New Contributors

• @K1-R1 made their first contribution in #1900

Full Changelog: v0.26.0...v0.27.0

v0.26.0

Version v0.26.0

Fixed

Breaking

• #1868: Include the event_inbox_root in the header hash. Changed types of the transactions_count to u16 and message_receipt_count to u32 instead of u64. Updated the application hash root calculation to not pad numbers.
• #1866: Fixed a runtime panic that occurred when restarting a node. The panic happens when the relayer database is already populated, and the relayer attempts an empty commit during start up. This invalid commit is removed in this PR.
• #1871: Fixed block endpoint to return fetch the blocks from both databases after regenesis.
• #1856: Replaced instances of Union with Enum for GraphQL definitions of ConsensusParametersVersion and related types. This is needed because Union does not support multiple Versions inside discriminants or empty variants.
• #1870: Fixed benchmarks for the 0.25.3.
• #1870: Improves the performance of getting the size of the contract from the InMemoryTransaction.
• #1851: Provided migration capabilities (enabled addition of new column families) to RocksDB instance.

Added

• #1853: Added a test case to verify the database's behavior when new columns are added to the RocksDB database.
• #1860: Regenesis now preserves FuelBlockIdsToHeights off-chain table.

Changed

• #1847: Simplify the validation interface to use Block. Remove Validation variant of ExecutionKind.
• #1832: Snapshot generation can be cancelled. Progress is also reported.
• #1837: Refactor the executor and separate validation from the other use cases

What's Changed

• Weekly cargo update by @github-actions in #1850
• Refactor/separate validation from other executions by @MitchTurner in #1837
• fix: Use Enum for ConsensusParametersVersion and related types by @bvrooman in #1856
• feat: snapshot generation graceful shutdown by @segfault-magnet in #1832
• regenesis: migrate FuelBlockIdsToHeights by @Dentosal in #1860
• Weekly cargo update by @github-actions in #1869
• Refactor/Simplify validation logic by @MitchTurner in #1847
• Fixed block endpoint to return fetch the blocks from both databases after regenesis by @xgreenx in #1871
• Add Eq and Partial Eq to tx response and status by @MujkicA in #1872
• test: restart with relayer data by @bvrooman in #1866
• Fix BlockHeader hash by @MitchTurner in #1868
• Added a test for the case of adding new columns into the existing RocksDB database by @xgreenx in #1853
• Fixed benchmarks for the 0.25.3 by @xgreenx in #1870
• Release v0.26.0 by @xgreenx in #1874

Full Changelog: v0.25.3...v0.26.0

v0.25.3

What's Changed

• fix: Use Enum for GQL versions (0.25.3) by @bvrooman in #1862
• Release v0.25.3 by @bvrooman in #1864
• fix: Bump executor crate version by @bvrooman in #1865

Full Changelog: v0.25.2...v0.25.3

v0.24.3

What's Changed

• fix: Use Enum for GQL versions (0.24.3) by @bvrooman in #1861
• Upgrade 0.24.2 to 0.24.3 by @bvrooman in #1863

Full Changelog: v0.24.2...v0.24.3

v0.25.2

Version v0.25.1

Fixed

• #1844: Fixed the publishing of the fuel-core 0.25.1 release.
• 1842: Ignore RUSTSEC-2024-0336: rustls::ConnectionCommon::complete_io could fall into an infinite loop based on network
• #1840: Fixed the publishing of the fuel-core 0.25.0 release.
• #1821: Can handle missing tables in snapshot.
• #1814: Bugfix: the iter_all_by_prefix was not working for all tables. The change adds a Rust level filtering.

Added

• #1831: Included the total gas and fee used by transaction into TransactionStatus.
• #1821: Propagate shutdown signal to (re)genesis. Also add progress bar for (re)genesis.
• #1813: Added back support for /health endpoint.
• #1799: Snapshot creation is now concurrent.
• #1811: Regenesis now preserves old blocks and transactions for GraphQL API.

Changed

• #1833: Regenesis of SpentMessages and ProcessedTransactions.
• #1830: Use versioning enum for WASM executor input and output.
• #1816: 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.
• #1812: Follow-up PR to simplify the logic around parallel snapshot creation.
• #1809: Fetch ConsensusParameters from the database
• #1808: Fetch consensus parameters from the provider.

Breaking

• #1826: The changes make the state transition bytecode part of the ChainConfig. It guarantees the state transition's availability for the network's first blocks.
  The change has many minor improvements in different areas related to the state transition bytecode:

  • The state transition bytecode lies in its own file(state_transition_bytecode.wasm) along with the chain config file. The ChainConfig loads it automatically when ChainConfig::load is called and pushes it back when ChainConfig::write is called.

  • The fuel-core release bundle also contains the fuel-core-wasm-executor.wasm file of the corresponding executor version.

  • The regenesis process now considers the last block produced by the previous network. When we create a (re)genesis block of a new network, it has the height = last_block_of_old_netowkr + 1. It continues the old network and doesn't overlap blocks(before, we had old_block.height == new_genesis_block.hegiht).

  • Along with the new block height, the regenesis process also increases the state transition bytecode and consensus parameters versions. It guarantees that a new network doesn't use values from the previous network and allows us not to migrate StateTransitionBytecodeVersions and ConsensusParametersVersions tables.

  • Added a new CLI argument, native-executor-version, that allows overriding of the default version of the native executor. It can be useful for side rollups that have their own history of executor upgrades.

  • Replaced:

             let file = std::fs::File::open(path)?;
             let mut snapshot: Self = serde_json::from_reader(&file)?;

    with a:

             let mut json = String::new();
             std::fs::File::open(&path)
                 .with_context(|| format!("Could not open snapshot file: {path:?}"))?
                 .read_to_string(&mut json)?;
             let mut snapshot: Self = serde_json::from_str(json.as_str())?;

    because it is 100 times faster for big JSON files.

  • Updated all tests to use Config::local_node_* instead of working with the SnapshotReader directly. It is the preparation of the tests for the futures bumps of the Executor::VERSION. When we increase the version, all tests continue to use GenesisBlock.state_transition_bytecode = 0 while the version is different, which forces the usage of the WASM executor, while for tests, we still prefer to test native execution. The Config::local_node_* handles it and forces the executor to use the native version.

  • Reworked the build.rs file of the upgradable executor. The script now caches WASM bytecode to avoid recompilation. Also, fixed the issue with outdated WASM bytecode. The script reacts on any modifications of the fuel-core-wasm-executor and forces recompilation (it is why we need the cache), so WASM bytecode always is actual now.

• #1822: Removed support of Create transaction from debugger since it doesn't have any script to execute.
• #1822: Use fuel-vm 0.49.0 with new transactions types - Upgrade and Upload. Also added max_bytecode_subsections field to the ConsensusParameters to limit the number of bytecode subsections in the state transition bytecode.
• #1816: 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.

What's Changed

• Add PR template by @Dentosal in #1806
• feat: Parallellize snapshot creation by @segfault-magnet in #1799
• Follow-up PR to simplify the logic around parallel snapshot creation by @xgreenx in #1812
• Bugfix: the iter_all_by_prefix was not working for all tables by @xgreenx in #1814
• Added back support for /health endpoint by @xgreenx in #1813
• Fetch consensus parameters from the provider by @xgreenx in #1808
• Fetch ConsensusParameters from the database by @xgreenx in #1809
• Handle FTI messages in executor by @Voxelot in #1787
• Use state transition bytecode from the database by @xgreenx in #1816
• feat: (re)genesis graceful shutdown by @segfault-magnet in #1821
• Use fuel-vm 0.49.0 with new transactions types by @xgreenx in #1822
• Included the total gas and fee into TransactionStatus by @xgreenx in #1831
• Use versioning enum for WASM executor input and output by @xgreenx in #1830
• Support upgradability of the consensus parameters and state transition bytecode in genesis by @xgreenx in #1826
• Store old blocks and txs after regenesis by @Dentosal in #1811
• Regenesis of SpentMessages and ProcessedTransactions by @xgreenx in #1833
• Release v0.25.0 by @xgreenx in #1839
• Fixed the publishing of the fuel-core 0.25.0 by @xgreenx in #1840
• Release v0.25.1 by @xgreenx in #1841
• Ignore vulnerability RUSTSEC-2024-0336 by @MitchTurner in #1842
• Fixed the publishing of the fuel-core 0.25.1 by @xgreenx in #1844
• Release v0.25.2 by @xgreenx in #1845

Full Changelog: v0.24.2...v0.25.2

v0.24.2

Version v0.24.2

Changed

Breaking

• #1798: add nonce to relayed transactions and also hash full messages in the inbox root.

Fixed

• #1802: Fixed a runtime panic that occurred when restarting a node. The panic was caused by an invalid database commit while loading an existing off-chain database. The invalid commit is removed in this PR.
• #1803: Produce block when da height haven't changed.
• #1795: Fixed the building of the fuel-core-wasm-executor to work outside of the fuel-core context. The change uses the path to the manifest file of the fuel-core-upgradable-executor to build the fuel-core-wasm-executor instead of relying on the workspace.

What's Changed

• Weekly cargo update by @github-actions in #1794
• Improvements for the fuel-core-upgradable-executor build script by @xgreenx in #1795
• Use full hash for messages in inbox_root and add nonce to relayed transactions by @Voxelot in #1798
• Modify block producer to take into account the total gas used by the L1 transactions by @MitchTurner in #1785
• Fix: Produce block when da height haven't changed by @xgreenx in #1803
• fix: Fix commit error on GraphQL service startup by @bvrooman in #1802
• Release v0.24.2 by @xgreenx in #1805

Full Changelog: v0.24.1...v0.24.2

v0.24.1

Version v0.24.1

Added

• #1786: Regenesis now includes off-chain tables.
• #1716: Added support of WASM state transition along with upgradable execution that works with native(std) and WASM(non-std) executors. The fuel-core now requires a wasm32-unknown-unknown target to build.
• #1770: Add the new L1 event type for forced transactions.
• #1767: Added consensus parameters version and state transition version to the ApplicationHeader to describe what was used to produce this block.
• #1760: Added tests to verify that the network operates with a custom chain id and base asset id.
• #1752: Add ProducerGasPrice trait that the Producer depends on to get the gas price for the block.
• #1747: The DA block height is now included in the genesis state.
• #1740: Remove optional fields from genesis configs
• #1737: Remove temporary tables for calculating roots during genesis.
• #1731: Expose schema.sdl from fuel-core-client.

Changed

Breaking

• #1771: Contract 'states' and 'balances' brought back into ContractConfig. Parquet now writes a file per table.

• 1779: Modify Relayer service to order Events from L1 by block index

• #1783: The PR upgrade fuel-vm to 0.48.0 release. Because of some breaking changes, we also adapted our codebase to follow them:

  • Implementation of Default for configs was moved under the test-helpers feature. The fuel-core binary uses testnet configuration instead of Default::default(for cases when ChainConfig was not provided by the user).
  • All parameter types are enums now and require corresponding modifications across the codebase(we need to use getters and setters). The GraphQL API remains the same for simplicity, but each parameter now has one more field - version, that can be used to decide how to deserialize.
  • The UtxoId type now is 34 bytes instead of 33. It affects hex representation and requires adding 00.
  • The block_gas_limit was moved to ConsensusParameters from ChainConfig. It means the block producer doesn't specify the block gas limit anymore, and we don't need to propagate this information.
  • The bytecodeLength field is removed from the Create transaction.
  • Removed ConsensusParameters from executor config because ConsensusParameters::default is not available anymore. Instead, executors fetch ConsensusParameters from the database.

• #1769: Include new field on header for the merkle root of imported events. Rename other message root field.

• #1768: Moved ContractsInfo table to the off-chain database. Removed salt field from the ContractConfig.

• #1761: Adjustments to the upcoming testnet configs:

  • Decreased the max size of the contract/predicate/script to be 100KB.
  • Decreased the max size of the transaction to be 110KB.
  • Decreased the max number of storage slots to be 1760(110KB / 64).
  • Removed fake coins from the genesis state.
  • Renamed folders to be "testnet" and "dev-testnet".
  • The name of the networks are "Upgradable Testnet" and "Upgradable Dev Testnet".

• #1694: The change moves the database transaction logic from the fuel-core to the fuel-core-storage level. The corresponding issue described the reason behind it.

  Technical details of implementation

  • The change splits the KeyValueStore into KeyValueInspect and KeyValueMutate, as well the Blueprint into BlueprintInspect and BlueprintMutate. It allows requiring less restricted constraints for any read-related operations.

  • One of the main ideas of the change is to allow for the actual storage only to implement KeyValueInspect and Modifiable without the KeyValueMutate. It simplifies work with the databases and provides a safe way of interacting with them (Modification into the database can only go through the Modifiable::commit_changes). This feature is used to track the height of each database during commits and even limit how commits are done, providing additional safety. This part of the change was done as a separate commit.

  • The StorageTransaction is a StructuredStorage that uses InMemoryTransaction inside to accumulate modifications. Only InMemoryTransaction has a real implementation of the KeyValueMutate(Other types only implement it in tests).

  • The implementation of the Modifiable for the Database contains a business logic that provides additional safety but limits the usage of the database. The Database now tracks its height and is responsible for its updates. In the commit_changes function, it analyzes the changes that were done and tries to find a new height(For example, in the case of the OnChain database, we are looking for a new Block in the FuelBlocks table).

  • As was planned in the issue, now the executor has full control over how commits to the storage are done.

  • All mutation methods now require &mut self - exclusive ownership over the object to be able to write into it. It almost negates the chance of concurrent modification of the storage, but it is still possible since the Database implements the Clone trait. To be sure that we don't corrupt the state of the database, the commit_changes function implements additional safety checks to be sure that we commit updates per each height only once time.

  • Side changes:

    • The drop function was moved from Database to RocksDB as a preparation for the state rewind since the read view should also keep the drop function until it is destroyed.
    • The StatisticTable table lives in the off-chain worker.
    • Removed duplication of the Database from the dap::ConcreteStorage since it is already available from the VM.
    • The executor return only produced Changes instead of the storage transaction, which simplifies the interaction between modules and port definition.
    • The logic related to the iteration over the storage is moved to the fuel-core-storage crate and is now reusable. It provides an interator method that duplicates the logic from MemoryStore on iterating over the BTreeMap and methods like iter_all, iter_all_by_prefix, etc. It was done in a separate revivable commit.
    • The MemoryTransactionView is fully replaced by the StorageTransactionInner.
    • Removed flush method from the Database since it is not needed after #1664.

• #1693: The change separates the initial chain state from the chain config and stores them in separate files when generating a snapshot. The state snapshot can be generated in a new format where parquet is used for compression and indexing while postcard is used for encoding. This enables importing in a stream like fashion which reduces memory requirements. Json encoding is still supported to enable easy manual setup. However, parquet is prefered for large state files.

  Snapshot command

  The CLI was expanded to allow customizing the used encoding. Snapshots are now generated along with a metadata file describing the encoding used. The metadata file contains encoding details as well as the location of additional files inside the snapshot directory containing the actual data. The chain config is always generated in the JSON format.

  The snapshot command now has the '--output-directory' for specifying where to save the snapshot.

  Run command

  The run command now includes the 'db_prune' flag which when provided will prune the existing db and start genesis from the provided snapshot metadata file or the local testnet configuration.

  The snapshot metadata file contains paths to the chain config file and files containing chain state items (coins, messages, contracts, contract states, and balances), which are loaded via streaming.

  Each item group in the genesis process is handled by a separate worker, allowing for parallel loading. Workers stream file contents in batches.

  A database transaction is committed every time an item group is succesfully loaded. Resumability is achieved by recording the last loaded group index within the same db tx. If loading is aborted, the remaining workers are shutdown. Upon restart, workers resume from the last processed group.

  Contract States and Balances

  Using uniform-sized batches may result in batches containing items from multiple contracts. Optimal performance can presumably be achieved by selecting a batch size that typically encompasses an entire contract's state or balance, allowing for immediate initialization of relevant Merkle trees.

Removed

• [#1757](https://github.com/FuelLabs/f...

v0.22.4

Version v0.22.4

Added

• #1743: Added blacklisting of the transactions on the TxPool level.

        --tx-blacklist-addresses <TX_BLACKLIST_ADDRESSES>
            The list of banned addresses ignored by the `TxPool`
  
            [env: TX_BLACKLIST_ADDRESSES=]
  
        --tx-blacklist-coins <TX_BLACKLIST_COINS>
            The list of banned coins ignored by the `TxPool`
  
            [env: TX_BLACKLIST_COINS=]
  
        --tx-blacklist-messages <TX_BLACKLIST_MESSAGES>
            The list of banned messages ignored by the `TxPool`
  
            [env: TX_BLACKLIST_MESSAGES=]
  
        --tx-blacklist-contracts <TX_BLACKLIST_CONTRACTS>
            The list of banned contracts ignored by the `TxPool`
  
            [env: TX_BLACKLIST_CONTRACTS=]

What's Changed

• Added blacklisting transaction on the TxPool by @xgreenx in #1743

Full Changelog: v0.22.3...v0.22.4

v0.22.3

What's Changed

• Backport GraphQL clone derives for v0.22 by @Dentosal in #1732

Full Changelog: v0.22.2...v0.22.3

v0.22.2

Version v0.22.2

Added

• #1729: Exposed the schema.sdl file from fuel-core-client. The user can create his own queries by using this file.

What's Changed

• Expose the schema.sdl file by @xgreenx in #1729
• Bump version to 0.22.2 by @xgreenx in #1730

Full Changelog: v0.22.1...v0.22.2