Skip to content

Releases: sovrn-tech/sovr-networks

Sovren node v0.24.0

Choose a tag to compare

@sovrntechbot sovrntechbot released this 11 Sep 19:01

Node software for v0.24.0. Binaries are extracted from the container image ghcr.io/sovrn-tech/sovrd:v0.24.0 (sha256:4157fc01ba801531eb50144af509f1fd5c4276472010b849cf3a946e9f5e9e0e); verify with shasum -a 256 -c checksums.txt. Pin the digest, not the tag.

Sovren node v0.23.0

Choose a tag to compare

@cortesoft cortesoft released this 18 Aug 18:34

Sovren node software — v0.23.0

The exact build running on sovr-1 mainnet. Provenance is verifiable: these artifacts were
extracted from the container image sha256:2d2fbb8f48986b5ced9ca01ad515b41e5c34844ef43ba77ceb252ab938ecb396
the digest every mainnet node runs — not rebuilt.

Asset What
sovrd-v0.23.0-linux-amd64 The chain daemon (linux/amd64). sovrd versionv0.23.0
libwasmvm.x86_64.so Required. sovrd links against it dynamically — place it on the library path (e.g. /usr/local/lib, then ldconfig)
checksums.txt SHA-256 of both

Host requirements: linux/amd64, glibc ≥ 2.36 (Debian 12 or newer).

Container image

The same build as an image: ghcr.io/sovrn-tech/sovrd:v0.23.0 — digest
sha256:2d2fbb8f48986b5ced9ca01ad515b41e5c34844ef43ba77ceb252ab938ecb396, byte-identical to what
mainnet runs. Pin the digest, not the tag.

Verify

shasum -a 256 -c checksums.txt

# reproduce the binary from the image yourself:
docker create --name x ghcr.io/sovrn-tech/sovrd@sha256:2d2fbb8f48986b5ced9ca01ad515b41e5c34844ef43ba77ceb252ab938ecb396
docker cp x:/usr/local/bin/sovrd ./sovrd-from-image && docker rm x
shasum -a 256 sovrd-from-image   # must equal the value in checksums.txt

Joining the network

Genesis (checksum-pinned) and peers are in this repository: mainnet/joining.md.
The mainnet chain is sovr-1; the applied upgrade history is on-chain
(/cosmos/upgrade/v1beta1/applied_plan/v0.23.0-combined → height 1356994).