ZetaChain

https://github.com/zeta-chain/node
Admin
ZetaChain is an EVM-compatible L1 blockchain enabling omnichain, generic smart contracts and...
Tokens:46,383
Snippets:169
Trust Score:9.6
License:MIT
Update:1 year ago
Show doc for...
Tokens:
Raw
### Run Monitoring Setup

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/LOCAL_TESTING.md

Starts the monitoring setup, which includes Grafana dashboards. Requires the Zetacore API to be accessible at http://localhost:1317 and allows adding additional ETH addresses to monitor.

```makefile
make start-monitoring

```

--------------------------------

### ZetaTool Installation

Source: https://github.com/zeta-chain/node/blob/develop/docs/cli/zetatool/readme.md

Instructions for installing the ZetaTool utility on the target system.

```bash
make install-zetatool
```

--------------------------------

### Install zetae2e CLI

Source: https://github.com/zeta-chain/node/blob/develop/cmd/zetae2e/README.md

Command to install the zetae2e CLI tool.

```go
make install-zetae2e

zetae2e -h
```

--------------------------------

### Manage Ethereum Node (Mainnet)

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/DEPLOY_NODES.md

Commands for starting, stopping, and cleaning the Ethereum node on the ZetaChain mainnet. These commands interact with Docker Compose configurations located in `contrib/rpc/ethereum`.

```bash
make start-eth-node-mainnet
```

```bash
make stop-eth-node-mainnet
```

```bash
make clean-eth-node-mainnet
```

--------------------------------

### Zeta Chain Node Initialization and Execution

Source: https://github.com/zeta-chain/node/blob/develop/contrib/rpctest/README.txt

This snippet outlines the sequence of shell commands to initialize and run the Zeta Chain node. It includes running setup scripts and the main Go application.

```bash
#!/bin/bash

# Initialize the node
./init.sh

# Run the node
./run.sh

# In another window, set up the environment and note the transaction block number
# ./setup.sh
# <note the block number from the output of setup.sh>

# Run the main application with the captured block number
# go run main.go <blocknum>
```

--------------------------------

### Manage Zetacored Nodes (Mainnet)

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/DEPLOY_NODES.md

Commands for starting, stopping, and cleaning Zetacored nodes on the ZetaChain mainnet. These commands interact with Docker Compose configurations located in `contrib/rpc/zetacored`.

```bash
make start-mainnet-zetarpc-node DOCKER_TAG=ubuntu-v14.0.1
```

```bash
make stop-mainnet-zetarpc-node
```

```bash
make clean-mainnet-zetarpc-node
```

--------------------------------

### zetae2e Configuration Example

Source: https://github.com/zeta-chain/node/blob/develop/cmd/zetae2e/README.md

Example configuration file for zetae2e, detailing connections to ZetaChain, EVM, and Bitcoin networks, along with contract addresses.

```yaml
zeta_chain_id: "athens_7001-1"
default_account:
  evm_address: "<your evm address>"
  private_key: "<your evm private key>"
rpcs:
  zevm: "<zevm (ZetaChain) url>, generally using port 8545"
  evm: "<evm url>, generally using port 8545"
  bitcoin:
    host: "<bitcoin rpc url>"
    user: "<bitcoin user>"
    pass: "<bitcoin pass>"
    http_post_mode: true
    disable_tls: true
    params: "<mainnet|testnet3|regnet>"
  zetacore_grpc: "<ZetaChain grpc url>, generally using port 9090"
  zetacore_rpc: "<ZetaChain grpc url>, generally using port 26657"
contracts:
  zevm:
    system_contract: "0xEdf1c3275d13489aCdC6cD6eD246E72458B8795B"
    eth_zrc20: "0x13A0c5930C028511Dc02665E7285134B6d11A5f4"
    erc20_zrc20: "0x0cbe0dF132a6c6B4a2974Fa1b7Fb953CF0Cc798a"
    btc_zrc20: "0x65a45c57636f9BcCeD4fe193A602008578BcA90b"
    uniswap_factory: "0x9fd96203f7b22bCF72d9DCb40ff98302376cE09c"
    uniswap_router: "0x2ca7d64A7EFE2D62A725E2B35Cf7230D6677FfEe"
  evm:
    zeta_eth: "0x0000c304d2934c00db1d51995b9f6996affd17c0"
    connector_eth: "0x00005e3125aba53c5652f9f0ce1a4cf91d8b15ea"
    custody: "0x000047f11c6e42293f433c82473532e869ce4ec5"
    erc20: "0x07865c6e87b9f70255377e024ace6630c1eaa37f"
```

