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

v0.23.0

Version v0.23.0

Added

• #1713: Added automatic impl of traits StorageWrite and StorageRead for StructuredStorage. Tables that use a Blueprint can be read and written using these interfaces provided by structured storage types.
• #1671: Added a new Merklized blueprint that maintains the binary Merkle tree over the storage data. It supports only the insertion of the objects without removing them.
• #1657: Moved ContractsInfo table from fuel-vm to on-chain tables, and created version-able ContractsInfoType to act as the table's data type.

Changed

• #1723: Notify about imported blocks from the off-chain worker.
• #1717: The fix for the #1657 to include the contract into ContractsInfo table.
• #1657: Upgrade to fuel-vm 0.46.0.
• #1671: The logic related to the FuelBlockIdsToHeights is moved to the off-chain worker.
• #1663: Reduce the punishment criteria for mempool gossipping.
• #1658: Removed Receipts table. Instead, receipts are part of the TransactionStatuses table.
• #1640: Upgrade to fuel-vm 0.45.0.
• #1635: Move updating of the owned messages and coins to off-chain worker.
• #1650: Add api endpoint for getting estimates for future gas prices
• #1649: Add api endpoint for getting latest gas price
• #1600: Upgrade to fuel-vm 0.45.0
• #1633: Notify services about importing of the genesis block.
• #1625: Making relayer independent from the executor and preparation for the force transaction inclusion.
• #1613: Add api endpoint to retrieve a message by its nonce.
• #1612: Use AtomicView in all services for consistent results.
• #1597: Unify namespacing for libp2p modules
• #1591: Simplify libp2p dependencies and not depend on all sub modules directly.
• #1590: Use AtomicView in the TxPool to read the state of the database during insertion of the transactions.
• #1587: Use BlockHeight as a primary key for the FuelsBlock table.
• #1585: Let NetworkBehaviour macro generate FuelBehaviorEvent in p2p
• #1579: The change extracts the off-chain-related logic from the executor and moves it to the GraphQL off-chain worker. It creates two new concepts - Off-chain and On-chain databases where the GraphQL worker has exclusive ownership of the database and may modify it without intersecting with the On-chain database.
• #1577: Moved insertion of sealed blocks into the BlockImporter instead of the executor.
• #1574: Penalizes peers for sending invalid responses or for not replying at all.
• #1601: Fix formatting in docs and check that cargo doc passes in the CI.
• #1636: Add more docs to GraphQL DAP API.

Breaking

• #1725: All API endpoints now are prefixed with /v1 version. New usage looks like: /v1/playground, /v1/graphql, /v1/graphql-sub, /v1/metrics, /v1/health.

• #1722: Bugfix: Zero predicate_gas_used field during validation of the produced block.

• #1714: The change bumps the fuel-vm to 0.47.1. It breaks several breaking changes into the protocol:

  • All malleable fields are zero during the execution and unavailable through the GTF getters. Accessing them via the memory directly is still possible, but they are zero.
  • The Transaction doesn't define the gas price anymore. The gas price is defined by the block producer and recorded in the Mint transaction at the end of the block. A price of future blocks can be fetched through a new API nedopoint and the price of the last block can be fetch or via the block or another API endpoint.
  • The GasPrice policy is replaced with the Tip policy. The user may specify in the native tokens how much he wants to pay the block producer to include his transaction in the block. It is the prioritization mechanism to incentivize the block producer to include users transactions earlier.
  • The MaxFee policy is mandatory to set. Without it, the transaction pool will reject the transaction. Since the block producer defines the gas price, the only way to control how much user agreed to pay can be done only through this policy.
  • The maturity field is removed from the Input::Coin. The same affect can be achieve with the Maturity policy on the transaction and predicate. This changes breaks how input coin is created and removes the passing of this argument.
  • The metadata of the Checked<Tx> doesn't contain max_fee and min_fee anymore. Only max_gas and min_gas. The max_fee is controlled by the user via the MaxFee policy.
  • Added automatic impl of traits StorageWrite and StorageRead for StructuredStorage. Tables that use a Blueprint can be read and written using these interfaces provided by structured storage types.

• #1712: Make ContractUtxoInfo type a version-able enum for use in the ContractsLatestUtxotable.

• #1657: Changed CROO gas price type from Word to DependentGasPrice. The dependent gas price values are dummy values while awaiting updated benchmarks.

• #1671: The GraphQL API uses block height instead of the block id where it is possible. The transaction status contains block_height instead of the block_id.

• #1675: Simplify GQL schema by disabling contract resolvers in most cases, and just return a ContractId scalar instead.

