v1.7.0-rc.2

⚠️ TESTNET ⚠️

Upgrade instructions

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.6.0 node
sudo systemctl stop secret-node

# Get & verify secretd v1.7.0

## goleveldb
# wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.7.0-rc.2/secretnetwork_1.7.0-rc.2_testnet_goleveldb_amd64.deb"
# echo "9c6266f3e4bf0cac968e6a999ee5f7e7c7294c59f8fbbb7aa7237b468b0d72ad secretnetwork_1.7.0-rc.2_testnet_goleveldb_amd64.deb" | sha256sum --check

## rocksdb
# wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.7.0-rc.2/secretnetwork_1.7.0-rc.2_testnet_rocksdb_amd64.deb"
# echo "9c6266f3e4bf0cac968e6a999ee5f7e7c7294c59f8fbbb7aa7237b468b0d72ad secretnetwork_1.7.0-rc.2_testnet_rocksdb_amd64.deb" | sha256sum --check

# Install 1.7.0 binaries
sudo apt install -y ./secretnetwork_1.7.0-rc.2_testnet_*_amd64.deb

# Restart the node
sudo systemctl restart secret-node

Mandatory secret.js update (non-API breaking)

The tx encryption key format has changed, requiring an update of secret.js:

• v1.5.x, v1.6.x -> v1.7.1-beta.2 (Recommended)
• v1.4.x -> v1.4.6
• v0.17.8 - can still be used

Update

Ubuntu 18.04 is no longer supported

What's Changed

• Fixed OSX Ledger disconnection issues in secretcli
• Fixed an issue when sending multiple message types in the same tx
• Fixed /cosmos/base/node/v1beta1/config
• Added expedited gov proposals
• Added the ability to rotate consensus seed during a network upgrade
• Added a feature for auto-restake of staking rewards

v1.7.0-rc.1

⚠️ TESTNET ⚠️

Upgrade instructions

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.6.0 node
sudo systemctl stop secret-node

# Get & verify secretd v1.7.0

## goleveldb
# wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.7.0-rc.1/secretnetwork_1.7.0-rc.1_testnet_goleveldb_amd64.deb"
# echo "83ba70feb0405f5643be368d7707907efdfcc18567deb33f3dfe81292b073e1d secretnetwork_1.7.0-rc.1_testnet_goleveldb_amd64.deb" | sha256sum --check

## rocksdb
# wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.7.0-rc.1/secretnetwork_1.7.0-rc.1_testnet_rocksdb_amd64.deb"
# echo "41906c21a0929358114a6491f8a895eb8c3020fba62971d923a4f2c57b358b70 secretnetwork_1.7.0-rc.1_testnet_rocksdb_amd64.deb" | sha256sum --check

# Install 1.7.0 binaries
sudo apt install -y ./secretnetwork_1.7.0-rc.1_testnet_*_amd64.deb

# Restart the node
sudo systemctl restart secret-node

Mandatory secret.js update (non-API breaking)

The tx encryption key format has changed, requiring an update of secret.js:

• v1.5.x, v1.6.x -> v1.7.1-beta.2 (Recommended)
• v1.4.x -> v1.4.6
• v0.17.8 - can still be used

Update

Ubuntu 18.04 is no longer supported

What's Changed

• Fixed OSX Ledger disconnection issues in secretcli
• Fixed an issue when sending multiple message types in the same tx
• Fixed /cosmos/base/node/v1beta1/config
• Added expedited gov proposals
• Added the ability to rotate consensus seed during a network upgrade
• Added a feature for auto-restake of staking rewards

v1.6.0

Highlights:

• Fixed issue causing registrations to fail
• Changed internal WASM engine to Wasm3 from Wasmi. Contract performance increased greatly
• Changed default grpc-concurrency to false (from true). For nodes that serve API requests, we highly recommend setting this manually to true as described in the release notes for version 1.5.1
• Reduced gas costs

See https://github.com/scrtlabs/SecretNetwork/blob/master/CHANGELOG.md for more detailed patch notes.

