BeeZee v6.1.0

• upgrading Cosmos SDK to v0.45.16
• upgrading IBC to v4.5
• Remove starport/ignite from dependencies #18
• Increased Cointrunk article title limit from 140 to 320 characters #19
• Fixed a bug where internet domains longer than 6 letters were considered invalid (domains like cosmos.network) #20
• bumped go version to 1.20
• Removed Burner module address from blacklist so funds can be sent directly to it from the community pool and other external sources #26

Upgrading through gov proposal software upgrade: https://explorer.getbze.com/beezee/gov/20 at height 9079079

BeeZee v6.0.0

This version adds 3 new modules:

• authz module
• cointrunk module
• burner module

Upgrades:

• ibc-go was upgraded to v2
• Cosmos SDK to v.0.45.10

Upgrading through gov proposal software upgrade: https://explorer.getbze.com/beezee/gov/7 at height 4875460

BeeZee v5.1.2

This upgrade will fix IBC proposals routing that will allow us to upgrade Osmosis-BZE client

Upgrading through gov proposal software upgrade: https://explorer.getbze.com/beezee/gov/2 at height 3646700

BeeZee v5.1.1

Bumped required Go version to 1.19.

Used since height 3303144

Note
If you're stuck with error on block 3303144:
INF ABCI Handshake App Info hash="\x00�t8��d�s{�7B����\x12�Se�O�\x00#���_�+" height=3303144 module=consensus protocol-version=0 software-version=5.0.1 INF ABCI Replay Blocks appHeight=3303144 module=consensus stateHeight=3303144 storeHeight=3303145 INF Replay last block using real app module=consensus Error: error during handshake: error on replay: wrong Block.Header.LastResultsHash. Expected 7AB43C67EF1FA52B6F6DE8EF5F18865D17F08656823440D939FB05DADA7A7521, got E5EEAF7D4C1093B40329579198F508AAB4032A6A6C43F28874D508A8ACB4B544

It means that you need to roll back one block.
Make sure you compile bzed from branch rollback with go version 1.19.
Using the freshly compiled binary run bzed rollback --delete-pending-block (can take up to 60 minutes)
You should see an output similar to:
rollback pending block 3303145 Rolled back state to height 3303143 and hash 5202240C36131A13F3EE17BD55EEA2C01514AFFE6F492CD7243A08ADB6BD14C1

Then start bzed v5.1.1. Syncing should be resumed.

BeeZee v5.1.0

### DO NOT USE! JUMP to 5.1.1

Bump Cosmos SDK to v0.45.9

BeeZee v5.0.1

BeeZee v5.0.1 - The Cosmos GENESIS version

Run with halt-height=3303143

v5.0.0

TESTNET:
Please note that the binaries will be updated once we have new features prepared for public testing. Make sure you follow us to always use the up to date binaries.

In order to start the daemon on testnet make sure you do the following:

1. create config directory in /home/{USER}/.bze
2. Copy the genesis-testnet.json file from this repository to /home/{USER}/.bze/config/genesis.json
3. Setup keyring: https://docs.cosmos.network/master/run-node/keyring.html
4. Start the daemon with this peers
   --p2p.persistent_peers="85731d098d4007199efb1be8aae7d116a109ec6a@144.91.119.59:26656,49f20d69f56a0003f42c165a29c3cc8ebee23604@144.91.121.65:26656"

Or add them to the configuration file.

In order to use the daemon and new blockchain features advanced knowledge of linux/server is required.

Please use with caution.