• #1658: Receipts are part of the transaction status.
  Removed reason from the TransactionExecutionResult::Failed. It can be calculated based on the program state and receipts.
  Also, it is not possible to fetch receipts from the Transaction directly anymore. Instead, you need to fetch status and its receipts.

• #1646: Remove redundant receipts from queries.

• #1639: Make Merkle metadata, i.e. SparseMerkleMetadata and DenseMerkleMetadata type version-able enums

• #1632: Make Message type a version-able enum

• #1631: Modify api endpoint to dry run multiple transactions.

• #1629: Use a separate database for each data domain. Each database has its own folder where data is stored.

• #1628: Make CompressedCoin type a version-able enum

• #1616: Make BlockHeader type a version-able enum

• #1614: Use the default consensus key regardless of trigger mode. The change is breaking because it removes the --dev-keys argument. If the debug flag is set, the default consensus key will be used, regardless of the trigger mode.

• #1596: Make Consensus type a version-able enum

• #1593: Make Block type a version-able enum

• #1576: The change moves the implementation of the storage traits for required tables from fuel-core to fuel-core-storage crate. The change also adds a more flexible configuration of the encoding/decoding per the table and allows the implementation of specific behaviors for the table in a much easier way. It unifies the encoding between database, SMTs, and iteration, preventing mismatching bytes representation on the Rust type system level. Plus, it increases the re-usage of the code by applying the same blueprint to other tables.

  It is a breaking PR because it changes database encoding/decoding for some tables.

  StructuredStorage

  The change adds a new type StructuredStorage. It is a wrapper around the key-value storage that implements the storage traits(StorageInspect, StorageMutate, StorageRead, etc) for the tables with blueprint. This blueprint works in tandem with the TableWithBlueprint trait. The table may implement TableWithBlueprint specifying the blueprint, as...

v0.22.1

Version v0.22.1

Fixed

• #1664: Fixed long database initialization after restart of the node by setting limit to the WAL file.

What's Changed

• Fix for the long database initialization after restart by @xgreenx in #1664

Full Changelog: v0.22.0...v0.22.1

v0.22.0

This release contains largely internal breaking changes to adjust our database layout of SMT's and a new API to view the status of connected peers. The only major breaking external change is that the peer_count field on the ChainInfo query resolver was removed and migrated to NodeInfo.

[Version 0.22.0]

Added

• #1515: Added support of --version command for fuel-core-keygen binary.
• #1504: A Success or Failure variant of TransactionStatus returned by a query now contains the associated receipts generated by transaction execution.

Breaking

• #1531: Make fuel-core-executor no_std compatible. It affects the fuel-core crate because it uses the fuel-core-executor crate. The change is breaking because of moved types.
• #1524: Adds information about connected peers to the GQL API.

Changed

• #1517: Changed default gossip heartbeat interval to 500ms.
• #1520: Extract executor into fuel-core-executor crate.

Fixed

Breaking

• #1536: The change fixes the contracts tables to not touch SMT nodes of foreign contracts. Before, it was possible to invalidate the SMT from another contract. It is a breaking change and requires re-calculating the whole state from the beginning with new SMT roots.
• #1542: Migrates information about peers to NodeInfo instead of ChainInfo. It also elides information about peers in the default node_info query.

New Contributors

• @lukema95 made their first contribution in #1526

Full Changelog: v0.21.0...v0.22.0

v0.21.0

Version 0.21.0

This release focuses on preparing fuel-core for the mainnet environment:

• Most of the changes improved the security and stability of the node.
• The gas model was reworked to cover all aspects of execution.
• The benchmarking system was significantly enhanced, covering worst scenarios.
• A new set of benchmarks was added to track the accuracy of gas prices.
• Optimized heavy operations and removed/replaced exploitable functionality.

Besides that, there are more concrete changes:

• Unified naming conventions for all CLI arguments. Added dependencies between related fields to avoid misconfiguration in case of missing arguments. Added --debug flag that enables additional functionality like a debugger.
• Improved telemetry to cover the internal work of services and added support for the Pyroscope, allowing it to generate real-time flamegraphs to track performance.
• Improved stability of the P2P layer and adjusted the updating of reputation. The speed of block synchronization was significantly increased.
• The node is more stable and resilient. Improved DoS resistance and resource management. Fixed critical bugs during state transition.
• Reworked the Mint transaction to accumulate the fee from block production inside the contract defined by the block producer.

FuelVM received a lot of safety and stability improvements:

• The audit helped identify some bugs and errors that have been successfully fixed.
• Updated the gas price model to charge for resources used during the transaction lifecycle.
• Added no_std and 32 bit system support. This opens doors for fraud proving in the future.
• Removed the ChainId from the PredicateId calculation, allowing the use of predicates cross-chain.
• Improvements in the performance of some storage-related opcodes.
• Support the ECAL instruction that allows adding custom functionality to the VM. It can be used to create unique rollups or advanced indexers in the future.
• Support of transaction policies provides additional safety for the user.
  It also allows the implementation of a multi-dimensional price model in the future, making the transaction execution cheaper and allowing more transactions that don't affect storage.
