v1.4.1-patch.2

Dragonberry patch

Patch instructions

⚠️ If you want the upgrade to use iavl-fastnode (will improve performance) add iavl-disable-fastnode = false in app.toml under [base] before re-starting the node (it'll take several hours if you don't resync the node).

⚠️ If you have already installed a previous 1.4.1 version be sure to set iavl-disable-fastnode = false or you will apphash

Note: if you have modified your systemd unit file (/etc/systemd/system/secret-node.service) you will need to re-apply those changes post installation and pre-service restart.

Check what database type you're currently using:

awk -F \" '/^db_backend =/{print $2}' ~/.secretd/config/config.toml

Uncomment and download the right binary based on your database type:

# Stop node
sudo systemctl stop secret-node

# Get & verify secretd v1.4.1-patch.2

## goleveldb
# wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.4.1-patch.2/secretnetwork_1.4.1-patch.2_mainnet_goleveldb_amd64.deb"
# echo "9f9fac947083abcb90dbe9ffa0ad0e8f491d44654599b8768c068f49cbfc3a5d secretnetwork_1.4.1-patch.2_mainnet_goleveldb_amd64.deb" | sha256sum --check

## rocksdb
# wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.4.1-patch.2/secretnetwork_1.4.1-patch.2_mainnet_rocksdb_amd64.deb"
# echo "ef17a78fea1aa48a39044f61196fa492b4ca2cd786209d894f21312370f3aab7 secretnetwork_1.4.1-patch.2_mainnet_rocksdb_amd64.deb" | sha256sum --check

# Install new binaries
sudo apt install -y ./secretnetwork_1.4.1-patch.2_mainnet_*_amd64.deb

# re-apply any systemd unit file customizations

# Restart the node
sudo systemctl restart secret-node

v1.5.1-beta.4

⚠️ TESTNET ⚠️

Upgrading from v1.4.1-beta.2

When the network reaches the halt height XYZ, you'll see this message in your node's log (journalctl -fu secret-node):

2:00PM ERR UPGRADE "v1.5" NEEDED at height: XYZ:
2:00PM ERR CONSENSUS FAILURE!!! err="UPGRADE \"v1.5\" NEEDED at height: XYZ

Then, the upgrade steps for v1.5 are:

⚠️ Note: if you have modified your systemd unit file (/etc/systemd/system/secret-node.service) you will need to re-apply those changes post installation and pre-service restart.

Check what database type you're currently using:

awk -F \" '/^db_backend =/{print $2}' ~/.secretd/config/config.toml

Uncomment and download the right binary based on your database type:

# Stop the v1.4 node, to make sure that your process manager isn't trying to restart it while you upgrade
sudo systemctl stop secret-node

# Get & verify secretd v1.5

## goleveldb
# wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.5.1-beta.4/secretnetwork_1.5.1-beta.4_testnet_goleveldb_amd64.deb"
# echo "1a08f1f035f0db016a6bac69625adf5c9f938ac7a6eba8ca2c182dcad6628842 secretnetwork_1.5.1-beta.4_testnet_goleveldb_amd64.deb" | sha256sum --check

## rocksdb
# wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.5.1-beta.4/secretnetwork_1.5.1-beta.4_testnet_rocksdb_amd64.deb"
# echo "cb59172976f27605a935870292c60dac665d0a605857dce11eb60a5fa1bdce2f secretnetwork_1.5.1-beta.4_testnet_rocksdb_amd64.deb" | sha256sum --check

# Install v1.5 binaries
sudo apt install -y ./secretnetwork_1.5.1-beta.4_testnet_*_amd64.deb

# re-apply any systemd unit file customizations

# Restart the node
sudo systemctl restart secret-node

After restarting the node with v1.5, you should see INF applying upgrade "v1.5" at height: XYZ in the logs (journalctl -fu secret-node). Once 67% of voting power comes online, you'll see blocks executing again.

Details of Upgrade Time

When the network reaches the halt height XYZ, the Secret Network testnet blockchain will be halted and validators will need to take action to upgrade the chain to the secretd v1.5 binary (be it manually or automatically).

The proposal targets the upgrade proposal block to be XYZ, anticipated to be on Thursday October 6, 2022 at 2:00PM UTC.

The upgrade is anticipated to take approx 30 minutes, during which time, there will not be any on-chain activity on the network.

