Current Count: {count}
{error}
} {!wallet ? ( ) : (Wallet: {wallet}
Option 1: {votes.option1} votes
Option 2: {votes.option2} votes
{!hasVoted ? (You have already voted!
)}Chain name: KiteAI Testnet
Default RPC URL - https://rpc-testnet.gokite.ai/
Chain ID: 2368
Token: KITE
Block Explorer URL - https://testnet.kitescan.ai/
| | $KITE testnet tokens | Get from[ Faucet](https://faucet.gokite.ai) (Testnet Ozone). | | Ash Wallet URL | [https://wallet.ash.center/?network=kite](https://wallet.ash.center/?network=kite) | #### Create a Multisig 1. Connect wallet → Create new Smart Account. 2. Owners: paste each signer’s Kite address (hardware wallets recommended). 3. Threshold: Kite Foundation = 3 of 5; small team = 2 of 3. 4. Review gas (≈ 0.11 $KITE). 5. Deploy – transaction mined on Kite AI L1 in \~1 s. #### Import an Existing Safe / Ash Click “Add existing” → supply multisig address → Ash auto-detects Kite AI contracts; owners need no redeploy. #### Day-to-Day Ops | Task | Flow | | ------------------- | -------------------------------------------------------------------------------- | | Propose token spend | New Tx → Send funds → choose ERC-20 → input amount & recipient → Post. | | Approve | Each owner sees pending tx → Sign → gasless off-chain signature stored. | | Execute | When signatures ≥ threshold, any owner pays gas (can reimburse later). | | Batch agent payouts | New Tx → Contract interaction → select BatchTransfer module → CSV of recipients. | | Upgrade protocol | Use Module → TimelockGuard: delay = 48 h, gives DAO time to veto. | #### Security Best-Practices 1. Hardware keys for all signers. 2. Signer Rotation Playbook – store off-chain; test quarterly. 3. Alert Webhooks → route Ash event logs to Slack/Prometheus. 4. 2-Layer Governance – combine on-chain timelock with off-chain Snapshot vote for non-emergency upgrades. #### Troubleshooting | Symptom | Likely Cause | Fix | | -------------------------------- | ----------------------- | --------------------------------------------- | | Tx stuck in “Awaiting Execution” | Not enough signatures | Ping owners; check threshold. | | “Network not supported” popup | MetaMask on wrong chain | Switch to Kite AI RPC. | | Gas estimate fails | Node lag / mempool full | Retry | | UI missing dApps | Apps list cached | Hard-refresh or Clear dApp cache in settings. | #### Resources * Kite Documentation * Ash Wallet –[ https://wallet.ash.center/?network=kite](https://wallet.ash.center/?network=kite) * Discord – discord.gg/gokiteai * Contracts –[ ](https://github.com/ash-avax/ash-kite)[https://github.com/safe-global/safe-smart-account/tree/v1.3.0](https://github.com/safe-global/safe-smart-account/tree/v1.3.0) (GPLv3) * SDK – https://github.com/safe-global/safe-core-sdk #### Audit information * [https://github.com/safe-global/safe-smart-account/blob/v1.3.0-libs.0/docs/audit_1_3_0.md](https://github.com/safe-global/safe-smart-account/blob/v1.3.0-libs.0/docs/audit_1_3_0.md) --- # Kite Node URL: https://docs.gokite.ai/kite-chain/7-kite-node This page contains documentation and operational guidance for running and managing nodes on the Kite mainnet. Kite nodes form the backbone of the network. They power consensus, secure transactions, propagate state, and ensure reliable execution for agents, users, and applications built on Kite Chain. --- ## Overview The Kite Node documentation is structured to support both **understanding the network** and **operating production-grade infrastructure**. It is organized into two main sections: 1. [**Mainnet Network Information**](/kite-chain/7-kite-node/mainnet-network-information) 2. [**Mainnet Node Operations**](/kite-chain/7-kite-node/mainnet-node-operations) --- ## What’s Covered ### Mainnet Network Information This section explains how the Kite mainnet works at a protocol and infrastructure level. Topics include: - Network architecture and core components - Validator, full node, and RPC node roles - Chain parameters (block time, gas, limits) - Security details Use this section to understand the system before deploying or integrating nodes. --- ### Mainnet Node Operations This section focuses on hands-on operational guidance for running Kite nodes in production. Topics include: - Hardware and system requirements - Node installation and setup - Configuration and environment tuning - Running and managing node processes - Monitoring, logging, and alerting - Maintenance, upgrades, and recovery Designed for DevOps, SREs, and infrastructure providers. --- ## Who This Is For This documentation is intended for: - Validators participating in Kite network - Infrastructure providers offering RPC or indexing services - DevOps and SRE teams running blockchain infrastructure - Advanced builders requiring protocol-level understanding --- ## Security Good practices Running a node involves private keys, network exposure, and operational risk. Always: - Secure keys and credentials - Restrict network access - Monitor uptime and performance - Apply upgrades carefully and deliberately --- ## Support & Updates - Monitor governance channels for protocol updates - Track documentation changes for operational guidance - Coordinate upgrades during announced network windows --- --- # Mainnet Network Information URL: https://docs.gokite.ai/kite-chain/7-kite-node/mainnet-network-information This page provides the essential network details required to connect to and interact with the **Kite Mainnet**. Use this information when configuring wallets, RPC providers, node clients, or infrastructure services. ## Chain Information | Parameter | Value | |----------------|------------------| | **Chain Name** | KiteAI Mainnet | | **Chain ID** | 2366 | | **Token Symbol** | KITE | ## RPC Endpoints Kite Mainnet provides multiple geographically distributed RPC endpoints for reliability and low latency. It is recommended to configure **multiple RPCs** for redundancy in production environments. ### HTTPS RPCs - Global - [https://rpc.gokite.ai/](https://rpc.gokite.ai/) - Virginia - [https://rpc-virginia.gokite.ai](https://rpc-virginia.gokite.ai) - Tokyo - [https://rpc-tokyo.gokite.ai](https://rpc-tokyo.gokite.ai) - Ireland - [https://rpc-ireland.gokite.ai](https://rpc-ireland.gokite.ai) ### WebSocket (WSS) RPCs - Global - [wss://rpc.gokite.ai/ws](wss://rpc.gokite.ai/ws) - Virginia - [wss://rpc-virginia.gokite.ai/ws](wss://rpc-virginia.gokite.ai/ws) - Tokyo - [wss://rpc-tokyo.gokite.ai/ws](wss://rpc-tokyo.gokite.ai/ws) - Ireland - [wss://rpc-ireland.gokite.ai/ws](wss://rpc-ireland.gokite.ai/ws) WebSocket endpoints are recommended for: - Real-time event subscriptions - Block and transaction streaming - Indexers and agent-based applications ## Block Explorer Use the Kite block explorer to inspect transactions, blocks, contracts, and addresses: - **Explorer:** [https://kitescan.ai/](https://kitescan.ai/) ## Usage Notes - Always use **HTTPS RPCs** for standard JSON-RPC calls - Use **WSS RPCs** for subscriptions and real-time workloads - For production systems, configure **RPC failover** across regions - Monitor governance and upgrade announcements for endpoint changes ## Next Steps - Proceed to **Mainnet Node Operations** to run your own node - Configure wallets and tooling using the Chain ID and RPCs above - Review security best practices before deploying production infrastructure --- # Mainnet Node Operations URL: https://docs.gokite.ai/kite-chain/7-kite-node/mainnet-node-operations This page describes how to set up, configure, deploy, and operate a Kite mainnet node. ## System Requirements ### Minimum Hardware Specifications - **CPU:** 8 AWS vCPU or equivalent - **RAM:** 16GB - **Storage:** 1TB SSD ## Network Requirements Open inbound ports: - **TCP/9650:** HTTP API - **TCP/9651:** P2P Staking ## Prepare Node Config You need to prepare the node config content for `AVAGO_CHAIN_CONFIG_CONTENT` env var. Content must be base64 encoded. The node config options can be found in **C-Chain Configs**. The node config structure is as below, the root key is KiteAI mainnet's blockchain ID, `Config` key is the base64 encoded chain config, `Upgrade` key is the base64 encoded upgrade config. ```json { "3USaEfTcoUhHxpKXvpAG916UKCUEyjrtkg2hBArBG3JyDP7my": { "Config": "