--------------------------------

### Setup Bitcoin for zetae2e

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/LOCAL_TESTING.md

Initializes the Bitcoin account for use with the zetae2e CLI on the local network.

```bash
zetae2e setup-bitcoin cmd/zetae2e/config/local.yml
```

--------------------------------

### Manage Zetacored Nodes (Testnet Athens3)

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/DEPLOY_NODES.md

Commands for starting, stopping, and cleaning Zetacored nodes on the ZetaChain Athens3 testnet. These commands interact with Docker Compose configurations located in `contrib/rpc/zetacored`.

```bash
make start-testnet-zetarpc-node DOCKER_TAG=ubuntu-v14.0.1
```

```bash
make stop-testnet-zetarpc-node
```

```bash
make clean-testnet-zetarpc-node
```

--------------------------------

### Manage Zetacored Nodes (Testnet Athens3 Local Build)

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/DEPLOY_NODES.md

Commands for starting, stopping, and cleaning Zetacored nodes when using a local build for the Athens3 testnet. These commands interact with Docker Compose configurations located in `contrib/rpc/zetacored`.

```bash
make start-zetacored-rpc-testnet-localbuild
```

```bash
make stop-zetacored-rpc-testnet-localbuild
```

```bash
make clean-zetacored-rpc-testnet-localbuild
```

--------------------------------

### Start ZetaChain Localnet

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/LOCAL_TESTING.md

Command to start the ZetaChain local network. The localnet may take a few minutes to initialize.

```bash
make start-localnet
```

--------------------------------

### Manage Zetacored Nodes (Mainnet Local Build)

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/DEPLOY_NODES.md

Commands for starting, stopping, and cleaning Zetacored nodes when using a local build for the mainnet. These commands interact with Docker Compose configurations located in `contrib/rpc/zetacored`.

```bash
make start-zetacored-rpc-mainnet-localbuild
```

```bash
make stop-zetacored-rpc-mainnet-localbuild
```

```bash
make clean-zetacored-rpc-mainnet-localbuild
```

--------------------------------

### Setup Bitcoin Node for zetae2e

Source: https://github.com/zeta-chain/node/blob/develop/cmd/zetae2e/README.md

Command to set up a Bitcoin node for local testing with zetae2e. This is for local testing only.

```go
zetae2e setup-bitcoin [config]
```

--------------------------------

### Build ZetaChain Binaries

Source: https://github.com/zeta-chain/node/blob/develop/readme.md

Builds thezetacored and zetaclientd binaries for ZetaChain. Installs them in the $GOPATH/bin directory. After building, verify the versions match the release tag.

```bash
make install
zetacored version
zetaclientd version
```

--------------------------------

### Start ZetaNode Docker Image

Source: https://github.com/zeta-chain/node/blob/develop/contrib/localnet/README.md

Builds the zetanode Docker image. This command should be executed at the root of the repository.

```shell
make zetanode
```

--------------------------------

### Start Localnet with Docker Compose

Source: https://github.com/zeta-chain/node/blob/develop/contrib/localnet/README.md

Starts the local ZetaChain network using Docker Compose. This command brings up all defined services in detached mode.

```docker-compose
docker-compose up -d
```

--------------------------------

### Stop Monitoring Setup

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/LOCAL_TESTING.md

Stops the monitoring setup.

```makefile
make stop-monitoring

```

--------------------------------