In Case of an Upgrade Failure

In the event of an issue at upgrade time, we should coordinate via the "SN Testnet Validators" Telegram group.

If as a result of a software bug the network fails to produce new blocks with the v1.5 binaries, the SCRT Labs team will distribute a v1.4 binary with an empty v1.5 upgrade handler, which will essentially allow the chain to revert to v1.4 while continuing to produce new blocks.

Upgrading from v1.5.0-beta.4

⚠️ Note: if you have modified your systemd unit file (/etc/systemd/system/secret-node.service) you will need to re-apply those changes post installation and pre-service restart.

Check what database type you're currently using:

awk -F \" '/^db_backend =/{print $2}' ~/.secretd/config/config.toml

Uncomment and download the right binary based on your database type:

# Stop the v1.5.0 node
sudo systemctl stop secret-node

# Get & verify secretd v1.5.1

## goleveldb
# wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.5.1-beta.4/secretnetwork_1.5.1-beta.4_testnet_goleveldb_amd64.deb"
# echo "1a08f1f035f0db016a6bac69625adf5c9f938ac7a6eba8ca2c182dcad6628842 secretnetwork_1.5.1-beta.4_testnet_goleveldb_amd64.deb" | sha256sum --check

## rocksdb
# wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.5.1-beta.4/secretnetwork_1.5.1-beta.4_testnet_rocksdb_amd64.deb"
# echo "cb59172976f27605a935870292c60dac665d0a605857dce11eb60a5fa1bdce2f secretnetwork_1.5.1-beta.4_testnet_rocksdb_amd64.deb" | sha256sum --check

# Install v1.5.1 binaries
sudo apt install -y ./secretnetwork_1.5.1-beta.4_testnet_*_amd64.deb

# re-apply any systemd unit file customizations

# Restart the node
sudo systemctl restart secret-node

Note: Upgrading from v1.5.0 to v1.5.1 can take 2-3 hours, but afterwards node performance should drastically improve compared to v1.4.0.

What's Changed

• Fix secret message parsing when message is plaintext in IBC by @liorbond in #1199

Full Changelog: v1.4.1-beta.8...v1.5.1-beta.4

v1.5.0-beta.4

Upgrading from v1.4.0-beta.6

When the network reaches the halt height XYZ, you'll see this message in your node's log (journalctl -fu secret-node):

2:00PM ERR UPGRADE "v1.5" NEEDED at height: XYZ:
2:00PM ERR CONSENSUS FAILURE!!! err="UPGRADE \"v1.5\" NEEDED at height: XYZ

Then, the upgrade steps for v1.5 are:

⚠️ Note: if you have modified your systemd unit file (/etc/systemd/system/secret-node.service) you will need to re-apply those changes post installation and pre-service restart.

Check what database type you're currently using:

awk -F \" '/^db_backend =/{print $2}' ~/.secretd/config/config.toml

Uncomment and download the right binary based on your database type:

# Stop the v1.4 node, to make sure that your process manager isn't trying to restart it while you upgrade
sudo systemctl stop secret-node

# Get & verify secretd v1.5

## goleveldb
# wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.5.0-beta.4/secretnetwork_1.5.0-beta.4_testnet_goleveldb_amd64.deb"
# echo "2807c176955e29ff219b0cf60aac51d922785800a4bdac887ae8bc6721f8e4fe secretnetwork_1.5.0-beta.4_testnet_goleveldb_amd64.deb" | sha256sum --check

## rocksdb
# wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.5.0-beta.4/secretnetwork_1.5.0-beta.4_testnet_rocksdb_amd64.deb"
# echo "b00d09df145ec98414c75f6a69ac4a94de4f1f2b66b705f0e5a3492d1a0937f9 secretnetwork_1.5.0-beta.4_testnet_rocksdb_amd64.deb" | sha256sum --check

# Install v1.5 binaries
sudo apt install -y ./secretnetwork_1.5.0-beta.4_testnet_*_amd64.deb

# re-apply any systemd unit file customizations

# Restart the node
sudo systemctl restart secret-node

After restarting the node with v1.5, you should see INF applying upgrade "v1.5" at height: XYZ in the logs (journalctl -fu secret-node). Once 67% of voting power comes online, you'll see blocks executing again.

Details of Upgrade Time

