How zeta-chain/node works
Project type and purpose
• ZetaChain is a monorepo for an EVM-compatible L1 blockchain built on Cosmos SDK + Ethermint (the “core chain”) plus a specialized “observer/signer” client (ZetaClient) that relays and signs cross-chain transactions, and auxiliary components (JSON-RPC server, CLI tools, E2E test harness, TS SDK).
High-level system components
a. Core Blockchain Node (“zetacored”)
• Cosmos SDK application (Go) exposing ABCI to Tendermint Core
• EVM module (Ethermint fork) + precompiles for native cross-chain operations
• Modular Cosmos SDK modules under x/ (authority, crosschain, observer, lightclient, emissions, fungible, ibccrosschain, etc.)
• gRPC & REST gateways for chain APIs
• Protobuf definitions (proto/zetachain/…) driving codegen
b. Observer/Signer Client (“zetaclientd”)
• Multi-chain observer services for Bitcoin, EVM, Solana, Sui, TON
• Signer components for cross-chain message authorization (TSS)
• Relayer logic: polls external chains → constructs ZetaCore transactions → submits via gRPC or CLI
c. JSON-RPC & Indexer Server (“server/”)
• Ethereum-compatible JSON-RPC namespaces and websockets (rpc/ and server/)
• Indexer service for chain data (blocks, txs) to support RPC methods
d. CLI Tools & Scripts
• Command-line binaries (zetacored, zetaclientd, zetatool) under cmd/
• Makefile, Dockerfiles, buf, codegen and release scripts
e. E2E Test Harness (e2e/)
• Docker-based localnet orchestration (contrib/localnet)
• Go-based E2E test runner interacting with all chain components
f. TypeScript SDK (typescript/)
• Generated TypeScript definitions from Protobuf + helper APIs
Component Interactions and Data Flows
• Tendermint Core <-ABCI-> Zetacored (Cosmos SDK app)
• Zetacored <-gRPC/REST-> CLI tools (zetacored CLI), ZetaClient submission
• Zetacored <-gRPC-> ZetaClient for transaction submission and query
• ZetaClient <-RPC-> External Chains (Bitcoin RPC, EVM JSON-RPC, Solana RPC, Sui/MVM, TON Lite API)
• ZetaClient (TSS) → multisig services (for cross-chain consensus)
• Server JSON-RPC <-> Zetacored (block and tx indexing) → clients (web3 UIs, scripts)
• E2E runner orchestrates containers for all above, drives tests
Architectural patterns & design principles
• Modular Cosmos SDK: each domain in x/ is a plug-in module (separation of concerns)
• Microservice for cross-chain observation & signing (ZetaClient)
• Adapter pattern: per-chain RPC adapters under zetaclient/chains/*
• Codegen from Protobuf for type safety across Go, TS, gRPC, OpenAPI
• CI pipeline with GitHub Actions for build, tests, releases