Deprecated Testnet Chains

This release deprecates the Rinkeby and Ropsten networks as they are no longer supported. Also included are some dependency security updates as well as some type fixes.

Changelog:

Bump decode-uri-component from 0.2.0 to 0.2.2 #218
Bump json5 from 2.1.2 to 2.2.3 #221
4.6.3-0.0.1 - Update: Deprecate Rinkeby and Ropsten networks #222
4.6.3-0.0.2 - Fix: Incorrect Types #223

Deprecate Chains

This release deprecates the following networks as they are no longer supported by the Blocknative server:

• kovan
• bsc-main
• fantom
• Bitcoin testnet
• Bitcoin main

Changelog:

• 4.6.2-0.0.1: Deprecate Unsupported Chains #215

Optional dappId

This release has changed the types so that when initializing, the dappId is optional if a apiUrl is passed in. The use case for this is when using a WebSocket proxy server, so that the api key does not need to be kept in the client.

Changelog:

• 4.5.0-0.1.0: [feature] - Optional dappId when apiUrl #202

Multi Simulations

This release adds a new multiSim method to the API that allows you to simulate multiple transactions against the next block. It works the same as the simulation method, except that it takes an array of transaction objects that you would like to sim rather than a single object.

Changelog:

• 4.4.1-0.1.0: [feature] - Multi Sim #199

Default Export Fix

This release fixes and issue where the default export of the package did not work due to the mixing of named and default exports. To remedy this, the new multichain sdk API has been added as static method on the regular SDK import.

Changelog:

• 4.4.0-0.0.1: [fix]: Default Export #196

Experimental Multichain API

This release adds an additional name export to the package MultichainSDK that has a different API from the standard SDK. The idea is to provide a nice abstraction around subscribing to transaction events on multiple networks at a time. We will be evolving this API over time, so we may make breaking changes, with the hopes of having an official major release that will make this the default SDK at a future date.

Check out the docs in the README to see how to use it, and please give feedback on the repo!

Changelog:

4.3.0-0.1.0: [feature] - Multichain SDK #192

4.3.0

What's Changed

• Adds support for mumbai testnet, a member of the polygon/matic family. (#185)
• error handling for unsupported chain msg + move simulation error check down (#186 ) (#191)

Full Changelog: 4.2.0...4.3.0

Websocket Simulation Support

This release adds support for websocket simulation transactions.

• Adds a public handler for websocket simulations that returns as a promise
• Added new interfaces: SimulationTransaction and SimulationTransactionOutput
• Added nanoId to match websocket requests

Changelog:

• 4.1.0 - 0.1.0: [feature] - Websocket Simulations (#178)

Fantom Network Support, LocalStorage Enhancement, Updated Typescript BaseEth Transaction Object with GasGwei Values

This release includes new support for Fantom (Opera) Network as well as a few other fixes and enhancements

• Adds Fantom (Opera) Network support (networkId: 250).
• Adds a check for localStorage before checking/saving
• Adds new Type2 Transaction Gas Values to Typescript Interface (as optional):
  • `baseFeePerGasGwei'
  • maxPriorityFeePerGasGwei
  • maxFeePerGasGwei
  • gasPriceGwei

Changelog:

• 4.0.0-0.1.1 - Test whether localStorage is accessible before performing operations (#172)
• 4.0.0-0.1.1 - Add gasGwei values
• 4.0.0-0.1.0 : Add fantom network (#173)

Replacement Transaction Payloads

This is a breaking change to fix replacement transaction payloads to match our Webhook API

Previously if you received a replacement transaction status ('speedup' or 'cancel'), the hash parameter would refer to the new transaction hash and the replaceHash would refer to the original transaction hash that was replaced (flipped the wrong way around!). There rest of the payload would refer to the original transaction. So there was a major mismatch here that needed to be fixed.

The new behavior is that a replacement status is received, and the payload will refer to the original transaction that is being replaced. The hash will match the original hash. The replaceHash parameter now refers to the transaction hash that has replaced the original transaction. This allows for linking the original transaction to the new pending status notification that will be received for that new hash.

Changelog:

• 3.7.1-1.0.0: [fix] - Replacement Transactions (#168)