When the network reaches the halt height XYZ, the Secret Network testnet blockchain will be halted and validators will need to take action to upgrade the chain to the secretd v1.5 binary (be it manually or automatically).

The proposal targets the upgrade proposal block to be XYZ, anticipated to be on Thursday October 6, 2022 at 2:00PM UTC.

The upgrade is anticipated to take approx 30 minutes, during which time, there will not be any on-chain activity on the network.

In Case of an Upgrade Failure

In the event of an issue at upgrade time, we should coordinate via the "SN Testnet Validators" Telegram group.

If as a result of a software bug the network fails to produce new blocks with the v1.5 binaries, the SCRT Labs team will distribute a v1.4 binary with an empty v1.5 upgrade handler, which will essentially allow the chain to revert to v1.4 while continuing to produce new blocks.

What's Changed

• Fix secret message parsing when message is plaintext in IBC by @liorbond in #1199

Full Changelog: v1.4.0...v1.5.0-beta.4

v1.4.1-patch.1

Patch instructions

⚠️ Note: if you have modified your systemd unit file (/etc/systemd/system/secret-node.service) you will need to re-apply those changes post installation and pre-service restart.

Check what database type you're currently using:

awk -F \" '/^db_backend =/{print $2}' ~/.secretd/config/config.toml

Uncomment and download the right binary based on your database type:

# Stop node
sudo systemctl stop secret-node

# Get & verify secretd v1.4.1-patch.1

## goleveldb
# wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.4.1-patch.1/secretnetwork_1.4.1-patch.1_mainnet_goleveldb_amd64.deb"
# echo "916e66b0de0dc113b7e0b493b0aa04999de41324add6d8f221cae3b4fcf20437 secretnetwork_1.4.1-patch.1_mainnet_goleveldb_amd64.deb" | sha256sum --check

## rocksdb
# wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.4.1-patch.1/secretnetwork_1.4.1-patch.1_mainnet_rocksdb_amd64.deb"
# echo "263498bd271c136515285af8112e105b3768b06969ef665ea1e0cadb69442bfc secretnetwork_1.4.1-patch.1_mainnet_rocksdb_amd64.deb" | sha256sum --check

# Install new binaries
sudo apt install -y ./secretnetwork_1.4.1-patch.1_mainnet_*_amd64.deb

# re-apply any systemd unit file customizations

# Restart the node
sudo systemctl restart secret-node

v1.4.0-patch.1

Patch instructions

⚠️ Note: if you have modified your systemd unit file (/etc/systemd/system/secret-node.service) you will need to re-apply those changes post installation and pre-service restart.

Check what database type you're currently using:

awk -F \" '/^db_backend =/{print $2}' ~/.secretd/config/config.toml

Uncomment and download the right binary based on your database type:

# Stop node
sudo systemctl stop secret-node

# Get & verify secretd v1.4.0-patch.1

## goleveldb
# wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.4.0-patch.1/secretnetwork_1.4.0-patch.1_mainnet_goleveldb_amd64.deb"
# echo "3fa95c373cc85277e6ae85256c5261aa99b9128255162c8e467e0498fd3017a0 secretnetwork_1.4.0-patch.1_mainnet_goleveldb_amd64.deb" | sha256sum --check

## rocksdb
# wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.4.0-patch.1/secretnetwork_1.4.0-patch.1_mainnet_rocksdb_amd64.deb"
# echo "1de8ed31a4d64c02907b2d9884cd3267c71be680c7bab44da4e73e917d252a61 secretnetwork_1.4.0-patch.1_mainnet_rocksdb_amd64.deb" | sha256sum --check

# Install new binaries
sudo apt install -y ./secretnetwork_1.4.0-patch.1_mainnet_*_amd64.deb

# re-apply any systemd unit file customizations

# Restart the node
sudo systemctl restart secret-node

v1.4.0-beta.15

Update some deps

v1.4.1-beta.8

ibc-go v3.0.0 -> v3.3.0

v1.4.0

Shockwave Delta

The v1.4 software upgrade is set for block 5,309,200, which is estimated to occur on Wednesday September 21, 2022 at 12:20pm UTC. You can monitor the ETA at https://www.mintscan.io/secret/blocks/5309200.

Upgrade instructions

