v0.4.3-docker

Same release with v0.4.3 but with higher wasm memory cache

v0.4.3

BINARIES OF THIS RELEASE HAS MAJOR ISSUE, COMPILE BINARY FROM THE SOURCE AFTER git checkout v0.4.3

Release Note

This release is a hot fix for protecting the mempool for preventing heavy transaction to be filled in.

Description

We added new flag tx-gas-hard-limit to terrad cmd. Default tx-gas-hard-limit is 30,000,000. You have freedom to change the default value. This change is only applied to mempool operation (check tx), so can be applied anytime without consensus failure.

How to apply

Add --tx-gas-hard-limit to your terrad executable.

$ terrad start --tx-gas-hard-limit 10000000

Change

• #460 add tx-gas-hard-limit flag to prevent spamming attack

v0.4.2

Release Note

This release is a hotfix for two high-severity issues in the currently live Terra [email protected].

• go-cosmwasm iterator memory leak #440
• treasury division by zero protection #445

How to Upgrade

You can stop, update and restart terrad anytime before the upgrade time.

Upgrade Instructions

$ git fetch --all --tags
$ git checkout v0.4.2
$ make install

Upgrade Time

Target Height: 1,915,199

Tue Feb 23 2021 02:27:50 GMT+0000 (UTC)
Tue Feb 23 2021 11:27:50 GMT+0900 (KST)
Mon Feb 22 2021 18:27:50 GMT-0800 (PST)

v0.4.1

Release Note

This upgrade contains softfork
Please understand the details and apply it before the target height.

Upgrade Details
Upgrade Instructions

How to Upgrade

It is softfork, so you can update terrad anytime before the upgrade time.

$ git fetch --all --tags
$ git checkout v0.4.1
$ make install

Upgrade Time

Target Height for columbus-4: 1200000
Target Height for tequila-0004: 1350000

// MAINNET
// Fri Jan 01 2021 18:00:00 GMT+0900 (KST)
// Fri Jan 01 2021 09:00:00 GMT+0000 (UTC)
// Fri Jan 01 2021 01:00:00 GMT-0800 (PST)
//
// TEQUILA
// Fri Nov 27 2020 12:00:00 GMT+0900 (KST)
// Fri Nov 27 2020 03:00:00 GMT+0000 (UTC)
// Thu Nov 26 2020 19:00:00 GMT-0800 (PST)

WASM updates

• #426 [Enhancement] CosmWasm Cache Implementation (100x faster than before)
• #413 [Enhancement] CosmWasm Logging Whitelist
• #427 [Bugfix] CosmWasm Staking Query
• #433 [Param] Increase ExecuteMsgSize limit to 4096 from 1024

v0.4.0

0.4.0

Release Notes

• Cosmos-SDK v0.38 Release Notes
• Cosmos-SDK v0.39.0 Release Notes
• Cosmos-SDK v0.39.1 Release Notes
• Cosmos-SDK Breaking Changes

Improvements

• #407 Allow gov/MsgVote to be grantable
• #405 CosmWasm oracle exchange rates query interface
• #388 Bump CosmWasm to v0.10.1
• #383 Bump SDK version to v0.39.1
• #374 Bump SDK version to v0.39 and CosmWasm to v0.9.4
• #357 Bump CosmWasm to v0.9
• #352 MsgAuthorization module to allow subkey feature
• #349 Add --old-hd-path flag to support 118 coin type users
• #348 MsgSwapSend to allow sending all swap coin
• #347 CosmWasm custom msg & querier handler
• #343 Burn Address
• #335 CosmWasm integration
• #325 New oracle msgs for vote process optimization
• #324 Update to emit events at proposal handler
• #323 Bump SDK version to v0.38.x

Bug Fixes

• #360 Fix market module pool adjustment to apply delta with actual minted amount
• #336 Allow zero tobin tax rate

Breaking Changes

Keys Migration

Any existing keys that were managed via Keybase in prior versions must be migrated. To migrate keys, execute the following:

$ terracli keys migrate [--home] [--keyring-backend]

The above command will provide a prompt for each existing key and ask if you wish for it to be skipped or not. If the key is not to be skipped, you must provide the correct passphrase for it to be migrated successfully.

Pruning Configuration

The operator can now set the pruning options by passing a pruning configuration via command line option or app.toml. The pruning flag supports the following
options: default, everything, nothing, custom - see the PR for further details. If the operator chooses custom, they may want to provide either of the granular pruning values:

• pruning-keep-recent
• pruning-keep-every
• pruning-interval

The former two options dictate how many recent versions are kept on disk and the offset of what versions are kept after that
respectively, and the latter defines the height interval in which versions are deleted in a batch.

The operator, who wants to upgrade the node from v0.3 to v0.4, must change pruning option in app.toml to one of above options.

API Changes

• The block_meta field has been removed from /blocks/{block_height} becasuse it was redandunt data with block_header.
• The whitelist of/oracle/parameters response has been changed from []string to []{ name: string; tobin_tax: string; }

v0.4.0-rc.5

• #398 Store instantiated contract first before executing response messages

v0.4.0-rc.4

Release for Columbus-4 Testnet tequila-0004

• [#388] Bump CosmWasm to v0.10.1
• [#390] Fix CosmWasm replace versioning

v0.4.0-rc.3

• #383 Bump CosmosSDK to v0.39.1 Launchpad
• #378 Bump CosmWasm to v0.10.0
• #382 Use custom go-cosmwasm for signal propagation
• #384 Add mint module
• #352 Add MsgAuthorization module
• #381 Oracle Exchange Rate and Ballot Rewards by B-Harvest

v0.3.7

Changelog

d191517 bump sdk version to v0.37.14
7fd2e05 keep treasury indicators when exporting

v0.4.0-rc.2

• Bump Cosmos-SDK to v0.39.0 (launchpad)
• Bump CosmWasm to v0.9.4

Upgrade from v0.4.0-rc1

The operator can now set the pruning options by passing a pruning configuration via command line option or app.toml. The pruning flag supports the following options: default, everything, nothing, custom - see here for further details.

When you upgrade the node from v0.4.0-rc1 to v0.4.0-rc2, you need to be careful on pruning option.
Please refer Migrate a node from 0.38.5 to 0.39.0 section.