Note: with this release we are enforcing a custom, more strict policy than Intel IAS, for specific machines with CPUIDs 506E3 and 906ED. The check_hw tool can be used to verify your patch level & attestation status.

Upgrade Time

When the network reaches the halt height 6,537,300, the Secret Network blockchain will be halted and validators will need to take action to upgrade the chain to the secretd v1.6 binary.

The proposal targets the upgrade proposal block to be 6,537,300, anticipated to be on Tuesday, December 13, 2022 at 2:00PM UTC.

v1.6.0-rc.2

testnet upgrade name fix

v1.5.1

29/11/2022 - Startup fix due to TCB recovery - startup validation on 1.5.1 does not account for SW_HARDENING_NEEDED including INTEL-SA-00615 in it's response. Registering using this binary will not work, however restarting your node can be done using the _startup_bypass packages.

Fix for GRPC-gateway concurrency. This will greatly improve performance on nodes serving queries to GRPC-gateway requests (REST requests going to v1beta1/blah/blah)

Note that concurrency is toggled from the "concurrency" flag under GRPC in app.toml - see an example below.
(max-send-msg-size and max-recv-msg-size are also new, but are less important)

In this version the default is set to true for ease of deployment - We currently recommend for validators to not update to this version, or if you do, manually set concurrency to false. This update is for node runners that provide API services to increase performance of nodes that serve queries.

In this release we also include a special version for nodes that serve queries from legacy apps (those that use secretjs 0.x, for example Keplr) - this version contains an unstable patch that serves legacy LCD and rpc requests much faster. This fix has been found to be unstable at scale, and should be used sparingly until secretjs 1.5 is released and apps upgrade to the latest version

[grpc]

# Enable defines if the gRPC server should be enabled.
enable = true

# Address defines the gRPC server address to bind to.
address = "0.0.0.0:9090"

# The default value is math.MaxInt32.
max-recv-msg-size = "10485760"

# The default value is math.MaxInt32.
max-send-msg-size = "2147483647"

# Concurrency defines if node queries should be done in parallel.
# This is experimental and has led to node failures, so enable with caution.
# The default value is true.
concurrency = true

v1.5.0

Secret Network v1.5 Upgrade

What's Changed

• Fix secret message parsing when message is plaintext in IBC by @liorbond in #1199
• Refactor Tendermint and Cosmos configs by @assafmo in #1211
• Fix creating accounts using ICA by @assafmo in #1215
• Fix node registration by @Cashmaney in #1221
• Update Cosmos SDK 0.45.9 -> 0.45.10 & Tendermint 0.34.21 -> 0.34.22 by @assafmo in #1230
• Update IBC 3.3.0 -> 3.3.1 by @dependabot in #1237
• Fix nested attributes signatures by @liorbond in #1241
• Fix state sync by @assafmo in #1243
• Fix some protobuf type names by @assafmo in 256d9b2

Special thanks: @faddat!

Full Changelog: v1.4.1-patch.3...v1.5.0

Upgrade Time

When the network reaches the halt height 5,941,700, the Secret Network blockchain will be halted and validators will need to take action to upgrade the chain to the secretd v1.5 binary.

The proposal targets the upgrade proposal block to be 5,941,700, anticipated to be on Wednesday November 2, 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.

Upgrade Instructions

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

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

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/secretnetwork_1.5.0_mainnet_goleveldb_amd64.deb"
# echo "483e25f6ba189d4763a81da94f32e20306370bb3111aa208d16c0141a4a0da7d secretnetwork_1.5.0_mainnet_goleveldb_amd64.deb" | sha256sum --check

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

# Install v1.5 binaries
sudo apt install -y ./secretnetwork_1.5.0_mainnet_*_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: 5941700 in the logs (journalctl -fu secret-node). Once 67% of voting power comes online, you'll see blocks executing again.

In Case of an Upgrade Failure

In the event of an issue at upgrade time, we should coordinate via the "SN 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.

v1.4.1-patch.3

Dragonberry full 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.3

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

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

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

# re-apply any systemd unit file customizations

# Restart the node
sudo systemctl restart secret-node

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