v0.16.0

What's Changed

• Fix: pfm v4 by @angelorc in #232
• feat(fantoken): add denom to MsgIssueResponse by @angelorc in #232
• chore: add node service handler by @freak12techno in #233

New Contributors

• @freak12techno made their first contribution in #233

Full Changelog: v0.15.0...v0.16.0

v0.15.0

import CometBFT, bump: wasm, ibc-go (#228)

* import CometBFT, bump: wasm, ibc-go

* fix fantoken and merkledrop tests

* fix merkledrop test

* fix ante_handler_test

---------

Co-authored-by: simi <[email protected]>
Co-authored-by: angelorc <[email protected]>

v0.14.1

bump ledger deps (#227)

Co-authored-by: angelorc <[email protected]>

v0.14.0

This is the proposed upgrade for the BitSong Network to version v0.14.0. The scheduled block height for this upgrade to take place is 10,055,000, which is estimated to occur on February 17th, 2023 at 16:30:00 UTC, with a margin of error of approximately 4 hours to accommodate for any potential clock drift. The chain ID for the network will remain as "bitsong-2b".

Changelog

• fix(authz): Add Binary Codec support to MinValCommissionDecorator
• fix(authz): Add MinValCommissionDecorator test

Upgrade process

Clone the go-bitsong reposytory

git clone https://github.com/bitsongofficial/go-bitsong.git
cd go-bitsong
git checkout v0.14.0
make install

Check your version

$ bitsongd version
# 0.14.0

Restart your go-bitsong instance

systemctl restart bitsongd

v0.13.0

Changelog

• Updated Cosmos-sdk to v0.45.11 for improved stability and security
• Upgraded ibc-go to v3.3.1 for enhanced interoperability between different blockchain networks
• Tendermint upgraded to v0.34.24 for better performance and bug fixes
• Integrated Cosmwasm v0.29.2 for advanced smart contract functionality
• Added new command init-from-state which allows for easy initialization of private validator, p2p, genesis, and application configuration, as well as replacement of exported state.

Upgrade process

Clone the go-bitsong reposytory

git clone https://github.com/bitsongofficial/go-bitsong.git
cd go-bitsong
git checkout v0.13.0
make install

Check your version

$ bitsongd version
# 0.13.0

Restart your go-bitsong instance

systemctl restart bitsongd

v0.12.1

(feat): add the new cmd `init-from-state` that initialize a local nod…

v0.12.0

This release fix a security issue on ICS and Cosmos-SDK.

Changelog

• Bump cosmos-sdk v0.45.9
• Bump golang 1.18
• Bump ics v0.8.0

Upgrade process

1. Clone the go-bitsong reposytory

git clone https://github.com/bitsongofficial/go-bitsong.git
cd go-bitsong
git checkout v0.12.0
make install

2. Check your version

$ bitsongd version
# 0.12.0

3. Restart your go-bitsong instance

systemctl restart bitsongd

bitsongd for bwasmnet-1

This binay is used to interact with the current testnet bwasmnet-1

• RPC - https://rpc.bwasmnet-1.bitsong.network:443
• API - https://api.bwasmnet-1.bitsong.network

Version

$ bitsongd version
bwasmnet-1

v0.11.0

This is the final release for the v0.11.0 upgrade which is proposed to take place at height 6,777,500 which should occur approximately July 11th, 2022 at 14:00:00 UTC with a margin of error of ~6 hours to accommodate for any clock drift. The chain id will remain bitsong-2b.

---

This on-chain upgrade governance proposal, is to adopt go-bitsong v0.11.0 which includes a number of updates, fixes and new modules. By voting YES to this proposal, you approve of adding these updates to the BitSong Network.

Background

Since the last upgrade at height 4566000 there have been a number of updates, fixes and new modules added to the Cosmos SDK, IBC and Tendermint. This upgrade include the Fantoken and Merkledrop modules. The following updates are included in go-bitsong v0.11.0:

• (fantoken) introduce the fantoken module
• (merkledrop) introduce the merkledrop module
• (app) bump cosmos-sdk to v0.45.6
• (app) bump ibc to v3.0.0
• (app) bump tendermint to v0.34.19
• (app) bump packet-forward-middleware to v2.1.1
• (app) update swagger to reflect new modules
• (app) small fixs Makefile

Golang v1.18.x

This upgrade require golang v1.18.x

On-Chain Upgrade Process

This upgrade can be performed in multiple ways. When the network reaches the halt height, the state machine program of the BitSong Network will be halted. The classic method for upgrading requires all validators and node operators to manually substitute the existing state machine binary with the new binary.

v0.10.0

This is the final release for the v0.10.0 upgrade which is proposed to take place at height 4,566,000 which should occur approximately February 8th, 2022 at 13:00:00 UTC with a margin of error of ~6 hours to accommodate for any clock drift. The chain id will remain bitsong-2b.

---

This on-chain upgrade governance proposal, is to adopt go-bitsong v0.10.0 which includes a number of updates, fixes and new modules. By voting YES to this proposal, you approve of adding these updates to the BitSong Network.

Background

Since the last upgrade at height 2966150 there have been a number of updates, fixes and new modules added to the Cosmos SDK, IBC and Tendermint. The following updates are included in go-bitsong v0.10.0:

• Bump golang prerequisite to 1.17
• Bump Cosmos-SDK to v0.44.5 which notably includes fixes for the vesting accounts and two new modules outlined below. This release of the Cosmos SDK recognizes that IBC is maintained in an independent repository and is instead imported into go-bitsong from that repository. For a full list of updates in Cosmos-SDK v0.44.5 please see the CHANGELOG.md
  • Add the authz module to the BitSong Network, which will help lower the barrier to mass consumer adoption of Blockchain technologies by improving the UX and security of managine an account on the BitSong Network. x/authz is an implementation of a Cosmos SDK module, per ADR 30, that allows granting arbitrary privileges from one account (the granter) to another account (the grantee). Authorizations must be granted for a particular Msg service method one by one using an implementation of the Authorization interface.
  • Add the feegrant module to the BitSong Network, which will help lower the barrier to mass consumer adoption of Blockchain technologies by improving the UX of spending gas with an account on the BitSong Network. This module allows accounts to grant fee allowances and to use fees from their accounts. Grantees can execute any transaction without the need to maintain sufficient fees.
  • BREAKING CHANGE NOTICE While a full list of breaking changes should be checked within the Cosmos SDK v0.44.5 CHANGELOG.md, it's imortant to highlight PR #10041 which impacts WALLETS AND EXCHANGES. This update has removed the deprecated the legacy REST endpoints for broadcast & encode. This means POST /tx and POST /txs/encode no longer work. Please see the REST Endpoints Migration guide to migrate to the new REST endpoints.
• Add IBC as a standalone module from the Cosmos SDK using version v2.0.0. See the CHANGELOG.md for details.
  • Please note that the governance parameter for MaxExpectedBlockDelay is set to 30 seconds. As a recap, this means if a connection is opened with a packet delay of 1 minute, it requires 2 blocks to be committed after the consensus state is submitted before the packet can be processed.
• Add packet-forward-middleware v1.0.1 prepared and tested by Strangelove Ventures. This feature allows multi-hop IBC transfer messages so that a user can send tokens from chain A to chain C via chain B. This is useful in ensuring the BitSong Network is used as a routing hub as well as when "unwrapping" tokens to their source chain after they have taken multiple hops.
• As per Proposal #5 increase minimum commission rate to 5%, ensures that new validators joining the set have to adhere to this
• As per Proposal #6 mint 9,656,879,130,000ubtsg to the cassini multisig wallet bitsong12r2d9hhnd2ez4kgk63ar8m40vhaje8yaa94h8w

On-Chain Upgrade Process

This upgrade can be performed in multiple ways. When the network reaches the halt height, the state machine program of the BitSong Network will be halted. The classic method for upgrading requires all validators and node operators to manually substitute the existing state machine binary with the new binary.