• Refactored errors, returning more detailed errors to the user, simplifying debugging.

Added

• #1503: Add gtf opcode sanity check.
• #1502: Added price benchmark for vm_initialization.
• #1501: Add a CLI command for generating a fee collection contract.
• #1492: Support backward iteration in the RocksDB. It allows backward queries that were not allowed before.
• #1490: Add push and pop benchmarks.
• #1485: Prepare rc release of fuel core v0.21
• #1476: Add the majority of the "other" benchmarks for contract opcodes.
• #1473: Expose fuel-core version as a constant
• #1469: Added support of bloom filter for RocksDB tables and increased the block cache.
• #1465: Improvements for keygen cli and crates
• #1642: Added benchmark to measure the performance of contract state and contract ID calculation; use for gas costing.
• #1457: Fixing incorrect measurement for fast(µs) opcodes.
• #1456: Added flushing of the RocksDB during a graceful shutdown.
• #1456: Added more logs to track the service lifecycle.
• #1453: Add the majority of the "sanity" benchmarks for contract opcodes.
• #1452: Added benchmark to measure the performance of contract root calculation when utilizing the maximum contract size; used for gas costing of contract root during predicate owner validation.
• #1449: Fix coin pagination in e2e test client.
• #1447: Add timeout for continuous e2e tests
• #1444: Add "sanity" benchmarks for memory opcodes.
• #1437: Add some transaction throughput tests for basic transfers.
• #1436: Add a github action to continuously test beta-4.
• #1433: Add "sanity" benchmarks for flow opcodes.
• #1432: Add a new --api-request-timeout argument to control TTL for GraphQL requests.
• #1430: Add "sanity" benchmarks for crypto opcodes.
• #1426 Split keygen into a create and a binary.
• #1419: Add additional "sanity" benchmarks for arithmetic op code instructions.
• #1411: Added WASM and no_std compatibility.
• #1405: Use correct names for service metrics.
• #1400: Add releasy beta to fuel-core so that new commits to fuel-core master triggers fuels-rs.
• #1371: Add new client function for querying the MessageStatus for a specific message (by Nonce).
• #1356: Add peer reputation reporting to heartbeat code.
• #1355: Added new metrics related to block importing, such as tps, sync delays etc.
• #1339: Adds baseAssetId to FeeParameters in the GraphQL API.
• #1331: Add peer reputation reporting to block import code.
• #1324: Added pyroscope profiling to fuel-core, intended to be used by a secondary docker image that has debug symbols enabled.
• #1309: Add documentation for running debug builds with CLion and Visual Studio Code.
• #1308: Add support for loading .env files when compiling with the env feature. This allows users to conveniently supply CLI arguments in a secure and IDE-agnostic way.
• #1304: Implemented submit_and_await_commit_with_receipts method for FuelClient.
• #1286: Include readable names for test cases where missing.
• #1274: Added tests to benchmark block synchronization.
• #1263: Add gas benchmarks for ED19 and ECR1 instructions.

Changed

• #1512: Internally simplify merkle_contract_state_range.
• #1507: Updated chain configuration to be ready for beta 5 network. It includes opcode prices from the latest benchmark and contract for the block producer.
• #1477: Upgraded the Rust version used in CI and containers to 1.73.0. Also includes associated Clippy changes.
• #1469: Replaced usage of MemoryTransactionView by Checkpoint database in the benchmarks.
• #1468: Bumped version of the fuel-vm to v0.40.0. It brings some breaking changes into consensus parameters API because of changes in the underlying types.
• #1466: Handling overflows during arithmetic operations.
• #1460: Change tracking branch from main to master for releasy tests.
• #1454: Update gas benchmarks for opcodes that append receipts.
• #1440: Don't report reserved nodes that send invalid transactions.
• #1439: Reduced memory BMT consumption during creation of the header.
• #1434: Continue gossiping transactions to reserved peers regardless of gossiping reputation score.
• #1408: Update gas benchmarks for storage opcodes to use a pre-populated database to get more accurate worst-case costs.
• #1399: The Relayer now queries Ethereum for its latest finalized block instead of using a configurable "finalization period" to presume finality.
• #1397: Improved keygen. Created a crate to be included from forc plugins and upgraded internal library to drop requirement of protoc to build
• #1395: Add DependentCost benchmarks for k256, s256 and mcpi instructions.
• #1393: Increase heartbeat timeout from 2 t...