### Database Statistics JSON Output Example

Source: https://github.com/zeta-chain/node/blob/develop/docs/cli/zetatool/db_stats.md

An example of the JSON output from the `zetatool db-stats` command, showing a breakdown of database statistics by module.

```json
{
  "totalKeys": 564492,
  "totalKeySize": 13540693,
  "totalValSize": 41652535,
  "modules": {
    "acc": {
      "count": 51796,
      "totalKeySize": 1087716,
      "totalValSize": 3868440,
      "avgKeySize": 21,
      "avgValSize": 74
    },
    "authority": {
      "count": 4363,
      "totalKeySize": 117801,
      "totalValSize": 59315,
      "avgKeySize": 27,
      "avgValSize": 13
    },
    "authz": {
      "count": 4389,
      "totalKeySize": 100947,
      "totalValSize": 61607,
      "avgKeySize": 23,
      "avgValSize": 14
    },
    "bank": {
      "count": 240816,
      "totalKeySize": 5297952,
      "totalValSize": 15499972,
      "avgKeySize": 22,
      "avgValSize": 64
    },
    "consensus": {
      "count": 4359,
      "totalKeySize": 117693,
      "totalValSize": 56754,
      "avgKeySize": 27,
      "avgValSize": 13
    },
    "crisis": {
      "count": 4359,
      "totalKeySize": 104616,
      "totalValSize": 56672,
      "avgKeySize": 24,
      "avgValSize": 13
    },
    "crosschain": {
      "count": 42507,
      "totalKeySize": 1190196,
      "totalValSize": 5299249,
      "avgKeySize": 28,
      "avgValSize": 124
    },
    "distribution": {
      "count": 57523,
      "totalKeySize": 1725690,
      "totalValSize": 3691463,
      "avgKeySize": 30,
      "avgValSize": 64
    },
    "emissions": {
      "count": 4584,
      "totalKeySize": 123768,
      "totalValSize": 94185,
      "avgKeySize": 27,
      "avgValSize": 20
    },
    "evidence": {
      "count": 4359,
      "totalKeySize": 113334,
      "totalValSize": 0,
      "avgKeySize": 26,
      "avgValSize": 0
    },
    "evm": {
      "count": 7395,
      "totalKeySize": 155295,
      "totalValSize": 575876,
      "avgKeySize": 21,
      "avgValSize": 77
    },
    "feemarket": {
      "count": 13077,
      "totalKeySize": 353079,
      "totalValSize": 610134,
      "avgKeySize": 27,
      "avgValSize": 46
    },
    "fungible": {
      "count": 4387,
      "totalKeySize": 114062,
      "totalValSize": 60447,
      "avgKeySize": 26,
      "avgValSize": 13
    },
    "gov": {
      "count": 4439,
      "totalKeySize": 93219,
      "totalValSize": 64217,
      "avgKeySize": 21,
      "avgValSize": 14
    },
    "group": {
      "count": 4363,
      "totalKeySize": 100349,
      "totalValSize": 56782,
      "avgKeySize": 23,
      "avgValSize": 13
    },
    "lightclient": {
      "count": 4359,
      "totalKeySize": 126411,
      "totalValSize": 56745,
      "avgKeySize": 29,
      "avgValSize": 13
    },
    "misc": {
      "count": 4360,
      "totalKeySize": 25055,
      "totalValSize": 4660205,
      "avgKeySize": 5,
      "avgValSize": 1068
    },
    "observer": {
      "count": 7939,
      "totalKeySize": 206414,
      "totalValSize": 488021,
      "avgKeySize": 26,
      "avgValSize": 61
    },
    "params": {
      "count": 4359,
      "totalKeySize": 104616,
      "totalValSize": 0,
      "avgKeySize": 24,
      "avgValSize": 0
    },
    "slashing": {
      "count": 13505,
      "totalKeySize": 351130,
      "totalValSize": 955079,
      "avgKeySize": 26,
      "avgValSize": 70
    },
    "staking": {
      "count": 72851,
      "totalKeySize": 1821275,
      "totalValSize": 5379169,
      "avgKeySize": 25,
      "avgValSize": 73
    },
    "upgrade": {
      "count": 4403,
      "totalKeySize": 110075,
      "totalValSize": 58203,
      "avgKeySize": 25,
      "avgValSize": 13
    }
  }
}
```

