v4.3.0 release notes

1. New feature. Add logic to support the ibc_plugin automatically push the proxy transactions with relay authority.

v4.2.3 release notes

1. Not charge the hub-transaction fee anymore.

Others:

The docker image: ibc_plugin_bos:ibc-v4.2.3

v4.2.2 release notes

Change

1. Change function ibc_core_checker() to strengthen the logic to avoid stuck the whole process in some situations when handle orig_trxs failed.

Others:

The docker image: ibc_plugin_bos:ibc-v4.2.2

v4.2.1 release notes

1. Change the ibc_core_checker() logic to avoid stuck the whole process in some situations when handling orig_trxs failed.

v4.2.0 release notes

add ibc_plugin and related code based on github.com/boscore/bos:v3.0.8.

v4.1.1 release notes

In ibc_plugin

1. fix a bug in the function get_memo_info(...), enable it to parse memo string correctly.
2. add more information to dump in function ibc_core_checker(...) to facilitate bug trace.

Other

Docker image: boscore/ibc_plugin_bos:ibc-v4.1.1

v4.1.0 release notes

1. Modify structs hub_trx_info definition in ibc_plugin.hpp to maintain consistency with table definition of hub_trx_info in the ibc.token contract

2. Modify structs hub_transfer_params definition in ibc_plugin.hpp and some related logic to complete the transfer of memo string.

Docker Image: boscore/ibc_plugin_bos:ibc-v4.1.0

v4.0.0 release notes

Add programs supporting the IBC hub worker protocol, so that the ibc_plugin can automatically complete the second phase of the IBC hub protocol. For more details, please refer to IBC_Hub_Protocol.md

If you want to disable this feature, add ibc-hub-process-enable=false to the config file.

Docker Image: boscore/ibc_plugin_bos:ibc-v4.0.0

v3.0.0 release notes

Modify according to a new feature of ibc_contracts:v3.0.0, please refer to release notes

Docker Image: boscore/ibc_plugin_bos:ibc-v3.0.0

v2.0.0 release notes

1. Support batch-pbft(BOSCore 3.0 mainnet) and pipeline-bft(EOSIO mainnet) consensus mechanisms.
2. Enhancing the function of ibc.token contract, so that one ibc.token contract can cooperate with many ibc.chain contracts, and users only need to interact with one ibc.token contract to achieve inter-blockchain transfer with multiple side-chains.
3. Delete the dependence on relay account permissions and make IBC system completely decentralized.
4. Supporting multiple relay channels, which enhances the high availability of IBC systems.