Skip to content

Releases: onflow/flow-go

v0.19.2 - Mainnet 11

19 Jul 23:36
2644560
Compare
Choose a tag to compare

Mainnet 11

  1. Verifiable Events
  2. Sealing & Verification: various minor improvements and code cleanups
  3. Minor Crypto Upgrades (Relic)

Verifiable events

  • Test execution matches verification + fix wrong transaction index for verified events [Verifiable events part 5] (#869) @m4ksio
  • Compute event hashes in separate thread [Verifiable events part 4] (#868) @m4ksio
  • Verify service events [Verifiable events part 3] (#804) @m4ksio
  • Verify events hash [Verifiable events part 2] (#739) @m4ksio
  • Hash events collection [Verifiable events part 1] (#734) @m4ksio

🛠 Improvements

🐞 Bug Fixes

Misc

Mainnet 10 - v0.18.4

19 Jun 21:39
Compare
Choose a tag to compare
Mainnet 10 - v0.18.4 Pre-release
Pre-release

⭐ Features

Improved and updated the Sealing and Verification logic to more fully involve the Verification nodes in the Sealing process

🛠 Improvements

Cadence Updates

Crypto Updates

Metrics and Monitoring

  • [Verification] Logging block height on chunk processing pipeline (#856) @yhassanzadeh13
  • [Execution] Expose more execution/fvm metrics (#813) @ramtinms
  • [Networking] Adding logging around libp2p one-to-one stream management (#785) @vishalchangrani
  • [Collection] Add Metric to Track Greatest Epoch Final View (#698) @danuio

General Improvments

🐞 Bug Fixes

Misc.

Mainnet 9 - v0.17.4

26 May 01:46
2d81520
Compare
Choose a tag to compare

Changes since v0.16.2

⭐ Features

🛠 Improvements

🐛 Bug Fixes

❓ Miscellaneous

Breaking changes

Proposer Key Sequence Number (#602)

When running a transaction, the proposer key sequence number would always be incremented unless any of the following conditions occur:

  • invalid transaction (transaction rejected by collection nodes)
  • any of the transaction signatures are not valid
  • the transaction is missing the signature(s) by the proposer
  • the proposal sequence number is invalid (not match with the one stored on the chain)

In other words, the new behaviour increments the sequence number even if the transaction fails at runtime or any other condition that is not mentioned above. The new behaviour protects the network against some cases of spamming attacks and protects users from double transaction submission attacks.

Transaction Domain Tags (#694)

Transaction domain tags allow signers to identify which messages are intended to represent encoded transactions, and which are not. The Flow protocol has been updated (as of May 5th 2021) to both accept signatures produced from messages prepended with a transaction domain tag, and from messages that are not. This spork will strictly require all signatures for transactions to have been produced from messages prepended with a transaction domain tag.

This breaking change requires all users of Flow Client Library, the Flow JavaScript SDK and Flow Go SDK to update their versions to a version greater than or equal to the version that supports transaction domain tags.

FlowIDTableStaking Smart Contract Breaking Change

This change refactors certain functions to eliminate excessive gas usage and is a part of preparing the contract for new protocol contracts like FlowEpoch and StakingCollection and making the contract more efficient

BREAKING CHANGE: Consolidating node and delegator metadata into a single struct to make querying staking information more straightforward.

These changes do not affect any transactions or active interactions with the Staking contract
You only need to take action if you are using any fo the following:

Cadence: Signature Algorithm Name Update (#710)

The naming of the ECDSA secp256k1 signature algorithm was not consistent across different codebases.

To main change is to replace SignatureAlgorithm.ECDSA_Secp256k1 with SignatureAlgorithm.ECDSA_secp256k1

Devnet 23 - v0.17.3

19 May 00:22
fef8381
Compare
Choose a tag to compare
Devnet 23 - v0.17.3 Pre-release
Pre-release

Changes since v0.16.2

⭐ Features

🛠 Improvements

🐛 Bug Fixes

❓ Miscellaneous

Breaking changes

Proposer Key Sequence Number (#602)

When running a transaction, the proposer key sequence number would always be incremented unless any of the following conditions occur:

  • invalid transaction (transaction rejected by collection nodes)
  • any of the transaction signatures are not valid
  • the transaction is missing the signature(s) by the proposer
  • the proposal sequence number is invalid (not match with the one stored on the chain)

In other words, the new behaviour increments the sequence number even if the transaction fails at runtime or any other condition that is not mentioned above. The new behaviour protects the network against some cases of spamming attacks and protects users from double transaction submission attacks.

Transaction Domain Tags (#694)

Transaction domain tags allow signers to identify which messages are intended to represent encoded transactions, and which are not. The Flow protocol has been updated (as of May 5th 2021) to both accept signatures produced from messages prepended with a transaction domain tag, and from messages that are not. This spork will strictly require all signatures for transactions to have been produced from messages prepended with a transaction domain tag.

This breaking change requires all users of Flow Client Library, the Flow JavaScript SDK and Flow Go SDK to update their versions to a version greater than or equal to the version that supports transaction domain tags.

FlowIDTableStaking Smart Contract Breaking Change

This change refactors certain functions to eliminate excessive gas usage and is a part of preparing the contract for new protocol contracts like FlowEpoch and StakingCollection and making the contract more efficient

BREAKING CHANGE: Consolidating node and delegator metadata into a single struct to make querying staking information more straightforward.

These changes do not affect any transactions or active interactions with the Staking contract
You only need to take action if you are using any fo the following:

Cadence: Signature Algorithm Name Update (#710)

The naming of the ECDSA secp256k1 signature algorithm was not consistent across different codebases.

To main change is to replace SignatureAlgorithm.ECDSA_Secp256k1 with SignatureAlgorithm.ECDSA_secp256k1

Mainnet 8 Patch

27 Apr 03:49
4e733ba
Compare
Choose a tag to compare

Mainnet 8 Patch

  • Fixes various state migration issues

See the rest of the release notes here

v0.16.1 - Mainnet 8 Spork

23 Apr 04:08
5f9db61
Compare
Choose a tag to compare

Mainnet 8 - Spork

April 28th, 2021

State Migrations

There will be an update to the Cadence storage format, requiring a migration of all trie values. This affect the state commitment hash.

Change Log since v0.16.0

Note that Mainnet 8 will include all changes in v0.16.0 as well.

⭐ Features

🛠 Improvements

🐛 Bug Fixes

  • [FVM] capture events of meta transactions (#641) @ramtinms
  • [Exec] Update sequence number independent of transaction invocation result (#602) @ramtinms

❓ Miscellaneous

  • Backport account freezing test (#651) @m4ksio
  • Increase default distance between ledger checkpoints (#640) @ramtinms
  • Backport of CHDP cache and cache resource name requirement (#622) @m4ksio
  • Bootstrapping Generates Root Snapshot File (#424) @danuio
  • Update bootstrap MVP integration test (#619) @jordanschalm
  • Fixed Docker volume permissions issue with SELinux (#393) @awfm9

v0.16.0 - Canary 3 Spork

14 Apr 17:06
438f333
Compare
Choose a tag to compare
Pre-release

🛠 Improvements

  • [Ledger] complete memory trie optimization (#505) @tarakby

🐞 Bug Fixes

v0.15.4

05 Apr 19:03
a9b3abf
Compare
Choose a tag to compare
v0.15.4 Pre-release
Pre-release

🛠 Improvements

  • [Crypto] improve BLS compression settings in the lib (#457) @tarakby
  • Convert Transit CLI to spf13/cobra (#553) @danuio
  • [Crypto] optimize public key aggregation to verify a QC (#445) @tarakby
  • [Crypto] use BLS multi-sig to create and verify QCs (#580) @tarakby

v0.15.3 - Mainnet 7 - April 7 Spork

29 Mar 20:09
b71dec4
Compare
Choose a tag to compare

Mainnet 7 - Spork

April 7th, 2021

State Migrations

There will be an update for all accounts to get the minimum balance required for storage fees

Improvements

This Spork will be updating the Mainnet from v0.14.9 to v0.15.3

The main items being added are:

Bug fixes

  • Fix more script execution crashes
  • Crypto.ECDSA_Secp256k1 fix

Logging, monitoring and tracing improvements

  • More improvements to tracing of the FVM

Performance related improvements

  • Cadence interpreter optimizations
  • Cadence contract value lazy loading
  • TransactionResult and Event caching

New Features

  • Enable storage limit
  • Support Account Freezing
  • Add block ID to TransactionResult response

Changes since v0.14.9

v0.15.0

v0.15.1

v0.15.2

v0.15.3

v0.15.2

26 Mar 21:41
47fade3
Compare
Choose a tag to compare
v0.15.2 Pre-release
Pre-release
  • Update Cadence to v0.14.4 (#574) @Kay-Zee
  • [FVM] Patch for program cache to support contract upgrades (#572) @ramtinms
  • Validate collection guarantees based on reference block (#502) @jordanschalm
  • access node: passing a list of fixed execution node ids to choose from (#560) @vishalchangrani
  • [FVM] Updating program cache handler to always clean up state stack (#567) @ramtinms