--------------------------------

### E2E Test Configuration Example

Source: https://github.com/zeta-chain/node/blob/develop/e2e/README.md

YAML configuration file structure for E2E tests, defining RPC endpoints and smart contract addresses.

```yaml
rpcs:
  zevm: "http://localhost:8545"
  evm: "http://localhost:8546"
  bitcoin: "http://localhost:18332"
  zetacore_grpc: "localhost:9090"
  zetacore_rpc: "http://localhost:26657"
contracts:
  evm:
    zeta_eth: "0x..."
    connector_eth: "0x..."
    erc20: "0x..."
zeta_chain_id: "zetachain-1"
```

--------------------------------

### Run E2E Tests

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/LOCAL_TESTING.md

Starts the localnet and runs standard end-to-end tests using Docker Compose. Supports various configurations via environment variables like LOCALNET_MODE, E2E_ARGS, and NODE_COMPOSE_ARGS.

```makefile
make start-e2e-test

```

```bash
export E2E_ARGS='--verbose --test-filter eth_deposit|eth_withdraw'
make start-e2e-test

```

```bash
export NODE_COMPOSE_ARGS="--profile monitoring -f docker-compose-persistent.yml"
make start-e2e-test

```

--------------------------------

### Example Usage of TON Transaction Scraper

Source: https://github.com/zeta-chain/node/blob/develop/pkg/contracts/ton/testdata/readme.md

Demonstrates how to use the TON transaction scraper with the testnet enabled. The command fetches transaction data for a specific address, logical time, and hash, and pipes the JSON output to `jq` for formatted display.

```sh
go run pkg/contracts/ton/testdata/scraper.go -testnet \
    kQCZfYicgVrqwhxH-Grg44OD78PDRjBnWC9iY61IxaFIW77M \
    26023788000003 \
    cbd6e2261334d08120e2fef428ecbb4e7773606ced878d0e6da204f2b4bf42bf | jq
```

--------------------------------

### List Current Authorizations

Source: https://github.com/zeta-chain/node/blob/develop/docs/releases/v19_observer_migration.md

Lists the current authorization grants for a given grantee address using the zetacored CLI.

```bash
zetacored q authz grants-by-grantee [operator_address]
```

--------------------------------

### zetae2e Commands

Source: https://github.com/zeta-chain/node/blob/develop/cmd/zetae2e/README.md

Demonstrates various commands available in the zetae2e CLI tool for checking balances, Bitcoin addresses, listing tests, and running tests.

```go
zetae2e balances [config]
zetae2e bitcoin-address [config]
zetae2e list-tests
zetae2e run zeta_deposit:2000000000000000000 eth_deposit:2000000000000000000 erc20_deposit:200000 --config cmd/zetae2e/config/local.yml --verbose
```

--------------------------------

### Zetaclient TSS Architecture

Source: https://github.com/zeta-chain/node/blob/develop/zetaclient/tss/readme.md

Illustrates the high-level architecture of the TSS implementation within Zetaclient, showing the interaction between zetaclientd, the TSS Service, go-tss Server, and libp2p.

```text
zetaclientd(
    tss.Service(
        gotss.Server(libp2p()) 
    )
)
```

--------------------------------

### Run zetae2e Test Scenario

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/LOCAL_TESTING.md

Executes a specific end-to-end test scenario using the zetae2e CLI, specifying deposit amounts and configuration.

```bash
zetae2e run zeta_deposit:2000000000000000000 eth_deposit:2000000000000000000 erc20_deposit:200000 --config cmd/zetae2e/config/local.yml
```

--------------------------------

### Generate ZetaChain Source Code

