Create Genesis
Create and customize the genesis.json file for an EVM Avalanche L1.
The genesis file of your blockchain contains critical configurations determines how your blockchain will operate and sets various parameters that will govern its behavior. These configurations include:
- Chain ID: A unique identifier for your blockchain
- Native Token Allocation: How many tokens are allocated to each address at genesis
- Fee Configuration: Parameters that govern transaction fees and block production
- Precompiles: Which precompiled contracts are enabled and their configurations
- Network Upgrades: Activation times for new features and changes
With this tool below you can create a simple genesis file for your EVM blockchain. We use many default values for configurations not relevant for this course. Native tokens are allocated to your currently connected wallet. You can customize the genesis file further by editing the JSON directly.
Chain Parameters
Enter the basic parameters of your L1, such as the EVM chain ID.
Unique identifier for your blockchain. Check chainlist.org to avoid conflicts.
Permissions
By design, blockchain networks are fully permissionless, allowing anyone to transact and deploy smart contracts. However, certain use cases require permissioning to control who can participate in transactions or deploy contracts. On Avalanche, permissioning is an optional feature for Layer 1 blockchains that may or may not be activated, depending on the network's needs.
Tokenomics
Tokenomics in Layer 1 blockchains on the Avalanche network are highly flexible, allowing developers to tailor economic models to their specific needs. Each L1 can define its own native token, specifying its initial allocation, distribution mechanism, and whether it should be mintable for ongoing issuance. This enables a wide range of economic designs, from fixed-supply tokens to inflationary models that support network sustainability.
Transaction Fees & Gas
In addition to the native token, you can also configure the transaction fees (also known as gas fees). This allows Avalanche L1s to define the desired or maximal throughput of the blockchain differently.
Is this guide helpful?
