> For the complete documentation index, see [llms.txt](https://docs.cogitus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cogitus.io/getting-started/managing-l1-devnet-testnet/dashboard.md).

# Dashboard

Any Avalanche L1 network is an EVM-based Layer 1 blockchain deployed on either the **Fuji Testnet** or **Avalanche Mainnet**. Below are the key technical and configuration details associated with the network with the **Deployment Status:** ✅ Deployed.

### ℹ️L1 Details

* **L1 Name:** Custom name provided by the user
* **L1 ID:** *Auto-generated upon network creation*
* **Blockchain ID:** *Auto-generated unique identifier for the blockchain*
* **VM ID:** *Auto-generated identifier for the deployed Virtual Machine*
* **Network:** Fuji Testnet / Avalanche Mainnet *(select based on deployment)*
* **EVM Chain ID:** Custom value provided by the user

  > 🔍 *<mark style="color:red;">Note: Please verify the EVM Chain ID on</mark>* [*<mark style="color:blue;">chainlist.org</mark>*](https://chainlist.org) *<mark style="color:red;">to avoid conflicts with existing public networks.</mark>*
* **Token Symbol:** User-defined native token symbol (e.g., ABC, TKN)

### ℹ️L1 Configurations

* **Chain Type:** EVM
* **Precompiles Enabled:** List of precompiles selected during deployment

  > 🛠 *<mark style="color:red;">Note: Warp Messenger is enabled by default.</mark>*
* **Initial Token Allocation:**\
  View the complete list of preminted tokens (denominated in AVAX units).

### ℹ️L1 Services

* **Avalanche Subnet Explorer:**\
  Public explorer provided by Avalanche that displays real-time on-chain activity for your subnet, including block production, transactions, validator status, and network health.\
  \&#xNAN;*<mark style="color:red;">Example:</mark>* `https://subnets.avax.network/subnets/<YourSubnetID>`
* **TraceHawk Explorer:**\
  A dedicated, customizable block explorer hosted by Zeeve for your network. It offers an intuitive UI to track transactions, blocks, token balances, contract verification, and more in a user-friendly format.\
  \&#xNAN;*<mark style="color:red;">Example:</mark>* `https://explorer-<networkname>.zeeve.net`
* **RPC Endpoint:**\
  The Remote Procedure Call (RPC) URL that developers and dApps use to connect to your Avalanche L1 network for querying blockchain data or submitting transactions.\
  \&#xNAN;*<mark style="color:red;">Example:</mark>* `https://rpc-<networkname>.zeeve.net/ext/bc/<blockchainID>/rpc`
* **Faucet (if available):**\
  A test token distribution service, allowing users to request native tokens for testing purposes on testnet.\
  \&#xNAN;*<mark style="color:red;">Example:</mark>* `https://faucet.<networkname>.zeeve.net` *(optional and usually for testnet only)*

### &#x20;🔐Precompile Management Keys

For each precompile enabled during deployment, specific management roles are assigned to control and configure their functionality within the Avalanche L1 network. These roles include:

* **Admin Addresses:**
  * Full control over the allowlist system
  * Can add/remove Manager keys
* **Enabler Addresses:**
  * Can interact with precompiled contracts for:
    * Deploying contracts
    * Managing chain params (if permitted)
    * Triggering key functions (e.g. mint, pause)
  * Cannot manage the allowlist
* **Manager Addresses:**
  * Can add/remove Enabler keys
  * Cannot manage Admins or other Managers

> 🛠 *<mark style="color:red;">Note: These addresses are provided by the user during network setup and vary based on the selected precompiles.</mark>*