> ## Documentation Index > Fetch the complete documentation index at: https://docs.tavchain.safeney.com/llms.txt > Use this file to discover all available pages before exploring further. # Network files and ports > Verify the 771002 genesis, public peers and observer configuration alongside the unchanged Tavchain node release. Tavchain's network files select native network `tavchaintestnet_771002-1` and EVM chain ID `771002`. For a new node, use the [installation chooser](https://docs.tavchain.safeney.com/tavchain/operate.md). The published Docker image and native bundles include the matching configuration; separate network-file assembly is for the earlier manual client installation. | Setting | Value | | - | - | | EVM chain ID | 771002 (`0xbc3ba`) | | Native chain ID | tavchaintestnet\_771002-1 | | Native asset | Tavcoin (TAV), 18 decimals, base denomination atav | | Genesis SHA-256 | a101ab9ccf1478757af8a69d832548ea1167e552fe6d6ef6621a77447a54e924 | | Support | [support@safeney.com](mailto:support@safeney.com) | ## Choose the matching release | Installation | Authenticated package | | - | - | | Native bundle | [Native bundle release](https://github.com/safeney/Tavchain/releases/tag/native-bundle-771002-1), with `BUNDLE-RELEASE.json`, its detached signature and `VERIFY.md`. Client `1.8.1-tavchain.eval1-native1`, runtime libraries and network files are included. | | Prebuilt Docker image | [Docker guide](https://docs.tavchain.safeney.com/tavchain/operate/node-docker.md), with an exact image digest in the registry Compose file. Client `1.8.1-tavchain.eval1` and network defaults are included. | | Earlier manual Linux client | [Earlier installation](https://docs.tavchain.safeney.com/tavchain/operate/run-full-node.md), using the binary and network manifests separately. This is also the client used by the existing systemd guide. | The earlier client archive contains historical network files. Its manual installation replaces them with the authenticated 771002 files before initializing a fresh node. Do not replace genesis or configuration in an existing home as an upgrade shortcut. Download base: `https://testnet.tavchain.safeney.com/downloads/tavchain-network-771002-1`. The package contains `genesis.json`, `config.toml`, `app.toml`, `peers.txt`, `network.json`, `README.md`, `VERIFY.md`, `SHA256SUMS` and `tavchain-network-771002-1.tar.gz`. Its signed manifest is `NETWORK-RELEASE.json` with detached `NETWORK-RELEASE.json.sig`. Use the trusted fingerprint `SHA256:rZRDFiztp0bd51gCAI/qKBGxkOKl9Fv52UWdbUpUQRM`, principal `safeney-tavchain-releases` and namespace `tavchain-release-v1`. Signed release metadata records the package at preparation time. Check the [network reference](https://docs.tavchain.safeney.com/tavchain/network.md) and current RPC for live network identity. Checksums alone do not establish publisher identity. A checksum or signature does not prove that a network is public or that synchronization succeeded. The node executable and application/dependency source archives remain at the [existing client release](https://testnet.tavchain.safeney.com/downloads/tavchain-node-1.8.1-tavchain.eval1/RELEASE.json). Dependencies retain their existing licenses and notices. The newer [native release](https://docs.tavchain.safeney.com/tavchain/operate/node-native.md) provides tested Linux x86-64, Linux ARM64 and Windows x86-64 full-node binaries with a separate signed manifest. Its exact source and packaging changes are provided alongside the binaries. Browse the [Tavchain node source and public network files](https://github.com/safeney/Tavchain). For installation and reproducible builds, continue to use the authenticated release archives and their exact build instructions. ## Docker package For a new Linux x86-64 node, follow [Run a node with Docker](https://docs.tavchain.safeney.com/tavchain/operate/node-docker.md). Its [public image](https://github.com/safeney/Tavchain/pkgs/container/tavchain-fullnode) includes the current network files; the [registry Compose file](https://github.com/safeney/Tavchain/blob/main/operators/docker/compose.registry.yaml) pins its exact digest. The [signed Docker archive](https://github.com/safeney/Tavchain/releases/tag/docker-771002-1) remains the local-build alternative. Verify `DOCKER-RELEASE.json` and its detached signature before extracting the archive and following its README. The original download base remains `https://testnet.tavchain.safeney.com/downloads/tavchain-docker-771002-1`. Both Docker routes map host RPC to `127.0.0.1` and publish no P2P host port. Their client is Linux amd64 only. The image digest identifies image bytes; it is separate from the archive's existing detached signature. Native binary compatibility is documented separately. ## Public peers ```text theme={null} 63c3e0f56b33ce0b45ebb03806dab3002691a187@77.42.64.182:28656 2b5612173d3d593a6cb210d436d7817ab9cb44b7@77.42.64.182:28756 b38fde60012b3fd37da07bdd82dce91428d50e73@77.42.64.182:28856 ``` These three endpoints share a hosting failure domain. They are persistent peers, not three independent operators or a separate seed service. The observer profile disables PEX and allows duplicate peer IPs. ## Local full-node listeners | Port | Purpose | Exposure | | - | - | - | | 29656 | CometBFT P2P | Loopback, with outbound peer connections | | 29657 | Native RPC | Loopback | | 29645 | EVM HTTP RPC | Loopback | | 29646 | EVM WebSocket | Local listener only | REST, gRPC, gRPC-web, metrics and unsafe RPC remain disabled. This observer follows history from genesis and retains it. It is not a validator configuration. See [Node service](https://docs.tavchain.safeney.com/tavchain/operate/node-service.md), [Monitor a node](https://docs.tavchain.safeney.com/tavchain/operate/monitoring.md) and [Security](https://docs.tavchain.safeney.com/tavchain/learn/security.md). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.