Practical overview
When it fits
Use the repository when working directly with ZetaChain node or observer-client software, or when changing and generating artifacts from its protocol-buffer definitions. Consult its linked deployment and testing guides for subsequent operational work.
Who it is for
- Developers modifying ZetaChain’s blockchain modules or protocol-buffer definitions.
- Operators building or running ZetaChain node software and its observer-and-signer client.
- Developers generating the project’s OpenAPI specification and module message documentation.
Documented uses
- Build the `zetacored` and `zetaclientd` binaries from a release tag.
- Operate software that observes the chain, relays messages and performs signing tasks for cross-chain transactions.
- Generate Go files, an OpenAPI specification and message documentation after protocol-buffer changes.
- Develop chain-level smart-contract and cross-chain messaging integrations.
Requirements & limits
The repository is public and lists the MIT license.
- The core chain modules and observer-and-signer client serve different development and operating roles.
- Go 1.23 is the stated build prerequisite; Docker and Docker Compose are optional for local tests.
- Protocol contracts for EVM networks, Solana, TON and Sui are maintained in separate repositories.
- The README links to dedicated guides for node deployment, local and end-to-end testing, and simulation testing.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Build ZetaChain node and client binaries
Build the documented ZetaChain binaries from a checked-out release tag.
Before you start
- Go 1.23
- A cloned repository with a release tag checked out
Steps
Clone the repository and check out the intended release tag.
Run the command below.
make installRun
zetacored versionandzetaclientd versionto check the binaries against the release tag.
Expected outcome
The `zetacored` and `zetaclientd` binaries are installed in `$GOPATH/bin`; their reported versions can be compared with the release tag.
Guide limitations
- This documents building binaries, not deploying a node or configuring the observer-and-signer client.
Regenerate code and API documentation after protocol-buffer changes
Generate Go files, an OpenAPI specification and module message documentation after editing protocol-buffer files.
Before you start
- The repository and edited protocol-buffer files
buffor processing protocol-buffer files
Steps
Make the protocol-buffer changes.
Run the command below.
make generate
Expected outcome
The generation process produces Go files, an OpenAPI specification and module message documentation.
Guide limitations
- The README describes generation after protocol-buffer changes; it does not document API deployment or client integration.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 13 October 2026
- Original website title
- zeta-chain/node · Official homepage title · retained in its source language

