v1.27.2

Chain secret-4 is already on 1.27.2. Pick the package that matches the machine's Ubuntu version.

Node that already has the seed

dpkg replaces /etc/systemd/system/secret-node.service. This puts the current unit back, then restarts.

. /etc/os-release
case "$VERSION_ID" in
  22.04|24.04) ;;
  *) echo "Ubuntu 22.04 or 24.04"; exit 1 ;;
esac

deb="secretnetwork_1.27.2_MAINNET_goleveldb_amd64_ubuntu-${VERSION_ID}.deb"
curl -fL -o "/tmp/$deb" \
  "https://github.com/Secret3dev/SecretNetwork/releases/download/v1.27.2/$deb"
case "$VERSION_ID" in
  22.04) echo "ffcca0fe04422228ae92b0bb216808a0eafa1030a7073d1bf1ca347a0781fcbb  /tmp/$deb" ;;
  24.04) echo "f90e7104d6308d491c9cfdb691672302b17b3364c3b355962479adc46da3d903  /tmp/$deb" ;;
esac | sha256sum -c -

sudo cp -a /etc/systemd/system/secret-node.service /tmp/secret-node.service.bak
sudo dpkg -i "/tmp/$deb"
sudo cp -a /tmp/secret-node.service.bak /etc/systemd/system/secret-node.service
sudo systemctl daemon-reload
sudo systemctl restart secret-node
secretd version

secretd version should print 1.27.2.

New machine

Same package. secretd auto-register does not work. A machine that is not on the hardware allowlist cannot register. The node home has to be chain secret-4 before start, with the network genesis and persistent peers already in ~/.secretd.

. /etc/os-release
case "$VERSION_ID" in
  22.04|24.04) ;;
  *) echo "Ubuntu 22.04 or 24.04"; exit 1 ;;
esac

deb="secretnetwork_1.27.2_MAINNET_goleveldb_amd64_ubuntu-${VERSION_ID}.deb"
curl -fL -o "/tmp/$deb" \
  "https://github.com/Secret3dev/SecretNetwork/releases/download/v1.27.2/$deb"
sudo dpkg -i "/tmp/$deb"

secretd init-enclave
secretd tx register auth /opt/secret/.sgx_secrets/attestation_combined.bin \
  --from KEY --chain-id secret-4 \
  --node https://rpc.secret.mainnet.secret3.dev

secretd query register secret-network-params \
  --node https://rpc.secret.mainnet.secret3.dev
NODE_ID=$(secretd dump /opt/secret/.sgx_secrets/pubkey.bin)
SEED=$(secretd query register seed "$NODE_ID" \
  --node https://rpc.secret.mainnet.secret3.dev | sed 's/^0x//')
secretd configure-secret node-master-key.txt "$SEED"
sudo systemctl enable --now secret-node

secret-network-params writes node-master-key.txt in the current directory. Run configure-secret from that directory, after the register transaction is in a block.

Testnet

Chain trinity-b. Use the TRINITY package for the same Ubuntu version. Same install and register steps, with that filename and --chain-id trinity-b.

deb="secretnetwork_1.27.2_TRINITY_goleveldb_amd64_ubuntu-${VERSION_ID}.deb"
curl -fL -o "/tmp/$deb" \
  "https://github.com/Secret3dev/SecretNetwork/releases/download/v1.27.2/$deb"

22.04 sha256 5ce31f1be3350b8d5d8757eec8c068adfc1b2e34c9aeaf6d8a3ff1eb9e252a1a. 24.04 sha256 de19050e32b7704b463876fa085289ca05c26fcdcb60711d8ef0249d78b05eeb.

v1.26.0-community-continuance

Install (all validators)

One script: detects chain-id (pulsar-3 → TESTNET package, secret-4 → MAINNET package)
and Ubuntu (22.04 / 24.04), downloads the matching asset from this Release, verifies
sha256, restarts secret-node.

curl -fsSL -o install.sh \
  https://raw.githubusercontent.com/Secret3dev/SecretNetwork/v1.26.0-community-continuance/scripts/install-continuance.sh
chmod +x install.sh
sudo ./install.sh

The script refuses a TESTNET package on secret-4 and a MAINNET package on pulsar-3.
Do not use --unsafe-skip-upgrades. Enclave is unchanged (MRENCLAVE 2b9a69d6…a80d).

Packages

File	SHA-256
secretnetwork_1.26.0_TESTNET_goleveldb_amd64_ubuntu-22.04.deb	672dd49b5b95587559e998f89e260142a4bcdb958a5f3009ece50e8ff4ce06d4
secretnetwork_1.26.0_TESTNET_goleveldb_amd64_ubuntu-24.04.deb	d86def55a3c38c7de3dd91583bc66c29e05962e039e0b2ae47939b5f04faf925
secretnetwork_1.26.0_MAINNET_goleveldb_amd64_ubuntu-22.04.deb	bb9baf0ee8d32b7800845771de1224edb42876245f1ae730323481353600a6f6
secretnetwork_1.26.0_MAINNET_goleveldb_amd64_ubuntu-24.04.deb	b38ebe3dfc54e236519751fe23962edd25eb2d3ba9bfbd6eab86ad3315534a8b