Skip to main content
You need a machine that meets the system requirements and the version you are installing from the Versions page. At the end you have a gaiad binary (or image) that reports v28.3.1 and that you have verified against the release signature or built yourself. All three options are equal. Pick the one that fits how you run servers.

Pick the version first

Install the current mainnet release tag, not the newest tag. Release candidates (-rc) are for the testnet.
On 2026-10-15 this printed v28.3.1. The examples below use that tag. Replace it if the chain has moved on.

Install

Each gaia release ships gaiad-linux-amd64.tar.gz and gaiad-darwin-amd64.tar.gz, a detached GNU Privacy Guard (GPG) signature (.asc) for each, and SHA256SUMS-<tag>.txt. The release is signed with the Cosmos release key, fingerprint E625 9F16 9C7B 913D BB75 DE02 5395 305D 29B8 8B32, published in the cosmos/security repository. There is no arm64 Linux binary. Use the source build on arm64.Import the release key once:
The fingerprint printed must match the one above. If it does not, stop. Do not install.Download the tarball, its signature, and the checksum file:
Verify the signature, then the checksum:
Expect Good signature from "Cosmos-Release <nodes@cosmoslabs.io>" from gpg --verify and ./gaiad-linux-amd64/gaiad: OK from sha256sum --check. A warning that the key is not certified is normal for a key you imported directly. A BAD signature line is not, and Can't check signature: No public key means the import did not reach the keyring gpg uses. On macOS use shasum -a 256 --check --ignore-missing.Install the binary where your service user can run it:
The install command copies the file and sets the mode in one step, and /usr/local/bin is on PATH for every user, including the service user on Run gaiad as a service.

Verify

Expected for the current release:
The commit is the git commit of the tag and is the same for every install method. It is the line to compare. The version line reads v28.3.1 for the release tarball and a source build at the tag. It reads HEAD-b7f8b81bd4bd3df697d484cbb5577c1382435243 for the container image. The build_tags line reads netgo,ledger for a source build. It reads netgo,muslc for the Linux release tarball and the container image, which are static musl builds without Ledger support. The go line shows the toolchain the binary was built with. A source build with a later 1.25 patch shows that patch instead of 1.25.7. For the container image, run the same command with docker run --rm --entrypoint gaiad ghcr.io/cosmos/gaia:v28.3.1 version --long.

Build tags

Next

Join mainnet to initialize and sync the node, or Join testnet to practice first. To run against a fork of the Cosmos SDK, add a replace directive to go.mod (go mod edit -replace github.com/cosmos/cosmos-sdk=../cosmos-sdk && go mod tidy) before make install.