Skip to content

Safrochain v0.3.0

Latest

Choose a tag to compare

@github-actions github-actions released this 16 Nov 10:31
· 10 commits to main since this release

Security and stability release for safrochain-1. State-machine breaking: it is activated by the software-upgrade plan v0.3.0 at block 4,557,100 (about Wednesday 18 November 2026, 14:00 UTC).

Upgrade guide for validators and node operators: https://docs.safrochain.com/governance/mainnet-upgrade-v0.3.0

What is upgraded

Component v0.2.2 v0.3.0
Cosmos SDK v0.50.14 v0.50.15
CometBFT v0.38.21 v0.38.26
CosmWasm wasmd / wasmvm v0.54.1 / v2.2.4 v0.54.11 / v2.2.10
ibc-go v8.7.0 v8.8.0
Go toolchain 1.25.8 1.26.11
  • At the upgrade height the block gas limit (max_gas) is set to 100,000,000 (it is unlimited today). No other mainnet parameter changes and no store migration.
  • Patched indirect dependencies (gRPC, golang.org/x/net, golang.org/x/crypto, go-jose, OpenTelemetry and others).
  • Security fixes in Safrochain modules. As is standard for security releases, the detailed notes and the advisories are published after the upgrade is live.
  • MAX_WASM_SIZE is no longer read from the environment: remove it from your service files.

Install

Build from source

git clone https://github.com/Safrochain-Org/safrochain-node.git
cd safrochain-node && git checkout v0.3.0
make build                       # Go 1.26.11, fetched automatically by Go >= 1.21
./bin/safrochaind version --long | grep -E '^(version|commit|go):'
./bin/safrochaind query wasm libwasmvm-version   # 2.2.10

Release binaries

Statically linked, built by CI from this tag. Mirror: https://rpc1.safrochain.network/binaries/v0.3.0/

File SHA-256
safrochaind-v0.3.0-linux-amd64 c5b8ee22cf51e702d8c9a0b6291ab00f4cda7cb3fceecaacdbd10fba3a217abd
safrochaind-v0.3.0-linux-arm64 dd9952cbb7ce5bc43708def067d66fe43218aa1cfbe0b517d61cf24f83392763
sha256sum -c --ignore-missing SHA256SUMS

Cosmovisor

Stage the binary at cosmovisor/upgrades/v0.3.0/bin/safrochaind (the directory name is the plan name v0.3.0). Do not run v0.3.0 before the upgrade height and do not keep v0.2.2 after it.