StateMesh Documentation

website·Indexed 32 days ago

https://docs.statemesh.net

A decentralized cloud infrastructure replacing traditional data centers with a global network of compute and storage nodes. StateMesh features an L1 EVM-compatible blockchain based on Fantom's Lachesis DAG, providing tools for deploying containers, virtual machines, and databases via the StateMesh Console or CLI.

Tokens
14.8K
Snippets
28
Records
131
Agent score
49%

What's inside StateMesh

  1. Overview of StateMesh Virtual Machines

    Virtual Machines (VMs) in StateMesh are the lowest-level unit of deployment, allowing users to run their own 64-bit operating systems on the StateMesh network.

    Supported Operating Systems:

    • Ubuntu 20.04, 22.04, 24.02
    • Fedora 40, 41
    • CentOS 9

    Key Architectural Constraints:

    • Node Requirements: VMs only run on Bare-metal nodes and Datacenter nodes because they require hardware virtualization support.
    • Root Disk Persistence: The root disk is bound to the lifecycle of the node. If a node is decommissioned, data on the root disk is lost. Use additional Volumes for persistent data.
    • Migration: Live migration is not supported. If a node is decommissioned, the VM is terminated and restarted on a different node.
    • Networking: VMs do not have public routable IP addresses; however, users can publish ports to the public network.
  2. Overview of StateMesh Managed Databases

    StateMesh provides managed PostgreSQL databases deployed via a Kubernetes operator. Key features include fast deployment, support for multiple replicas, logical backups, and configurable resource requirements. By default, databases are accessible only from within the cluster, though they can be exposed via public ingress.
  3. Overview of StateMesh decentralized cloud infrastructure

    StateMesh is a decentralized cloud infrastructure that replaces traditional data centers with a global network of crowd-sourced node operators, serving as a decentralized alternative to providers like AWS, GCP, and Azure. Key features include:

    • Censorship Resistance: No central authority controls the network, making it difficult for single entities to shut down applications.
    • Privacy and Anonymous Workloads: Supports payment via stablecoins (USDC, USDT, etc.) to allow running workloads without revealing the payer's identity.
    • Native Decentralization: Applications are inherently more secure and resilient, making the platform suitable for dApps and validator nodes.
  4. Overview of StateMesh Time Towers

    Time Towers are a mechanism used by StateMesh to ensure persistent, secure identities and verifiable metrics for node operators. They function as 'puzzle towers' that act as a proof of elapsed time using Verifiable Delay Functions (VDF). Unlike Proof of Stake (PoS), Time Towers do not rely on financial assets, allowing anyone to become a node operator without token sales or airdrops.

    Time Towers are stored on the StateMesh blockchain, and each operator is limited to one tower. They are used to:

    • Identify and authenticate node operators.
    • Maintain identity across reboots and network failures.
    • Provide a tamper-evident record of activity.
    • Record node metrics and reward contributions.
    • Punish malicious behavior.

    Nodes that actively generate Time Tower proofs are given higher preference for executing Agent tasks.

  5. Overview of StateMesh decentralized cloud infrastructure

    StateMesh is a decentralized cloud infrastructure that replaces traditional data centers with a global network of crowd-sourced node operators. It provides a permissionless environment for running workloads with a focus on censorship resistance, privacy (via stablecoin payments in USDT/USDC), and high availability. It is designed to be a decentralized alternative to public clouds like AWS, GCP, and Azure, specifically catering to Web3 builders and those requiring anonymous or resilient workloads.
  6. Overview of planned Storage node types

    Storage nodes (currently planned) will provide storage resources to the network based on the drive type:

    • SSD nodes: Provide SSD storage.
    • HDD nodes: Provide HDD storage.
    • NVMe nodes: Provide NVMe storage.
  7. Manage assets and bridge funds with StateMesh Wallet

    The StateMesh Wallet provides the following core functionalities for interacting with the blockchain network:

    • Account Management: View account balances, transaction history, and manage multiple accounts.
    • Asset Transfers: Send and receive funds, ERC-20 tokens, and other assets.
    • Cross-chain Bridging: Bridge MESH and stablecoins to and from other blockchains.
  8. Unsupported StateMesh JSON-RPC Features

    The following features and namespaces are not supported in StateMesh's JSON-RPC API:

    • Pending block retrieval (the concept of pending blocks does not exist in the Lachesis consensus model).
    • shh namespace
    • db namespace
    • bzz namespace
  9. StateMesh Blockchain Core Features Overview

    StateMesh is built on a modified go-ethereum (geth) architecture. It maintains full EVM compatibility, allowing developers to deploy Ethereum-compatible smart contracts using Solidity and standard developer tools. Key performance improvements include transaction finality in approximately 1 second and immediate confirmation without the need for multiple block confirmations.
  10. StateMesh Network Regional Architecture

    StateMesh organizes its global network into Regions and Availability Zones. A Region is a geographical area containing one or more Availability Zones. Each region operates a private mesh network (VPN-like) for inter-zone communication, utilizing ChaCha20 encryption with Poly1305 authentication. This mesh network runs in kernel space to optimize performance, typically adding ~0.1ms of latency and providing throughput of approximately 50% of the public network bandwidth (e.g., 5Gbps on a 10Gbps public link).
  11. Understand StateMesh Application architecture

    Applications in StateMesh are the highest-level unit of deployment, functioning as a combination of Kubernetes Deployment, Service, and Ingress. An application bundles together a collection of containers (the workload), storage resources, a load-balancing mechanism for network traffic, and Entrypoints for internet exposure.
  12. Understand the benefits of Proof of Time (PoT) mining

    Proof of Time (PoT) mining for Time Towers is designed for accessibility and sustainability. Key characteristics include:

    • Low Barrier to Entry: Requires only a CPU, minimizing capital requirements.
    • Environmental Sustainability: Uses minimal computational resources because the process is sequential, meaning parallelization provides no advantage.
    • Long-term Equity: Because time towers grow linearly, the initial advantage held by genesis peers diminishes over time, allowing new participants to compete fairly.