https://docs.scrt.network/secret-network-documentation/post-mortems-upgrades/upgrade-instructions/shockwave-delta

Highlights

This upgrade adds the following features:

• CosmWasm v1
• Bump WASM gas costs
  • Base WASM invocation from 10k to 100k
  • WASM chain access 2k per access
• Add support for EIP191 signatures (MetaMask compatible data)
• Ledger support for Authz & Feegrant
• Revert Chain of Secrets tombstone state and restore slashed funds to all delegators
• Upgrade the ibc-go module to v3.3.0

On-chain proposal

• https://secretnodes.com/proposals/110
• https://www.mintscan.io/secret/proposals/110
• https://ping.pub/secret/gov/110

Full Changelog

What's Changed

• v1.3.1 and docker by @Cashmaney in #933
• AnalyzeCode functionality by @liorbond in #935
• Cosmwasm V1 IBC by @liorbond in #936
• Node updating script by @dbriggsie in #938
• Instantiate event by @liorbond in #939
• Fix for CI aesm by @Cashmaney in #948
• Port v0.10 test contract to v1 by @assafmo in #944
• Lior cosmwasm v1 by @liorbond in #952
• Cw v1 refactor output structure by @liorbond in #955
• Support old CPUs in SGX_MODE=SW by @assafmo in #951
• Fix CI & Test Bank::MsgSend for CosmWasm v1 & v0.10 by @assafmo in #958
• Port dev image faucet from python to node #957 by @levackt in #959
• gofumpt -w -l . by @faddat in #946
• add gitpod develeopment environment by @faddat in #953
• Port dev image faucet from python to node #961 by @levackt in #963
• fumpt the v1 work by @faddat in #965
• Test v1 BankMsg::Burn & v0.10+v1 CosmosMsg::Custom by @assafmo in #962
• go 1.18 by @faddat in #947
• Feature/node faucet by @Cashmaney in #961
• Reverted xgo version to one that doesn't fail by @Cashmaney in #972
• Added dev environment for vscode/docker/gitpod by @Cashmaney in #971
• Changing log levels a bit to make running localsecret easier to parse by @Cashmaney in #950
• Custom chain ID from env by @levackt in #970
• Getting started docs by @Cashmaney in #1022
• test: use T.TempDir to create temporary test directory by @Juneezee in #1021
• settings by @faddat in #967
• Change query depth limit from 5 to 10 by @liorbond in #1062
• Fix another recursion test by @liorbond in #1068
• Cosmwasm v1 funds tests by @eshelB in #1070
• Lior update wasmd 028 by @liorbond in #1069
• Print proper error when unknown code id by @liorbond in #1074
• Fixed startup script to be a bit friendlier. By default will run ./se… by @Cashmaney in #1078
• Correct the error in label cli by @liorbond in #1075
• Fix list-contract-by-code output by @liorbond in #1077
• Fix 2 possible null drefs by @liorbond in #1083
• Fix contract-hash command in cli by @liorbond in #1076
• Add missing RPC function and make proto file readable by @liorbond in #1081
• Add all of the missing RPC apis by @liorbond in #1080
• Create contract hash by ID api both for CLI and RPC by @liorbond in #1079
• update CI by @liorbond in #1090
• Fix CI by @liorbond in #1091
• Fix possible null-dref by @liorbond in #1092
• Fix go linter warnings (including some more null-drefs) by @liorbond in #1093
• stop using ioutil by @faddat in #1066
• Limit length of error messages by @Cashmaney in #1086
• Eshel ibc env refactor by @Cashmaney in #1095
• IBC packet receive tests and bug fixes by @liorbond in #1096
• All IBC tests by @liorbond in #1097
• Fix gtests by @liorbond in #1098
• Lior ibc tests by @liorbond in #1099
• Cosmwasm v1 with every by @liorbond in #1105
• WIP: CosmWasm v1 IBC Receive Hooks by @assafmo in #966
• StargateQuery (and more) by @assafmo in #1073
• IBC + Stargate + wasmd 0.28 by @liorbond in #1101
• Fix redundant base64 in SubMsgResponse by @liorbond in #1107
• Ibc integration tests by @eshelB in #1113
• Fix CI by uploading the artifacts by @liorbond in #1110
• Fix xbuild the same way as it was fixed in master by @liorbond in #1115
• CW v1 supports every error rather than only StdErrors in query by @liorbond in #1114
• Split events when using StoreCode by @liorbond in #1111
• Fixed that stupid dependency on SGX_MODE in secretcli by @Cashmaney in #1104
• Add /cosmos/tx/v1beta1 to swagger by @assafmo in #1117
• go-1.19 by @faddat in #1067
• Refactor integration tests + Test MsgDelegate by @assafmo in #1118
• Fix CI + More Stuff by @assafmo in #1121
• Add support for nano ledger s+ by @bjaanes in #1123
• Gitignore by @faddat in #969
• make go tests start up faster when rerunning them by @reuvenpo in #1124
• more perf adjustments to go tests by @reuvenpo in #1125
• Fix EIP191 signature verification inside the enclave by @assafmo in #1127
• Lint CosmWasm v1 by @assafmo in #1129
• More CosmWasm v1 Integration Tests by @assafmo in #1128
• Overhaul gRPC queries by @assafmo in #1130
• Add ibc routing for compute module by @liorbond in #1132
• Init tx info by @liorbond in #1131
• Stderr logs cosmwasmv1 by @liorbond in #1134
• v1.4 upgrade handler by @Cashmaney in #1109
• Decrypt multiple txs q compute tx by @toml01 in #1135
• Ibc integration tests cw by @liorbond in #1137
• Bump gas costs to 100K per contract instance and another 200_000 (was… by @Cashmaney in #1133
• Fix release by @liorbond in #1139
• Fix secretcli q compute tx data field decryption by @assafmo in #1140
• Add validate test by @liorbond in #1141
• Create dependabot.yml by @faddat in #1059
• Create codeql-analysis.yml by @Cashmaney in #1020
• Bump actions/download-artifact from 2 to 3 by @dependabot in #1143
• Bump docker/login-action from 1.10.0 to 2.0.0 by @dependabot in #1144
• Bump actions/cache from 1 to 3 by @dependabot in #1145
• Bump action...

v1.4.1-beta.3

⚠️ TESTNET ⚠️

Upgrading from v1.4.0-beta.6

Check what database type you're currently using:

awk -F \" '/^db_backend =/{print $2}' ~/.secretd/config/config.toml

Uncomment and download the right binary based on your database type:

# Stop the v1.4.0 node
sudo systemctl stop secret-node

# Get & verify secretd v1.4.1

## goleveldb
# wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.4.1-beta.3/secretnetwork_1.4.1-beta.3_testnet_goleveldb_amd64.deb"
# echo "1ec2b9b197196113f34ec3430603972e472b35f91db0e6b98d2f772f8e0081d6 secretnetwork_1.4.1-beta.3_testnet_goleveldb_amd64.deb" | sha256sum --check

## rocksdb
# wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.4.1-beta.3/secretnetwork_1.4.1-beta.3_testnet_rocksdb_amd64.deb"
# echo "f8aeb3f24448f244e36f4a1fb5f7f64ccc04c1796cac0e76f38aa6362c0b3017 secretnetwork_1.4.1-beta.3_testnet_rocksdb_amd64.deb" | sha256sum --check

# Install v1.4.1 binaries
sudo apt install -y ./secretnetwork_1.4.1-beta.3_testnet_*_amd64.deb

# Restart the node
sudo systemctl restart secret-node

Note: Upgrading can take 2-3 hours, but afterwards node performance should drastically improve compared to v1.4.0.

What's Changed

• Upgrade Cosmos SDK to v0.45.8
• Upgrade Tendermint to v0.34.21

Full Changelog: v1.4.0-beta.6...v1.4.1-beta.3

v1.4.0-beta.6

⚠️ TESTNET ⚠️

Upgrade instructions

https://docs.scrt.network/secret-network-documentation/post-mortems-upgrades/upgrade-instructions/shockwave-delta-testnet

What's Changed

• Create dependabot.yml by @faddat in #1059
• Create codeql-analysis.yml by @Cashmaney in #1020
• Refactored v1 & v0.10 contracts to be in the same path by @Cashmaney in #1126
• StartgateQuery: Remove all non-O(1) queries by @assafmo in #1163
• Fix & test v0.10 env.block.time by @assafmo in #1162
• Fix & test init data output by @liorbond in #1164

Full Changelog: v1.4.0-beta.5...v1.4.0-beta.6