# 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](https://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.

<figure><img src="/files/BkyKrbAFc1wAkvzYXR7t" alt=""><figcaption><p>Chain Parameters</p></figcaption></figure>

### 💰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.

<mark style="color:red;">**Important:**</mark>

* <mark style="color:red;">You may add</mark> <mark style="color:red;"></mark><mark style="color:red;">**as many addresses as needed**</mark> <mark style="color:red;"></mark><mark style="color:red;">to distribute the total token supply.</mark>
* <mark style="color:red;">Make sure the total allocated tokens across all addresses</mark> <mark style="color:red;"></mark><mark style="color:red;">**do not exceed the total supply.**</mark>

{% hint style="success" %}
Refer this [Tokenomics link](https://build.avax.network/docs/avalanche-l1s/evm-configuration/tokenomics) to know more about it.
{% endhint %}

<figure><img src="/files/vOdQKDVfwYLk3vSucpyV" alt=""><figcaption><p>Tokenomics</p></figcaption></figure>

### ⚙️Permissions

* **Validator Set**\
  Provide the **POA Owner Address** responsible for controlling the validator set of the blockchain.
* [**Native Minter AllowList**](https://build.avax.network/docs/virtual-machines/default-precompiles/nativeminter)\
  The Native Minter hook enables minting of native tokens on the chain.
* [**Contract Deployer AllowList**](https://build.avax.network/docs/virtual-machines/default-precompiles/deployerallowlist)\
  The Deployer AllowList hook manages permissions for deploying smart contracts.
* [**Transaction AllowList**](https://build.avax.network/docs/avalanche-l1s/evm-configuration/permissions#transaction-allowlist)\
  The Transaction AllowList hook governs which transactions are permitted on the network.
* [**Fee Manager**](https://build.avax.network/docs/virtual-machines/default-precompiles/feemanager)\
  The Fee Manager hook handles chain fee configurations and adjustments.
* [**Reward Manager**](https://build.avax.network/docs/virtual-machines/default-precompiles/rewardmanager)\
  The Reward Manager hook controls settings related to reward distribution.

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

{% hint style="success" %}
Refer this [Permissions link](https://build.avax.network/docs/avalanche-l1s/evm-configuration/permissions) to know more about it.
{% endhint %}

<figure><img src="/files/ho24WQvitzjz41V8SE7O" alt=""><figcaption><p>Permissions</p></figcaption></figure>

* [**Warp Precompile**](https://build.avax.network/docs/avalanche-l1s/evm-configuration/warpmessenger)

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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cogitus.io/getting-started/launching-an-l1-devnet-testnet/network-setup-and-configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.