æternity Documentation Hub
AeternityGitHub
  • æternity Hub
  • Welcome to æternity documentation
  • Getting Started
    • What is æternity?
    • How to Use Aeternity
  • æternity core concepts
    • Introduction
    • æternity Protocol
      • æternity Coin
      • Fast Æternity Transaction Engine (FATE VM)
      • æternity Nodes
        • Node architecture
        • Node types
        • Node Roles
      • Transactions
        • Types of transactions
        • Transaction Lifecycle
        • Transaction Fees
        • Meta-transactions and Generalized Accounts
        • State Channel Transactions
      • Networks
      • Consensus Mechanisms
        • Next Generation Nakamoto Consensus (Bitcoin-NG)
        • Cuckoo Cycle Proof of Work
        • Hyperchains and Delegated Proof of Stake
        • Governance and Weighted Coin Voting
      • State Channels
      • Oracles
      • Aeternity Naming System (AENS)
    • Hyperchains
      • Hyperchains Whitepaper
    • Aeternity Governance
    • Aeternity Foundation
  • aeternity user tools and services
    • Introduction
    • Run an æternity node
    • Hyperchains web app
    • Hyperchains Bridge app
    • Mine aeternity coin
    • Superhero DEX
    • Superhero Wallet
    • ærc Bridge
    • Make an NFT
    • aepps: decentralized applications on æternity
    • æScan: æternity blockchain explorer
  • æternity Developer tools
    • Quick Start Guide
      • Development Environment Setup
      • Essential Tools Overview
      • Æternity Stack
      • First Steps in Development
    • Protocol
      • Core Protocol Components
        • æternity Consensus Protocol
        • Generalized Accounts
        • Smart Contracts
          • FATE VM
          • Smart contract languages
            • æternity Sophia Language
              • In-Depth Overview
              • Sophia Compiler
              • Sophia Visual Studio
              • Sophia http
              • æREPL
            • Solidity
          • Contract Transactions
        • State Channels
        • Oracles
      • Network Layer
        • Nodes
        • Sync
        • Gossip
        • Stratum
      • Utility Features
        • æternity Naming System (AENS)
        • Seralization Formats
    • æternity Sophia Language
      • In-Depth Overview
      • Sophia Compiler
      • Sophia Visual Studio
      • Sophia http
      • æREPL
    • Development Infrastructure
      • CLIs
      • SDKs and APIs
        • Javascript/Typescript SDK
        • Java SDK
        • Outdated SDKs
        • Node API reference
      • Middleware
      • Testing and Deployment
        • æproject
        • Testnets and Faucet
    • Token Standards
    • Aepps: Building apps on Aeternity
      • Boiler Plates
        • Angular Boiler Plate
        • React JS BoilerPlate
        • Vue BoilerPlate
    • Data and analytics
      • æScan
    • ÆRC Bridge
  • Hyperchains
    • Hyperchains Development Guide
    • Hyperchains Bridge
Powered by GitBook
On this page
  • æternity Networks
  • Overview
  • Mainnet
  • Development Networks
  • Testnet
  • Network Differences
  • Cross-Network Considerations
  • Future Network Evolution

Was this helpful?

Export as PDF
  1. æternity core concepts
  2. æternity Protocol

Networks

PreviousState Channel TransactionsNextConsensus Mechanisms

Last updated 17 days ago

Was this helpful?

æternity Networks

Overview

The æternity blockchain ecosystem consists of different networks that serve various purposes, from main network operations to development and testing. Each network type maintains the core features of æternity, including Bitcoin-NG consensus, state channels, oracles, and the FATE virtual machine, while serving specific needs within the ecosystem.

Mainnet

The æternity mainnet is the primary production network where real AE tokens hold economic value. Launched in November 2018, the mainnet implements all protocol features with full security measures in place. This network processes actual transactions, executes smart contracts, and maintains the authoritative state of the blockchain. The mainnet uses Cuckoo Cycle proof-of-work for consensus, with carefully calibrated difficulty adjustments to maintain consistent block times.

Development Networks

For developers building on æternity, several development network options exist. The most commonly used is the local development network, which developers can run on their own machines. These networks allow developers to test applications, smart contracts, and protocol features without spending real tokens or waiting for network confirmations.

Development networks can be configured with different parameters than the mainnet, such as faster block times or lower mining difficulty, to facilitate rapid development and testing. They support all mainnet features, including state channels and oracles, making them ideal for application development and testing.

Testnet

The æternity testnet serves as a staging environment for testing applications and protocol updates before mainnet deployment. This network mirrors the mainnet's functionality but uses test tokens without real economic value. Developers and users can experiment with new features, test applications, and validate protocol upgrades on the testnet without risk.

The testnet maintains the same core architecture as the mainnet, including the Bitcoin-NG consensus mechanism and all protocol features. This ensures that testing conditions closely match production environments while providing a safe space for experimentation.

Network Differences

While all æternity networks implement the same basic protocol, they can differ in several aspects:

Genesis configuration determines the initial state of each network, including token distribution and protocol parameters. Mining difficulty varies between networks, with development networks typically using lower difficulties to facilitate faster block creation. Network parameters such as minimum fees, name registration costs, and oracle query fees may be adjusted for different network purposes.

Cross-Network Considerations

When developing on æternity, it's important to consider the differences between networks. Code that works on a development network should be thoroughly tested on the testnet before mainnet deployment. State channel applications, in particular, should be tested across networks to ensure proper behavior under different network conditions.

Future Network Evolution

The æternity protocol continues to evolve, with new features and improvements being developed. These changes typically follow a path from development networks through testnet validation before reaching mainnet deployment. This progression ensures that protocol updates are thoroughly tested and validated before affecting the main network.

Through this network structure, æternity provides a complete environment for both development and production use, enabling secure and efficient blockchain operations while supporting continued innovation and development.

For more information on how to set up a local development network or run the testnet, please refer to the section of our developer Tools section.

Development Infrastructure
Cover

Network Layer Documentation