Source: https://github.com/zeta-chain/node/blob/develop/readme.md

Generates Go files from protocol buffer files using buf, moves them to the correct directories, and creates an OpenAPI spec. It also updates module documentation by analyzing protocol buffer files and source code for message handlers.

```bash
make generate
```

--------------------------------

### E2E Test Debugging Script

Source: https://github.com/zeta-chain/node/blob/develop/e2e/README.md

Shell script to debug specific E2E tests using Delve. Requires Delve installation and IDE configuration.

```shell
./e2e/scripts/debug.sh my_test_name arg1 arg2 arg_n
```

--------------------------------

### Initialize Swagger UI

Source: https://github.com/zeta-chain/node/blob/develop/docs/openapi/openapi.html

Initializes the Swagger UI interface for visualizing the OpenAPI specifications. It loads the API definition from './openapi.swagger.yaml' and configures various UI options for a comprehensive API exploration experience.

```javascript
window.onload = function() { window.ui = SwaggerUIBundle({
  url: "./openapi.swagger.yaml",
  dom_id: "#swagger-ui",
  deepLinking: true,
  layout: "BaseLayout",
  showExtensions: true,
  showCommonExtensions: true,
  defaultModelExpandDepth: 5
}); }
```

--------------------------------

### Build zetanode

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/LOCAL_TESTING.md

Builds the zetanode Docker image. Rebuild this image if the zetacored or zetaclientd code is updated.

```makefile
make zetanode

```

```bash
docker build -t zetanode .

```

--------------------------------

### Create New Release Branch

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/RELEASES.md

Commands to create a new release branch from the develop branch and push it to origin. This is the starting point for a new major release.

```bash
git fetch
git checkout -b release/v15 origin/develop
git push origin release/v15
```

--------------------------------

### E2E Tests: Governance Proposal Execution

Source: https://github.com/zeta-chain/node/blob/develop/e2e/TESTING_GUIDE.md

Instructions for executing governance proposals in E2E tests. Proposals can be run at the start or end of tests by placing JSON files in specific directories.

```shell
Place proposal JSON in: contrib/localnet/orchestrator/proposal_e2e_start (for execution before tests)
Place proposal JSON in: contrib/localnet/orchestrator/proposal_e2e_end (for execution after tests)
```

--------------------------------

### Grant Authorizations for New Messages

Source: https://github.com/zeta-chain/node/blob/develop/docs/releases/v19_observer_migration.md

Grants authorization for new cross-chain message types using the zetacored CLI. Observers must execute these commands to update their authorizations for V19.

```bash
zetacored tx authz grant [grantee_address] generic --msg-type=/zetachain.zetacore.crosschain.MsgVoteInboundzetacored tx authz grant [grantee_address] generic --msg-type=/zetachain.zetacore.crosschain.MsgVoteOutboundzetacored tx authz grant [grantee_address] generic --msg-type=/zetachain.zetacore.crosschain.MsgAddOutboundTrackerzetacored tx authz grant [grantee_address] generic --msg-type=/zetachain.zetacore.crosschain.MsgAddInboundTracker
```

--------------------------------

### Sample Failed Deposit Error Message

Source: https://github.com/zeta-chain/node/blob/develop/docs/zetacore/status_message.md

An example JSON payload representing a failed deposit transaction. This sample illustrates the structure and content of an error message when a contract call fails during an EVM operation.

```json
{
  "type": "contract_call_error",
  "message": "contract call failed when calling EVM with data",
  "method": "depositAndCall0",
  "contract": "0x733aB8b06DDDEf27Eaa72294B0d7c9cEF7f12db9",
  "args": "[ {[]0xdFb74337c53141bf912101b0Ee770FA8e2DCB921 1337} 0x13A0c5930C028511Dc02665E7285134B6d11A5f410000000000000000 0xD28D6A0b8189305551a0A8bd247a6ECa9CE781Ca [114 101 118 101114 116]]",
  "error": "execution reverted: ret 0x: evm transaction execution failed"
}
```

