@substrate/asset-transfer-api
Advanced tools
Changelog
0.1.2(2023-09-26)
NOTE:
In order to use rococo's asset hub with the AssetTransferApi
one will need to hardcode the specName
into the initialization like the following:
new AssetTransferApi(api, `asset-hub-rococo`, xcmVersion);
The reason being, kusama's asset hub and and rococo's asset-hub both share the same specName currently and will cause conflicts. We currently do an overewrite in the registry that the api uses and set the specName
for rococo's asset hub to be asset-hub-rococo
. This is on the horizon to get solved on the actual chain itself soon, so this wont be necessary in the coming future.
Changelog
0.1.1(2023-09-25)
Changelog
0.1.0(2023-09-19)
This release assumes the following is stable, and tested. The api is still not fully featured as we don't have support for certain things which will be listed below. Please review the documentation in the README.md for any information, and feel free to file an issue if anything is unclear.
What is not supported:
What is supported:
Changelog
0.1.0-beta.5(2023-09-13)
Changelog
0.1.0-beta.4(2023-08-30)
Changelog
0.1.0-beta.3(2023-08-21)
Changelog
0.1.0-beta.2(2023-08-09)
Changelog
0.1.0-beta.0(2023-06-16)
AssetsTransferApi.fetchFeeInfo
AssetsTransferApi.regsitry
which exposes a bunch of useful functionality now. Check out the following PR #183paysWithFeeOrigin
as an option for AssetsTransferApi.createTransferTransaction
SystemToPara
SystemToPara
.dest
, and origin
to TxResult<T>
.fetchFeeInfo
to take in call
, and payload
types.NOTE - The API is considered stable for the following direction:
Changelog
0.1.0-alpha.5(2023-06-07)
AssetTransferApi
constructor, and constructApiPromise
createTransferTransaction
inputsdecodeExtrinsic
to AssetsTransferApi
RelayToPara
AssetType explicitly to Foreign