Skip to content

Releases: onflow/flow-go-sdk

v0.41.0

31 May 21:42
b3f967a
Compare
Choose a tag to compare

What's Changed

🛠 Improvements

Other Changes

New Contributors

Full Changelog: v0.40.0...v0.41.0

v0.40.0

04 Apr 17:16
aa03c00
Compare
Choose a tag to compare

What's Changed

Other Changes

Full Changelog: v0.39.0...v0.40.0

v0.39.0

31 Mar 15:47
d064af3
Compare
Choose a tag to compare

What's Changed

🛠 Improvements

Other Changes

Full Changelog: v0.38.0...v0.39.0

v0.38.0

30 Mar 17:21
249a95f
Compare
Choose a tag to compare

🛠 Improvements

📖 Documentation

New Contributors

Full Changelog: v0.37.0...v0.38.0

v0.37.0

23 Mar 15:45
04067d6
Compare
Choose a tag to compare

What's Changed

Other Changes

New Contributors

Full Changelog: v0.36.0...v0.37.0

v0.36.0

13 Mar 17:53
cbf7014
Compare
Choose a tag to compare

💥 Breaking Changes

Update Crypto version

by @tarakby in #353

The Flow Go-SDK crypto package is based on the github.com/onflow/flow-go/crypto package. In particular, ECDSA key generation (the keys supported by Flow accounts) is a wrapper around the flow-go/crypto key generation. The underlying package used to implement a very simple deterministic key generation for ECDSA that maps any input seed to a private key using a simple modular reduction.
This requires the seed to not only have enough entropy, but to also have its entropy uniformly distributed across all the bits. This is true for a seed that is sampled using a secure RNG. To be safer with low-quality input seeds, the Flow-Go-SDK/crypto used to hash the input seeds to guarantee uniform distribution before invoking flow-go/crypto.

The flow-go/crypto package recently updated its key generation process to a more robust one that requires less constraints from the input seed (onflow/flow-go#3788). The entropy is now extracted from the input seed and then expanded into the required data thanks to a Key derivation Function (KDF). This change means that the flow-go-sdk/crypto no longer needs to implement the safety hashing and can simply invoke the more secure generation from flow-go/crypto. Although the key generation process is still deterministic, the new process maps seeds to different private keys than it used to in the previous version.

If you would like to preserve the private keys you used to find with the previous SDK version, it is always possible to use the method Encode on your private keys. This is an alternative way to storing the seeds. Encode is already implemented in the previous versions and returns a serialization of the private key. Calling DecodePrivateKey on the serialization gets you back to the original key, regardless of the SDK version used.
Remember that dealing with seeds or private keys of sensitive assets requires using a safe environment like a secure hardware. flow-go-sdk is a pure software implementation that should not be used for sensitive keys.

Full Changelog: v0.35.0...v0.36.0

v0.35.0

08 Mar 19:28
94bfe0c
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.34.0...v0.35.0

v0.34.0

27 Feb 18:09
a0f0fc4
Compare
Choose a tag to compare

What's Changed

⭐ Features

🛠 Improvements

📖 Documentation

New Contributors

Full Changelog: v0.33.0...v0.34.0

v0.33.0

20 Feb 15:15
2b0b443
Compare
Choose a tag to compare

What's Changed

🛠 Improvements

Other Changes

New Contributors

Full Changelog: v0.32.0...v0.33.0

v0.32.0

16 Feb 21:16
9f5d740
Compare
Choose a tag to compare

What's Changed

📖 Documentation

Other Changes

  • Auto update to onflow/cadence v0.34.0 by @SupunS in #343

New Contributors

Full Changelog: v0.31.3...v0.32.0