--------------------------------

### Check Localnet Balances with zetae2e

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/LOCAL_TESTING.md

Retrieves the balances of accounts on the local network using the zetae2e CLI.

```bash
zetae2e balances cmd/zetae2e/config/local.yml
```

--------------------------------

### Retrieve TON Transactions via TON Center API

Source: https://github.com/zeta-chain/node/blob/develop/zetaclient/chains/ton/readme.md

Fetches transaction data from the TON network using the TON Center v2 API. This example demonstrates how to query transactions for a specific address with pagination and filtering, then parses the result using `jq`.

```sh
curl -s \
  'https://testnet.toncenter.com/api/v2/getTransactions?address=0%3A87115e4a012e747d9bce013ce2244010c6d5e3b0f88ddbc63420519b8619e5a0&limit=1&lt=36905041000001&hash=a0a423d045e3b4099e28957eff5a9f893f69edd649a82fb35154b76770961812&to_lt=0&archival=false' \
  -H 'accept: application/json' | jq '.result[0]'
```

--------------------------------

### ZetaClient Log Structure Overview

Source: https://github.com/zeta-chain/node/blob/develop/docs/zetaclient/zetaclient_logging.md

Illustrates the hierarchical structure of the MasterLogger in ZetaClient, showing how logs are organized by module and chain type (e.g., BTC, EVM). This helps in understanding the origin and context of log messages.

```go
// MasterLogger
//   StartupLogger: module = `Startup`
//   ZetaChainLogger
//     ChainLogger: chain = `ZetaChain`
//       ZetaChainWatcher: chain = `ZetaChain` module = `ZetaChainWatcher`
//   BTCLogger
//     ChainLogger: chain = `BTC`
//       WatchInbound: chain = `BTC` module = `WatchInbound`
//       WatchGasPrice: chain = `BTC` module = `WatchGasPrice`
//       ObserverOutbound: chain = `BTC` module = `ObserveOutbound`
//       WatchUTXOs: chain = `BTC` module = `WatchUTXOs`
//   EVMLoggers (Individual sections for each EVM Chain)
//     ChainLogger: chain = `evm_chain_name`
//       BuildBlockIndex: chain = `evm_chain_name` module = `BuildBlockIndex`
//       ExterrnalChainWatcher: chain = `evm_chain_name` module = `ExternalChainWatcher`
//       WatchGasPrice: chain = `evm_chain_name` module = `WatchGasPrice`
//       ObserverOutbound: chain = `evm_chain_name` module = `ObserveOutbound`
//   BTCSigner: chain = `BTC` module = `BTCsigner`
//     ProcessOutTX: chain = `BTC` module = `BTCsigner` OutboundId = `OutboundID of cctx being signed` SendHash = `Index of cctx being signed`
//   EVMSigner: chain = `evm_chain_name` module = `EVMSigner`
//     ProcessOutTX: chain = `evm_chain_name` module = `BTCsigner` OutboundId = `OutboundID of cctx being signed` SendHash = `Index of cctx being signed`
```

--------------------------------

### Run Upgrade Tests

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/LOCAL_TESTING.md

Performs upgrade tests by running E2E tests with an older version, upgrading nodes to a new version, and then running E2E tests again. Requires specifying OLD_VERSION and NEW_VERSION.

```makefile
make start-upgrade-test

```

```makefile
make start-upgrade-test-light

```

--------------------------------

### ZetaClient Log Levels

Source: https://github.com/zeta-chain/node/blob/develop/docs/zetaclient/zetaclient_logging.md

Defines the available log levels for the zetaclientd daemon, ranging from TRACE to PANIC, with descriptions of their use cases. These levels are configured via the --log-level flag during initialization.

```go
const (
	TRACE int = -1
	DEBUG int = 0
	INFO  int = 1
	WARNING int = 2
	ERROR int = 3
	FATAL int = 4
	PANIC int = 5
)
```

--------------------------------

### Run Import and Run Simulation Test

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/SIMULATION_TESTING.md

