Downloads

Run Genesis yourself.

Everything is open source and builds from the repository. Versioned public downloads with checksums ship with the public testnet, until then, clone and build.

01

Chrome extension

A working build of the wallet extension is produced in every release. It connects to the live devnet (genesisdev-1), derives eth_secp256k1 keys, and signs SIGN_MODE_DIRECT transactions that the chain accepts.

  1. Clone the repo and install the extension toolchain.
  2. Run the extension build to produce the Chrome MV3 bundle.
  3. Load the unpacked extension from chrome://extensions (Developer mode → Load unpacked).

A published listing (Chrome Web Store, unlisted) is planned for the public testnet phase. Until then the bundle loads from source.

02

Node binary

The chain ships as the genesisd binary (Cosmos SDK + CometBFT). On Windows, the desktop app installs a node as a background service; Linux ships a tarball. genesisctl verifies operator logins with the same on-chain identity.

  1. Windows: build the package (node/win/scripts/build.ps1) and run genesis-node install.
  2. Linux: build the tarball (node/linux/build.sh), then install.sh.
  3. Build the binary directly: go build -o build/genesisd ./cmd/genesisd.

Versioned release artifacts and checksums for Linux/macOS/Windows are on the roadmap for the public testnet. Today, builds come from the repository.

03

Explorer

The block explorer + burn indexer runs against the live devnet, exposing blocks, ERC-20 token pairs, lineage birth certificates, and the burn ledger.

  1. Run the explorer locally, pointed at the devnet RPC and indexer.
  2. Or browse the deployed instance when testnet opens to the public.

Currently served from the dev environment; public hosting ships with the testnet.

Testnet/devnet funds are minted for development only. Genesis Protocol tokens do not exist and are not sold.

Read legal