Releases: boscore/ibc_contracts
v4.6.1 release notes
v4.6.0 release notes
-
New Feature: the contract
ibc.proxymakes the IBC system can transferinline action or deferred transaction.
For detailed info, please refer to README.md -
Add
inline actioncheck to make it fail directly if this action transfer token toibc.tokencontract directly, code is here. -
Add table
rmdunrbs2to allow rollback dead original transactions manually. -
Add action
rbkunrbktrxto roll back the transactions in tablermdunrbs2, which is processed by admin
v4.5.2 release notes
-
Fix a bug. remove function
get_currency_accept_by_orig_contract(), because tableaccepts's primary key is no longer beorig_contract's name. -
Add action
rbkdiehubtrxto rollback dead hub transactions.
v4.5.1 release notes
- Fix a bug in function
ibc_cash_to_hubofibc.tokencontract, code is here, cash_seq_num cannot be used as the ID of tablehubtrxshere, because cash_seq_num grows according to different chains, and its' scope is peer chain name, while the scope of tablehubtrxsis_self,
v4.5.0 release notes
- New feature: allow transfer token to account of the self chain in memo string through
bosibc.iocontract.
v4.4.2 release notes
- Fix a bug in
ibc.chaincontract about the producer schedule calculation when the wtmsig_protocol is activated on the original chain.
Others
Pre-built version: https://github.com/boscore/bos.contract-prebuild/tree/master/bosibc
v4.4.1 release notes
Change
- Fix a memo string parsing bug in function
get_memo_infoof fileibc.token.cpp.
Others
The prebuild version can get here.
v4.4.0 release notes
- Add data structure
producer_authority_scheduleand related logic, to enable theibc.chaincontract can deal with the special situation whenwtmsigprotocol is activated, that is, each block_producer still only uses one key, and the key's weight and threshold are both 1.
v4.3.0 release notes
After resigning the owner and active authority of IBC related contracts to BPs, in order to facilitate the management work, we add admin authority to each contract. Most of the management work can be performed through the admin account, including:
ibc.chain actions:
relay
forceinit
ibc.token actions:
regpeerchain
setchainbool
regacpttoken
setacptasset
setacptstr
setacptint
setacptbool
setacptfee
regpegtoken
regpegtoken2
setpegasset
setpegint
setpegbool
setpegtkfee
unregtoken
fcrollback
fcrmorigtrx
lockall
unlockall
forceinit
setfreeacnt
you can set the admin account by action setadmin(name admin) in each IBC contract.
Others
Pre-build contract: ibc-v4.3.0
v4.2.0 release notes
Let the hub protocol support free-account related logic, to facilitate the inter-chain heartbeat communication.