This test simulates the application, exports its state, and then imports that state into a subsequent simulation. The primary goal is to verify the import process and its impact on the application's state. The estimated runtime is 2 minutes.

```bash
make test-sim-after-import
```

--------------------------------

### Run TON Transaction Scraper

Source: https://github.com/zeta-chain/node/blob/develop/pkg/contracts/ton/testdata/readme.md

Executes the TON transaction scraper tool. It requires an address, logical time (lt), and hash. The `--testnet` flag can be used to specify the testnet. The output can be piped to `jq` for pretty-printing.

```sh
go run pkg/contracts/ton/testdata/scraper.go <address> <lt> <hash> [--testnet]
```

--------------------------------

### Access ZetaCore Node CLI

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/LOCAL_TESTING.md

Executes a command to access the zetacore0 Docker container, allowing direct interaction with the ZetaCore node CLI.

```bash
docker exec -it zetacore0 sh
```

--------------------------------

### Run Import Export Simulation Test

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/SIMULATION_TESTING.md

Performs a full application simulation, exports the application state, and then imports this state into a new simulation. It compares the application state keys between the two simulations to ensure data consistency. This test typically takes around 2 minutes.

```bash
make test-sim-import-export
```

--------------------------------

### Run Full Application Simulation Test

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/SIMULATION_TESTING.md

Conducts a comprehensive simulation of the entire blockchain application using a specified configuration. It attempts to export the genesis state at the end of the simulation to verify the export functionality. The approximate run time is 2 minutes.

```bash
make test-sim-full-app
```

--------------------------------

### Send Transaction on EVM with cast

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/LOCAL_TESTING.md

Uses the cast CLI to send a transaction on the local EVM, specifying the recipient, value, RPC URL, and private key.

```bash
cast send 0x9fd96203f7b22bCF72d9DCb40ff98302376cE09c --value 42 --rpc-url http://0.0.0.0:8545 --private-key "d87baf7bf6dc560a252596678c12e41f7d1682837f05b29d411bc3f78ae2c263"
```

--------------------------------

### Query ZetaCore Bank Balances

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/LOCAL_TESTING.md

Performs a bank balance query on the ZetaCore node for a given Zeta address.

```bash
zetacored q bank balances zeta1amcsn7ja3608dj74xt93pcu5guffsyu2xfdcyp
```

--------------------------------

### MsgDeploySystemContracts

Source: https://github.com/zeta-chain/node/blob/develop/docs/spec/generated.md

Deploys new instances of the system contracts. This action is authorized for admin policy group 2.

```proto
message MsgDeploySystemContracts {
	string creator = 1;
}
```

--------------------------------

### Execute Governance Proposal Script

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/LOCAL_TESTING.md

Command to execute a script within the zetacore0 Docker container that generates and manages localnet governance proposals.

```bash
docker exec -it zetacore0 bash
/root/test-gov-proposals.sh
```

--------------------------------

### ZetaTool CLI Commands

Source: https://github.com/zeta-chain/node/blob/develop/docs/cli/zetatool/readme.md

Provides core functionalities for interacting with Zetachain data. Includes fetching ballot identifiers, tracking cctx status, and database statistics.

```bash
zetatool get-ballot --inbound-hash <inbound_hash> --chain-id <chain_id>
zetatool track-cctx --inbound-hash <inbound_hash> --chain-id <chain_id>
zetatool db-stats
```

--------------------------------

### Check EVM Account Balance with cast

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/LOCAL_TESTING.md

Uses the cast CLI to check the balance of an Ethereum account connected to the local EVM RPC endpoint.

```bash
cast balance 0xE5C5367B8224807Ac2207d350E60e1b6F27a7ecC --rpc-url http://0.0.0.0:8545
```

--------------------------------

### Run Stress Tests

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/LOCAL_TESTING.md

Executes end-to-end tests with a larger number of nodes and clients to assess network performance and stress the network with numerous cross-chain transactions.

```makefile
make start-stress-test

```

