XION
DiscordGithub
  • Welcome to XION
  • XION'S Core
    • Concepts
      • Generalized Chain Abstraction
      • Intro to Account Abstraction
      • XION's Meta Accounts
      • Meta Accounts Design
      • Architecture & Tech Glossary
      • Use Cases
  • developers
    • XION Quick Start
      • Zero to App in 5 Minutes
        • Launch a User Map App on XION in 5 Minutes
        • React Native Mobile App on XION in 5 Minutes
        • Todo App
          • Build a TODO App using the Collection-Document Storage Smart Contract
          • Build a TODO Mobile App using the DocuStore Contract
    • Mobile App Development
      • Set up your XION Mobile Development Environment
      • Build a TODO Mobile App using the DocuStore Contract
      • Create Mobile App and Integrate Meta Account Authentication
      • Building a React Native Mobile App with Abstraxion (Xion.js)
    • Getting Started (Advanced)
      • Set Up Local Environment
        • Setting up your Local Smart Contract Development Environment for XION
          • Setting up your XION Smart Contract Development Environment on Windows (WSL2 + Ubuntu)
        • Set Up an Integrated Development Environment (IDE)
        • Interacting with Xion Chain using Xion Daemon
      • Your First Contract
        • Deploying Your First Smart Contract on XION
      • Gasless UX & Permission Grants
        • Enabling Gasless Transactions with Treasury Contracts
      • App Development
        • Account Abstraction with Gasless Transactions
        • Interact with XION via your Backend Service
    • Re-using Existing Contracts
      • Deployed Contracts on XION
      • Non-Fungible Tokens (NFTs)
      • Fungible Tokens
      • Marketplace
      • Multisig
      • Proxy Contracts
      • Membership Management
      • Governance
      • Valuts
      • SCV Audited Contracts
    • Web3 for Web2 Developers
      • Web2 vs Web3 App Architecture: A Comparison
      • Misconceptions and Misapplied Web2 Patterns
      • Recommended Architecture for Apps on XION
    • Building for Mainnet
      • Xion Testnet: Your Development Playground
      • Building with Audited & Battle-Tested Contracts
      • Community Engagement: Building Support for Your app
      • Deploying to Xion Mainnet
        • Smart Contract Audits: Process, Costs & Support
        • Governance Process to Deploying Smart Contracts to Mainnet
    • Learn & Build
      • Token Factory
        • Creating, Minting, and Interacting with a Token Factory Token
        • Building a React dApp to Interact with Token Factory Tokens
        • Integrating a Token Factory Token in a Smart Contract
      • Websockets
        • WebSockets with Xion: Real-Time Communication
      • Oracles
        • Creating a Smart Contract with Pyth Oracle Integration
      • Indexers: Optimized Data Retrieval
        • SubQuery
      • Use Cases
        • Building a Per-User Data Storage App
        • Build a TODO App using the Collection-Document Storage Smart Contract
      • Crossmint Integration
        • Crossmint Digital Collectibles Checkout via Credit Card
    • Reference and Resources
      • Requesting XION Testnet Tokens
      • Public Endpoints & Resources
      • Block Explorers
      • Governance
        • Deploying Smart Contracts to Mainnet
      • Developer Tools: Abstract
      • IBC Denoms on XION Networks
      • Frequently Asked Questions
      • XION Token Contract Addresses on EVM Chains
  • Nodes & Validators
    • Run a Node
      • System Specifications
      • Build the Xion Daemon
      • Download the Xion Daemon
      • Configure the Xion Daemon
        • app.toml
        • client.toml
        • config.toml
      • Join the XION Network
        • xion-testnet-1
      • Confirm node is running
    • Become a Validator
      • Initial Setup
      • Obtain a XION Wallet Address
      • Obtain Funds
        • Testnet
      • Create Validator
    • IBC Relayers and Tokens
  • Others
    • Resources
Powered by GitBook
On this page
  • Hardware Requirements
  • Commonly used ports

Was this helpful?

Edit on GitHub
  1. Nodes & Validators
  2. Run a Node

System Specifications

Recommended system specs

PreviousRun a NodeNextBuild the Xion Daemon

Last updated 2 months ago

Was this helpful?

🐧 Recommended operating systems

We've tested our technology on several Linux distributions.

If you're considering running another OS, your mileage may vary, and we'll be unable to assist you to get up and running.

Hardware Requirements

The minimum recommended specs for running an instance of xiond on the Burnt Networks are:

Network
CPU cores
RAM
Disk (SSD)
Bandwidth

xion-testnet-2

8 (gen-purpose)

32 GB

128 GB

~120 Mbps

xion-mainnet-1

8 (compute-optim)

32 GB

256 GB

~120 Mbps

Monitor your system

As the network grows, the minimum hardware requirements will also grow.

It is recommended that you monitor your system so you can prevent it from running out of resources.

Commonly used ports

The Xion daemon uses the following TCP ports. Please adapt their settings to match your needs.

In most cases, node operators only need to open the following port:

  • 26656: The default port for the P2P protocol.

    • This port is used to communicate with other nodes and must be open to join a network. However, it does not have to be open to the public. For validator nodes, configuring persistent_peers and closing this port to the public are recommended.

Additional ports:

  • 1317: The default port for the Lite Client Daemon (LCD).

    • The LCD provides a RESTful API to allow applications and services to interact with your instance. In the default configuration, it is disabled.

  • 26657: The default port for the Tendermint RPC protocol.

    • Because this port is used for querying and sending transactions, it must be open for serving queries. In the default configuration it is listening on 127.0.0.1.

  • 26660: The default port for interacting with the Prometheus database

    • This port can be used to monitor the node itself, and gather information about the network. In the default configuration, it is disabled.

Do not open ports 1317 and / or 26657 to the public unless you explicitly plan to run a publicly-accessible node.

Caution

⚠️
⚠️