🚀Network Setup & Configuration

Once your Devnet subscription is successfully activated, you can begin configuring your network settings through the Cogitus Dashboard or directly click on Configure Your Devnet.

🔗Chain Parameters

• L1 Name

  • Choose a name for your Layer 1 network.

  • ⚠️ Note: Do not include spaces.

  • ✅ Example: MyAvalancheL1

• Chain ID

  • Enter a unique Chain ID (numeric).

  • 🔍 Please verify its uniqueness using chainlist.org to ensure it is not already in use by another public network.

• Network

  • Pre-filled: Fuji Testnet

  • This indicates that the network will initially be deployed on Fuji (Avalanche's testnet).

• Validator Management

  • Pre-filled: POA (Controlled Validator Expansion)

  • Validators will be managed under a Proof of Authority model, allowing only selected entities to participate.

• Set Fees Configuration

  • Please select a fee and resource configuration that matches your expected workload:

    • 🟢 Low Disk Use / Low Throughput – Ideal for minimal load or test scenarios.

    • 🟡 Medium Disk Use / Medium Throughput – Balanced setup for general-purpose usage.

    • 🔴 High Disk Use / High Throughput – Optimized for heavy traffic and larger-scale deployments.

💰Tokenomics

• Provide Token Symbol

  • Enter the symbol for your native token (e.g., DCM, AVAX, MYTKN).

  • Keep it short (3–5 characters) and unique to your network.

• Initial Token Allocation Define the initial distribution of your native tokens by specifying wallet addresses and their corresponding token amounts.

  • POA Address (Pre-filled & Non-Editable): When you enter the POA (Proof of Authority) address under Permissions, this same address will appear here automatically and will not be editable. This ensures the POA address is always part of the token allocation.

Important:

• You may add as many addresses as needed to distribute the total token supply.

• Make sure the total allocated tokens across all addresses do not exceed the total supply.

⚙️Permissions

• Validator Set Provide the POA Owner Address responsible for controlling the validator set of the blockchain.

• Native Minter AllowList The Native Minter hook enables minting of native tokens on the chain.

• Contract Deployer AllowList The Deployer AllowList hook manages permissions for deploying smart contracts.

• Transaction AllowList The Transaction AllowList hook governs which transactions are permitted on the network.

• Fee Manager The Fee Manager hook handles chain fee configurations and adjustments.

• Reward Manager The Reward Manager hook controls settings related to reward distribution.

Important: The AllowList hooks provide functions to manage access control lists for various roles such as Admin, Manager, and Enabler. For any enabled precompile, you need to specify addresses for Admin, Manager, and/or Enabler roles. However, providing all three addresses is not mandatory — only specify the roles relevant to your configuration.

• Warp Precompile

The Warp Messenger Precompile is used to perform cross chain operations among Avalanche L1s.

Warp Precompile enables cross-blockchain communication between other Layer 1s and primary-network (C-Chain) by leveraging the Avalanche P-Chain. In order to use Warp messaging, Subnet-EVM chains must activate their Warp precompiles.

Now click on Deploy button, provisioning of the network initiated.