Skip to content

Releases: axelarnetwork/interchain-token-service

v2.0.1

18 Nov 18:36
a7439cd
Compare
Choose a tag to compare

Patch Changes

v2.0.0

18 Nov 18:40
9d9a515
Compare
Choose a tag to compare

Major Changes

  • 1426b15: Add ITS Hub support to EVM ITS contract

Minor Changes

  • 2da5b3a: ITS deployInterchainToken is restricted from being on ITS on Amplifier chains. The ITS Factory should be used instead
  • 38698a2: Remove support for deploying token manager to chains connected via ITS Hub. When deploying ITS to an EVM chain connected via Amplifier / ITS Hub, a trusted address must be set for it's own chain name to the 'hub' identifier, to prevent deploying the token manager locally. Note that this restriction is temporary. Once the ITS Hub adds support for deploy token manager msg type, the restriction will be removed. Also note that the token manager deployed as part of registering a canonical ITS token from the ITS Factory is not affected by this.

v1.2.4

25 Mar 06:38
Compare
Choose a tag to compare

Changelog

This patch release introduces a change to custom token deployment to distinguish them from native interchain tokens deployed by ITS.

  • Custom tokens using mint/burn will now have to use the updated MINT_BURN token manager type (i.e 4 enum value).
  • Custom tokens using MINT_BURN or MINT_BURN_FROM token manager types will need to give mint permission to the corresponding token manager contract instead of ITS. The token manager address corresponding to a tokenId can be predicted via the tokenManagerAddress query and tokenId can be computed via this query.
  • Native interchain tokens deployed by ITS will use the NATIVE_INTERCHAIN_TOKEN token manager type (i.e 0 enum value).
  • deployTokenManager will now revert if 0 token manager type is provided. All other token manager types will work as expected.
  • Existing custom tokens deployed with 0 token manager type will still work as expected. Although, when deploying the same token on a new chain, the new 4 (MINT_BURN) token manager type will need to be used, along with giving mint permission to the token manager (token manager address can be predicted via this query).

What's Changed

  • feat: added new token managers that have the mint/burn permissions by @Foivos in 023083e

Full Changelog: v1.2.1...v1.2.4

v1.2.1

18 Dec 00:03
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.2.0...v1.2.1

v1.2.0

15 Dec 21:05
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.1.0...v1.2.0

v1.1.0

15 Dec 18:23
Compare
Choose a tag to compare

Changelog

  • Added missing IUpgradable interface in IInterchainTokenService for completeness
  • Bumped cgp and gmp-sdk deps
  • Various test improvements

What's Changed

Full Changelog: v1.0.0...v1.1.0

v1.0.0

06 Dec 20:47
Compare
Choose a tag to compare

CHANGELOG

The major changes in this stable release compared to the beta release are:

  • Tokens can be transferred directly via the ITS contract instead of TokenManagers, i.e provide the ERC20 approval (not needed for mint/burn tokens) to the ITS contract instead of the TokenManager.
  • Separate TokenManager implementations have been consolidated into a TokenHandler contract. This doesn't affect the API.
  • interchainTransfer now takes a gasValue param. This allows it to be used within a multicall (for e.g. transfer tokens to multiple chains in one tx).
  • InterchainTransfer event has a new dataHash field. This is set to keccak256(data) if a destination contract is being called with the transfer, and bytes32(0) otherwise. InterchainTransferWithData event type was removed as a result.
  • InterchainTokenExecutable.executeWithInterchainToken now takes commandId as well to allow apps to track individual messages. Similar change for the express executable.
  • Distributable has been renamed to Minter for clarity. You can call transferMintership to transfer mint rights to a token.
  • Removed support for deploy + transfer to remote chains in InterchainTokenFactory to reduce complexity. InterchainTokenFactory.deployInterchainToken will now mint the initial supply directly to the sender/deployer address. There is no need to transfer tokens from the factory to the sender anymore.
  • Renamed BaseInterchainToken to InterchainTokenStandard, and removed the coupling with an ERC20 implementation. Custom interchain tokens can now inherit InterchainTokenStandard directly to benefit from interchain transfer support.
  • Switch to using a minimal proxy for InterchainToken deployments to reduce gas usage significantly and support auto-proxy verification on explorers.
  • Passing bytes4(uint32(1)) as the metadata version will pay for an express call on the gas service. This is relevant for an express relayer.
  • Misc bug fixes, test coverage, and improvements.

What's Changed

Full Changelog: v1.0.0-beta.4...v1.0.0

v1.0.0-beta.4

04 Dec 10:33
Compare
Choose a tag to compare
v1.0.0-beta.4 Pre-release
Pre-release

What's Changed

Full Changelog: v1.0.0-beta.3...v1.0.0-beta.4

v1.0.0-beta.3

15 Nov 00:55
Compare
Choose a tag to compare
v1.0.0-beta.3 Pre-release
Pre-release

What's Changed

Full Changelog: v1.0.0-beta.2...v1.0.0-beta.3

v1.0.0-beta.2

07 Nov 04:10
Compare
Choose a tag to compare
v1.0.0-beta.2 Pre-release
Pre-release

What's Changed

New Contributors

Full Changelog: v1.0.0-beta.1...v1.0.0-beta.2