--------------------------------

### Show Application Database Statistics

Source: https://github.com/zeta-chain/node/blob/develop/docs/cli/zetatool/db_stats.md

Displays detailed statistics about the application's database, such as total keys, key sizes, value sizes, and module-specific metrics. Requires the path to the database file and allows specifying the output format.

```shell
zetatool db-stats --dbpath [pathToApplicationDb] --format [json|table]
```

--------------------------------

### Zetaclient Password Handling

Source: https://github.com/zeta-chain/node/blob/develop/docs/zetaclient/migration_v12.2-v12.3.md

Zetaclient previously used HOTKEY_PASSWORD and TSS_FRAGMENT_SEED environment variables for password encryption. These are now replaced by interactive prompts during startup for the hot key password and TSS key share password. Users should use their existing passwords if their key files are already encrypted.

```bash
# Environment variables HOTKEY_PASSWORD and TSS_FRAGMENT_SEED are no longer valid.
# Instead, prompts will appear during startup for:
# - Hot Key password
# - TSS Key share password

# For file backend, use the same password as the existing keyring.
# For test backend, leave the password blank.
```

--------------------------------

### TON Observer-Signer Tasks

Source: https://github.com/zeta-chain/node/blob/develop/zetaclient/chains/ton/readme.md

Lists the high-level orchestrator tasks for inbound and outbound TON transactions handled by the ton.go implementation.

```go
check_rpc_status - checks RPC health
post_gas_price - posts gas prices. They rarely change (only by governance proposals).
observe_inbound - scrolls Gateway transactions, detects inbounds, and converts them into votes.
process_inbound_trackers - same as other inbound trackers, but note that the hash here is $logical_time:$hash.
process_outbound_trackers - same as other outbound trackers, but note that the hash here is $logical_time:$hash.
schedule_cctx - lists pending outbound CCTXs, then constructs, signs, and broadcasts the corresponding TON transactions.
```

--------------------------------

### E2ERunner Struct Definition

Source: https://github.com/zeta-chain/node/blob/develop/docs/development/LOCAL_TESTING.md

Defines the E2ERunner struct, which provides access to various clients and authentication objects for interacting with different networks and services during e2e tests.

```go
type E2ERunner struct {
	ZEVMClient   *ethclient.Client
	EVMClient *ethclient.Client
	BtcRPCClient *rpcclient.Client

	CctxClient     crosschaintypes.QueryClient
	FungibleClient fungibletypes.QueryClient
	AuthClient     authtypes.QueryClient
	BankClient     banktypes.QueryClient
	ObserverClient observertypes.QueryClient
	ZetaTxServer   txserver.ZetaTxServer
	
	EVMAuth *bind.TransactOpts
	ZEVMAuth   *bind.TransactOpts
	
	// ...
}
```

--------------------------------

### TON RPC API Overview

Source: https://github.com/zeta-chain/node/blob/develop/zetaclient/chains/ton/readme.md

Provides an overview of the TON Center v2 RPC implementation, which is a JSON API hosted by node providers, used for data access and transaction submission. It highlights the shift from lite-server to this more widely adopted protocol and mentions the pruning period of non-archival nodes.

```APIDOC
TON Center v2 RPC API:

Overview:
TON Center v2 is a JSON API implementation built upon a Python webserver with a lite-client wrapper. It serves as the primary interface for data access and transaction submission in the TON ecosystem, offering a more accessible alternative to the binary lite-server protocol.

Key Features:
- JSON-based API for ease of integration.
- Hosted by node providers, ensuring wider availability.
- Supports data retrieval and transaction submission.

Considerations:
- Pruning Period: Non-archival nodes typically prune transactions after approximately 14 days. This is a critical factor for applications relying on historical transaction data, such as `process_inbound_trackers` and `process_outbound_trackers`.

Reference:
For detailed API types and guidelines, consult the official documentation: https://docs.ton.org/v3/guidelines/dapps/apis-sdks/api-types
```
Tokens:
Raw