v0.46.0
LBM SDK v0.46.0 Release Notes
In this version, the proto path defined separately in lbm-sdk is aligned with the path of cosmos-sdk, and the signature specification and address method are also modified to be the same as that of cosmos-sdk. So, we made it possible to use several products of the cosmos ecosystem, including cosmjs, without modification.
And the features that were added self-control kept the proto path of lbm-sdk.
This version based on cosmos-sdk v0.45.10, wasmd v0.27.0 and Ostracon v1.0.7.
New module: x/foundation
x/foundation's authority is a module account associated with the foundation and a decision policy. It is an "administrator" which has the ability to add, remove and update members in the foundation. x/foundation has several messages which cannot be triggered but by the authority. It includes membership management messages, and other messages which controls the assets of the foundation.
Note: The authority is a module account, which means no one has the private key of the authority. Hence, foundation members MUST propose, vote and execute the corresponding proposal.
For more details about x/foundation
, please refer to the SDK document
State-Breaking Changes
- Changed Ostracon VRF library from r2ishiguro to libsodium (r2ishiguro and libsodium vrf results are not compatible, chain reset required)
- add
x/foundation
module - upgrade wasmd to v0.27
- apply Ostracon's changes that replace
StakingPower
withVotingPower
andStakingPower
withVotingPower
API-Breaking Changes
- All protos identical to cosmos-sdk have their proto paths changed from lbm-sdk to cosmos.
- change
x/token
andx/collection
apis - Separate APIs unique to cosmos-sdk and lbm-sdk
- remove unused MsgEmpty
- add index field into TxResponse
Improvements
- Upgrade IBC module from v1.0.0 to v3.0.0
- apply the missing amino codec registratoin
See our RELEASE_CHANGELOG for detail list of all changes, or a full commit diff.