Skip to content
This repository was archived by the owner on Dec 20, 2024. It is now read-only.

Releases: quantnetwork/overledger-sdk-javascript-v2

v2.4.1

31 Mar 14:08
a848ddf
Compare
Choose a tag to compare

Version 2.4.1 of the Overledger JavaScript SDK.

This version:

  • updated the SDK to use the latest web3 and substrate libraries.
  • updated the SDK to use the latest version of Lerna.
  • updated the SDK to remove some unused dependencies.

v2.4.0

28 Mar 13:08
4796882
Compare
Choose a tag to compare

Version 2.4.0 of the Overledger JavaScript SDK.

This version upgrades our SDK to be compatible with Overledger's new multi-factor authentication system.

v2.3.0

13 May 09:14
89cca48
Compare
Choose a tag to compare

Version 2.3.0 of the Overledger JavaScript SDK.

This version is a minor release to include support for Bitcoin SegWit transactions.

v2.2.1

07 Apr 00:12
f8dcd97
Compare
Choose a tag to compare

Version 2.2.1 of the Overledger JavaScript SDK.

This version is a patch release to include all of the required Substrate DLT dependencies.

v2.2.0

05 Apr 14:10
de72bc8
Compare
Choose a tag to compare

Version 2.2.0 of the Overledger JavaScript SDK.

This version now supports account creation and transaction signing for Substrate DLT networks.

v2.1.1

28 Oct 10:28
cfa652e
Compare
Choose a tag to compare

Version 2.1.1 of the Overledger JavaScript SDK.

This version has upgraded package dependencies, and added unit & integration tests for all examples which are now checked on any pull request or push via automated github actions.

v2.1.0

11 Oct 16:14
Compare
Choose a tag to compare

Version 2.1.0 of the Overledger JavaScript SDK.

This version has improved transaction signing. For Ethereum transaction signing, EIP1559 transactions are now supported. For Bitcoin transaction signing, we now use the psbt library.

v2.0.0

27 Apr 15:06
22bba62
Compare
Choose a tag to compare

Version 2.0.0 of the Overledger JavaScript SDK is a lightweight iteration over the previous versions.

This version allows users to get Overledger access tokens and then sign their transactions offline. Using the access tokens, developers can choose any JavaScript HTTP client they like to call the Overledger Preparation API. Using the response, they can sign their transactions and then submit them to the Overledger Execution API.