Release v3.0.0-alpha.6

This is includes some breaking changes from v3.0.0-alpha.4, including:

• Chain classes (Bitcoin, Ethereum, etc.) parameters should be passed in as an object instead of individually, to avoid confusion with how providers and signers are passed in:

Bitcoin(network) ---> Bitcoin({network})
Ethereum(network, {signer, provider}) ---> Ethereum({network, signer, provider})

• The status field on gateway transactions has been removed in favor of checking the statuses of each transaction directly. Switching on tx.status should now instead check tx.in.status, tx.renVM.status and tx.out.status. This change is to push the concept that a gateway transaction is just a bundle of chain transactions (including the RenVM transaction), and because the number of states needing to be enumerated grew too large.

• The status field and event name on TxWaiter and TxSubmitter has been renamed to progress, to avoid confusion between the state of the transaction and its status enum.

• The fee object returns from gateway.fees or renJS.getFees now includes a single variableFee field that replaces the mint and burn fields, and a single fixedFee that replaces the lock and release fields.

Release v2.5.11

• The polygon RPC has been updated to https://polygon-rpc.com/
• A bug in BCH address validation has been fixed

Release v2.5.10

Changelog:

• Fix Avalanche mainnet chain ID (#181, acabb40)
• Fix decoding a subset of bech32 Bitcoin addresses (#181, f396c3f)

v2.5.6

Changelog:

• Fix Solana handler not being able to get associated token account immediately after creating it
• Update mock provider to support ren_queryBlockState endpoint
• Fix filecoin fallback to filfox if lotus is unavailable

v2.5.5

Changelog:

• Add retry logic for Solana transaction simulations
• Fix calculating number of confirmations required for burns

v2.5.4

Changelog:

• Use queryBlockState instead of queryState
  The RenVM JSON-RPC method queryState is now deprecated, and queryBlockState should be used instead.

v2.5.2

Changelog:

• Set a timeout for waiting for Solana confirmations to finalize
• Filecoin fix for fetching deposits

v2.5.1

Changelog:

• Allow minting to a Solana address that isn't in the connected wallet
• The Solana class no longer decodes addresses for burn recipients
• Fix looking up the submission status of Arbitrum mints

v2.5.0

Changelog:

• Initial Arbitrum support
• Goerli support
• Replace Web3 with Ethers.js
• Add MockProvider for testing contracts locally

The Ethereum class can now be initialized with a standard Web3 provider, or by providing an ethers provider as { provider, signer }.

Note - methods that previously returned Web3 promievents still return promievents, but the supported events are now "transactionHash" and "confirmation" - the latter returning the number of confirmations and the target confirmations, rather than a receipt.

v2.4.7

Changelog:

• Temporary fix for Filecoin decimals on Solana (#156)
• Fix checking if Filecoin should point to testnet (#155)