Skip to content

Releases: Emurgo/cardano-serialization-lib

9.0.0

19 Sep 12:37
Compare
Choose a tag to compare

Milestone: https://github.com/Emurgo/cardano-serialization-lib/milestone/3?closed=1

Breaking change: TransactionBuilder.new required two new parameters for max-value-size and max-tx-size (in bytes). It will now use these parameters to not only assert when the tx itself is out of bounds and cannot be built or when an out-of-bounds output is being added, but it also performs a safer change construction, breaking it into multiple outputs in case there are too many native assets.

See this PR for reference: #187

NOTE: maximum transaction and output sizes are protocol parameters that might change!

Current values at the time of this release are:

  1. maxTxSize was defined at the Shelley era = 16384 bytes (see here)
  2. maxValueSize was defined at the Alonzo era = 5000 bytes (see here)

8.1.0

03 Sep 15:07
58efd6f
Compare
Choose a tag to compare

Breaking change

Includes the updated definition of CostModel in the Alonzo binary specification (#193).

Alonzo Release

05 Aug 12:22
0825673
Compare
Choose a tag to compare

New features

Tentative support for the Alonzo hardfork. As the hardfork has not happened yet, we cannot guarantee there will not be other last minute changes requires (it's up to IOHK, not us)

Important notes

  • The TransactionBuilder utility struct does not offer support for any Alonzo features at the moment (actively being worked on)
  • Transactions that don't use any Alonzo-specific functionality (smart contracts) are backwards compatible with Mary (current Cardano version)
  • If you want to know how Alonzo works at the binary-specification level, consider watching this video that explains all the changes

Breaking changes

  • TransactionMetadata rename to AuxiliaryData
  • TransactionWitnessSet.scripts() renamed to .native_scripts()
  • set_metadata renamed to set_auxiliary_data
  • hash_metadata rename to hash_auxiliary_data
  • MetadataHash rename to AuxiliaryDataHash / PoolMetadataHash
  • multiple changes to MoveInstantaneousReward

7.1.0

11 Jun 22:02
Compare
Choose a tag to compare

Chore

  • Bump multiple dependencies (including wasm-bindgen to fix builds on webpack 5)
  • Improve validation for Ipv4 and Ipv6

New features

  • Add TransactionUnspentOutput for Cardano Connector CIP
  • Allow (de)serializing Value type

7.0.0

23 Apr 00:55
Compare
Choose a tag to compare

Breaking Change

  • For NativeScripts, delete the script_hash function (use hash instead`)
  • For NativeScripts, the hash function now takes an argument specifying which script namespace to use for the hash

6.1.0

15 Apr 09:31
Compare
Choose a tag to compare

New features

  • Encryption & decryption utility functions as described by EMIP-3 (useful for encrypting & decrypting private keys according to a user password)
  • Add hash and script_hash functions to the NativeScript type

6.0.0 - Mary support

12 Feb 14:55
Compare
Choose a tag to compare

This release adds support for the Mary hardfork (adds multi-asset transactions)

BREAKING CHANGES:

  • Many places that used to take a regular amount (BigNum) now take a Value which is a combination of BigNum + MultiAsset
  • TransactionBody now contains a mint field
  • TTL is now optional in transactions
  • Ipv4, Ipv6, Url moved to separate network-specific structs with better error checking

New Features:

  • New clamped_sub and compare functions added to BigNum
  • Minimum ADA per UTXO increases when assets are added to a UTXO entry. To calculate the new minimum, you can use min_ada_required

5.0.0-rc.0

11 Dec 06:09
Compare
Choose a tag to compare
5.0.0-rc.0 Pre-release
Pre-release

Support for the Allegra hardfork

Note: transactions created in 4.3.0 will still work (no need to upgrade if you're just creating and broadcasting transactions)

However, this upgrade is needed if either:

  1. You want to use Allegra specific functionality (token locking scripts for on-chain voting)
  2. You want to parse Allegra transactions / blocks from raw bytes (not needed if you're using cardano-db-sync)

4.3.0

16 Nov 19:29
Compare
Choose a tag to compare

Bug fixes

  • Negative integers are now properly serialized when using cbor-based metadata. Any cbor-based transaction metadata generated before this version that used negative numbers will produce the incorrect cbor.

New features

  • Tx metadata validation will now fast-fail when exceeding the per-value limit of 64-bytes for byte arrays and strings

Chore

  • Fixed asm.js builds (Thanks AtomicWallet!)

4.2.0

22 Oct 22:19
Compare
Choose a tag to compare

New features

  • Add from_bech32 and to_bech32 conversion functions on all the hash types.