Get started with Kadena Chainweb EVM

The Kadena network relies on nodes that run the Chainweb consensus protocol. When Ethereum transitioned from a Proof-of-Work consensus model to a Proof-of-Stake consensus model, it effectively split the blockchain into separate consensus and execution layers. This change to the architecture enabled the Ethereum Virtual Machine (EVM) to provide an execution environment that is agnostic about the underlying consensus. Because the execution layer operates independently, Chainweb nodes can provide the same EVM execution environment running in parallel with Pact while maintaining the Chainweb Proof-of-Work consensus, security, and decentralization over a multi-chain network.

How it works

The Chainweb consensus protocol enables multiple independent chains to share a common view of state beyond a certain block depth. This common view of state enables any chain in the network to verify whether historical events beyond the required block depth occurred on any other chain. For example, if a transaction occurs on chain 3, chain 3 can produce a simple payment verification (SPV) proof that chain 6 can verify by checking the shared history. The only requirement for verifying the transaction is that the proof must be conveyed from the original chain, in this example, chain 3—to the target chain, in this example, chain 6.

With this approach, security relies strictly on the shared consensus across the chains in the network. There are no relayers, oracles, validators, archives, or third-party coordinators.

The chains in the Kadena Chainweb EVM network run in parallel, but independently, allowing for concurrent transaction processing without the risk of collisions or delays. Because Chainweb provides a single common view of state, global security, and concurrent payload processing, Kadena Chainweb EVM enables cross-chain transactions to be executed more efficiently and at a lower cost than traditional bridging techniques.

At a high level, Kadena Chainweb EVM supports cross-chain activity in three main steps:

• An event occurs on a source chain.

  For a cross-chain transfer, a user initiates a transaction to transfer tokens from a source chain using a smart contract. The smart contract emits a well-defined cross-chain event.

• An off-chain endpoint generates proof of a specific event.

  For a cross-chain transfer, a user queries an endpoint that generates a simple payment verification proof or another type of proof that can be validated. The proof must encode all of the information required to uniquely identify the event on the source chain and the contract on the target chain.

• The event is observed on the target chain.

  For a cross-chain transfer, a user relays the proof to the target chain, where it is verified against the history shared by the source and target chains. By checking the shared history, the contract on the target chain validates that the transfer event claimed by the user occurred on the source chain. The smart contract on the target chain completes the transaction, for example, by minting the number of tokens transferred from the source chain.

Chainweb EVM development environment

The kadena-evm-sandbox repository provides tools and configuration files for developers interested in setting up a private local development environment for testing the Ethereum Virtual Machine (EVM) execution environment running on Chainweb nodes that provide the infrastructure for the Kadena blockchain network.

The repository includes a default configuration for a docker compose image that is optimized for basic frontend development with an EVM-compatible node as the backend. The default configuration includes chains 0 through 19 for Pact smart contracts and chains 20 though 24 for Solidity contracts.

What's included in the repository

The kadena-evm-sandbox repository provides everything you need to set up a local Kadena development network that runs a single Chainweb node with core backend services and a mining client. The default configuration for the development network provides five chains that use EVM as the payload provider for processing transactions.

The repository includes the following directories and components:

Name	What it provides
allocations	Files to set up an ethers project that describes a set of BIP-44 wallets and allocations to be created in the genesis block for the development network.
apps	Files to set up the contract, server, and frontend application that demonstrates cross-chain transactions.
blockscout	Files to set up an optional block explorer for the EVM chains in the development network. Blockscout instances provide an explorer interface and API similar to Etherscan.
devnet	A Docker compose project and files to set up the Chainweb node services for the development network.
docker‑bake.hcl	A script to build multi-platform images for the development network Docker compose project.
docs	Technical documentation about the functions and events proposed for the Kadena Chainweb EVM cross-chain bridging protocol in draft form.
network	An optional command-line program for starting, stopping, and monitoring the Kadena Chainweb EVM development network.
solidity	A Hardhat project that demonstrates the implementation of a simple ERC-20 token with support for burn and mint style transfers between the two EVM chains in the network.

Prerequisites and system requirements

Before you set up the Kadena Chainweb EVM development environment, verify that your local computer has the required tools installed and meets the following basic requirements:

• You must have Docker and Docker Compose or an Open Container Initiative (OCI) compliant alternative.
• You must have at least 4 CPU cores and 8 GB of memory available for Docker. You can configure CPU and memory for Docker using command-line options or Resource settings.
• You must have a network connection to download the container images for the development network.
• You must have a POSIX-compliant terminal shell for running command-line programs and scripts.
• You should have bash and jq programs installed.
• You must have JavaScript tooling installed, including Node.js version v22, the npm or yarn package manager, and npx to deploy Solidity contracts with Hardhat.
• You must have at least 6 CPU cores and 12 GB of memory available for Docker to run the Blockscout block explorer.

Quick start

To download and install the Chainweb EVM development network:

1. Open a terminal shell on your computer.

2. Clone the kadena-evm-sandbox repository and change to the kadena-evm-sandbox directory by running the following command:

   git clone https://github.com/kadena-io/kadena-evm-sandbox && cd kadena-evm-sandbox

   The kadena-evm-sandbox directory includes the network command-line program that you can use to perform common tasks to manage and monitor the development network. The network program supports commands that are similar to Docker commands. You can explore all of the commands available by running the following command:

   ./network help

3. Pull the latest container images using the network command-line program by running the following command:

   ./network devnet pull

   You can execute network commands for convenience or use docker commands directly. Pulling the latest container images isn't strictly required, but it's recommended before you start the development network for the first time.

   You should see output similar to the following:

   [+] Pulling 10/10
    ✔ bootnode-evm-22 Skipped - Image is already being pulled by bootnode-evm-21               0.0s
    ✔ bootnode-evm-20 Skipped - Image is already being pulled by bootnode-evm-21               0.0s 
    ✔ bootnode-evm-24 Skipped - Image is already being pulled by bootnode-evm-21               0.0s 
    ✔ bootnode-evm-23 Skipped - Image is already being pulled by bootnode-evm-21               0.0s 
    ✔ bootnode-mining-client Pulled                                                            1.7s
    ✔ allocations Pulled                                                                       1.7s
    ✔ bootnode-frontend Pulled                                                                 1.7s
    ✔ bootnode-mining-trigger Pulled                                                           1.8s
    ✔ bootnode-evm-21 Pulled                                                                   1.7s
    ✔ bootnode-consensus Pulled                                                                1.8s
      ✔ 63467be34da6 Pull complete                                                            34.9s 
      ✔ 036ac59a35be Pull complete                                                             6.4s 
      ✔ 4a057fff0021 Pull complete                                                             6.3s 

4. Start the network by running the following command:

   ./network devnet start

   This command starts the development blockchain and allocates the test account addresses. You should see output similar to the following excerpt:

   [+] Running 3/4
    ✔ Network chainweb-evm_bootnode-internal      Create...                                    0.1s 
    ✔ Network chainweb-evm_p2p                    Created                                      0.0s 
    ✔ Network chainweb-evm_bootnode-frontend      Create...                                    0.0s 
    ⠋ Volume "chainweb-evm_bootnode-evm-22_data"  Cr...                                        0.0s
   ...
    ✔ Container bootnode-evm-23                   Started                                      1.2s
    ✔ Container bootnode-evm-20                   Started                                      1.2s
    ✔ Container bootnode-evm-22                   Started                                      1.3s 
    ✔ Container bootnode-evm-24                   Started                                      1.7s 
    ✔ Container bootnode-evm-21                   Started                                      1.2s 
    ✔ Container bootnode-allocations              Started                                      1.5s 
    ✔ Container bootnode-consensus                Healthy                                      9.3s 
    ✔ Container bootnode-frontend                 Started                                      9.7s 
    ✔ Container bootnode-mining-trigger           Started                                      9.5s 
    ✔ Container bootnode-mining-client            Started                                      9.6s 
   [+] Creating 1/1
    ✔ Container bootnode-evm-20    Running                                                     0.0s 
   wallets created: {
     alloc0: {
       address: '0x8849BAbdDcfC1327Ad199877861B577cEBd8A7b6',
       privateKey: '0xe711c50150f500fdebec57e5c299518c2f7b36271c138c55759e5b4515dc7161'
     },
   ...

5. Check that blocks are being produced by running the following command:

   ./network devnet status

   This command displays the current block height and cut height for the development network with output similar to the following excerpt:

   Node: bootnode-consensus
   chain        height  hash                                         type
   0            36      G1BY2DprJ6ULTaPOt67XEDtjw03gVgu4IHXsYhHgUfs  default
   1            35      Euw83eOfY1DTbQIHOnETvNYjAW6hvxMZ4RDeZWsmuzI  default
   2            36      dPs3Tj6ug0c7NyG0v-XbyZdXh2QZh_WvyvZHu6uk4_I  default
   3            36      OoC9hTEJmPVj3pMcjPwM0qofXS4wN4172aL5ffN2om4  default
   4            36      GKNU8tzdtLNXudlvRv5orVQ8bFXN0F7pQ63MlavtE88  default
   ...
   20           37      dsrjWRrIgsezR2InWb3EzMml28owAmIQLh20fdHVrqs  evm
   21           36      j9fI_MQEYboaqx2qu2MtyBjKGTsJHb9FMq8ktVPq4zw  evm
   22           36      _6quxrPShEpb0hyd3jB2VNdlQq2xmsPZFOgku4iA5SY  evm
   23           37      Q_muuzU3TUZH0n1kP74tmW7VMIuelsrlGRW8TnYwqVE  evm
   24           36      pUattWugcCjy_2_0ejgTx1SqaeHGvtV_nWA_Fc5PGnw  evm
   ...
   cut-height:  3529

   You can call the ./network devnet status command repeatedly to verify that the block height and cut height values are increasing.

Restarting the development network

If the development network stops producing blocks or seems stuck, you can restart the bootnode-consensus service without stopping or restarting other network components.

To restart the development network:

./network devnet restart

Stopping the development network

When you're finished testing, you can shut down the development network, remove all containers, and reset the database to a clean state.

To shut down the network and remove containers:

./network devnet stop

In some cases, you might find that stopping or restarting the network fails to return the container to a clean state. If this problem occurs, run the following command to forcibly remove orphan processes:

docker compose down --volumes --remove-orphans

After removing all containers and processes, you should be able to restart the network in a clean state.

Modifying the network configuration

The devnet folder in the kadena-evm-sandbox repository includes a Python script, compose.py, that generates the docker-compose.yaml file for the Chainweb EVM Docker Compose project. The compose.py script automates the creation of the docker-compose.yaml file with different configuration settings for the following predefined project use cases:

• The app-dev project generates a configuration file optimized for application development with a single full-service bootstrap node. This configuration produces blocks at a fixed rate of two seconds per chain, has mining enabled, and exposes the Chainweb service API on the chains you specify as command-line arguments.
• The kadena-dev project generates a configuration file that simulates a production environment with four node roles: one bootstrap node, one application development node, and two mining nodes. This configuration is optimized for testing and debugging Chainweb node backend services, such as consensus and peer-to-peer networking.
• The minimal project generates a configuration file for a minimal development environment with one bootstrap node and simulated mining.

To generate a docker-compose.yaml for one of the predefined project use cases, add the --project command-line option and the use case project name to the compose.py script. For example, you can run the following command to generate a docker-compose.yaml file that simulates a production environment and then starts the network using that configuration:

python3.13 compose.py --project kadena-dev > docker-compose.yaml && docker compose up -d

To generate a docker-compose.yaml that's optimized for application development, you can run a command similar to the following:

python3.13 compose.py --project app-dev --exposed-chains "3, 20" > docker-compose.yaml && docker compose up -d

This example only exposes the Chainweb service API on one Pact chain (3) and one EVM chain (20). You can run compose.py script to generate the docker-compose.yaml file for any of the predefined project configurations. Alternatively, you can modify the compose.py script or write your own script to customize the development environment settings you want to use.

Test the sample Solidity project

The solidity directory provides an example of a simple Hardhat project with a Hardhat configuration file, Solidity smart contract, and test files. The project is also configured by default use to the @kadena/hardhat-chainweb and @kadena/hardhat-kadena-create2 Hardhat v2 plugins.

• The @kadena/hardhat-chainweb plugin simplifies deployment to multiple chains without requiring you to configure individual chains as external networks when using Hardhat v2, and later. The plugin also supports smart contract verification. The sandbox configuration settings in the Hardhat configuration file for the solidity project provide an example of using the @kadena/hardhat-chainweb plugin to define a five-chain network.

• The @kadena/hardhat-kadena-create2 supports Create2 to enable you to deploy a smart contract with the same address on all chains.

The solidity project also includes a devnet-accounts.json file with account information generated from a test BIP-44 wallet using a seed entropy value of 0x0000 0000 0000 0000 0000 0000 0000 0000 (16 zero bytes). The Hardhat configuration file reads this account information to generate accounts for you to use in the local sandbox development network configuration.

Installing dependencies

You can install Hardhat and related dependencies in the development network, if needed, by running the following command:

./network solidity setup

If the npm package manager reports any issues, address them before continuing to the next step. For example, you might be prompted to run npm audit fix to address issues.

Running tests

You can develop, test, and deploy Solidity contracts using standard Hardhat commands. For example, you can run the unit tests for the SimpleToken contract against the internal Hardhat v2 network:

npx hardhat test

The solidity project also provides sample npm scripts to perform common tasks. To execute unit tests for the SimpleToken contract using a sample npm script, run:

npm run test

The SimpleToken tests deploy the sample ERC-20 token contract and check that token transfer operations succeed or revert as expected when tokens are transferred between addresses on two Chainweb EVM chains. For example, you should see output similar to the following excerpt as tests are executed and new blocks are added to the chain:

Chainweb:  hardhat  Chains:  5  

[hardhat -] creating chains
[hardhat -] integrating chains into Chainweb
[hardhat -] Starting chain networks
Creating provider
Creating provider
...
Transferring 500000000000000000000 tokens from 20:0x5FbDB2315678afecb367f032d93F642f64180aa3:0x70997970C51812dc3A010C7d01b50e0d17dc79C8 to 21:0x5FbDB2315678afecb367f032d93F642f64180aa3:0x70997970C51812dc3A010C7d01b50e0d17dc79C8
Initiating cross-chain transfer from chainweb_hardhat20 to chainweb_hardhat21
Switched to 20
[hardhat 20] mining requested
[hardhat 20] current height is 16
[hardhat 21] current height is 15
...
transfer-crosschain status: 1, at block number 17 with hash 0x2ac3ff7aa6dae262355da187088b9f79b70ac62309b1870a65765fea38a959e7
found log at tx 0 and event 1
waiting for SPV proof to become available on chain 21; current height 16; required height 18
[hardhat 21] mining requested
[hardhat 21] current height is 16
[hardhat 22] current height is 15
...
waiting for SPV proof to become available on chain 21; current height 17; required height 18
[hardhat 21] mining requested
[hardhat 21] current height is 17
[hardhat 22] current height is 16
...
Hex proof: 0x8b950f0e...01b1ae4d6e
Switched to 21
Redeeming tokens on chain chainweb_hardhat21
[hardhat 21] mining requested
[hardhat 21] current height is 18
[hardhat 20] current height is 17
...
result at block height 19 received with status undefined
   ✔ Should transfer tokens to same address from one chain to another (239ms)
...
   38 passing (2m)
   1 pending

[hardhat -] Stopping chain networks
[hardhat 20] Automine disabled
[hardhat 21] Automine disabled

Deploying

To deploy the SimpleToken contract against the local sandbox development network using the npm script, run:

npm run deploy sandbox

To deploy deterministically with the same address on all chains using Create2, run:

npm run deploy-create2 sandbox

To deploy the SimpleToken contract to the internal Hardhat network, run:

npm run deploy:hardhat

To deploy deterministically with the same address on all chains using Create2, run:

npm run deploy-create2:hardhat

Starting a local node

To start a separate Hardhat node, run:

npx hardhat node

After starting the node, open another terminal, then run:

npm run deploy localhost

To deploy deterministically with the same address on all chains using Create2, run:

npm run deploy-create2 localhost

Integrating with other Hardhat projects

If you want to experiment with using the Chainweb EVM development environment with other Hardhat projects, you must configure the Hardhat project to connect to the Chainweb EVM development environment much like you would configure a project to connect to an external network. You must also configure the Hardhat project to include account information—addresses and balances—for all available accounts.

You can use the solidity project as a template for how configure your Hardhat environment to use the @kadena/hardhat-chainweb plugin to develop, test, and deploy smart contracts using Hardhat v2 into local, test, and production Chainweb networks.

After a project is configured to use the Chainweb EVM development configuration settings and accounts, you can compile, test, and deploy the project using standard Hardhat commands. You can also compile, test, and deploy using any of the sample npm scripts included in the solidity project.

The project includes the following npm scripts to perform common tasks:

"scripts": {
  "build": "npx hardhat compile",
  "test": "npx hardhat test",
  "deploy:hardhat": "hardhat compile && npx hardhat run scripts/deploy.js",
  "deploy-create2:hardhat": "hardhat compile && npx hardhat run scripts/deploy-using-create2.js",
  "deploy": "hardhat compile && npx hardhat run scripts/deploy.js --chainweb",
  "deploy-create2": "hardhat compile && npx hardhat run scripts/deploy-using-create2.js --chainweb"
},

With these scripts, you can compile, test, and deploy the SimpleToken using npm run commands. For example, you can deploy a project with the same address on all chains by running the following command:

npm run deploy-create2 sandbox

Modifying the Hardhat project

To integrate with the Chainweb EVM development network:

1. Copy the solidity/devnet-accounts.json file into the root directory of your Hardhat project.

2. Install the @kadena/hardhat-chainweb and @kadena/hardhat-kadena-create2 plugins in the root directory of your project:

   npm install @kadena/hardhat-chainweb @kadena/hardhat-kadena-create2

3. Open the hardhat.config.js or hardhat.config.ts file for your Hardhat project in your code editor.

4. Copy and paste the code to import plugins and read account information from the solidity/hardhat.config.js file into the Hardhat configuration file for your project.

   For example:

   require("@nomicfoundation/hardhat-toolbox");
   require('@kadena/hardhat-chainweb');
   require('@kadena/hardhat-kadena-create2');
   require("hardhat-switch-network");
   require("@nomicfoundation/hardhat-verify");
   
   const { readFileSync } = require("fs");
   
   const devnetAccounts = JSON.parse(
     readFileSync("./devnet-accounts.json", "utf-8")
   );

5. Copy and paste the code to configure network information from the solidity/hardhat.config.js file into the Hardhat configuration file for your project.

   For example:

   chainweb: {
        hardhat: {
          chains: 2,
      },
      sandbox: {
        type: 'external',
        chains: 5,
        accounts: devnetAccounts.accounts.map((account) => account.privateKey),
        chainIdOffset: 1789,
        chainwebChainIdOffset: 20,
        externalHostUrl: "http://localhost:1848/chainweb/0.0/evm-development/"
      }
    },

   Be sure to include the accounts key with mapping for accounts to private keys in the Chainweb EVM configuration settings.

   You can also modify the configuration settings in the hardhat.config.js or hardhat.config.ts file to customize the development environment to suit your needs. For example, if you want the sandbox configuration to have two EVM chains instead of five, modify the chains setting:

   ...
   sandbox: {
      type: 'external',
      chains: 2,
      accounts: devnetAccounts.accounts.map((account) => account.privateKey),
   ...
   }  

6. (Optional) Copy and paste the code to configure etherscan settings from the solidity/hardhat.config.js file to use Blockscout into the hardhat.config.js or hardhat.config.ts file for your project.

   Note that you must configure these settings if you want Blockscout to verify your smart contract.

   For example:

   etherscan: {
     apiKey: 'abc', // Any non-empty string works for Blockscout
     apiURLTemplate: 'http://chain-{cid}.evm.kadena.internal:8000/api/',
     browserURLTemplate: 'http://chain-{cid}.evm.kadena.internal:8000/',
   },

   After updating the Hardhat configuration file, you should have a hardhat.config.js or hardhat.config.ts file with configuration settings similar to the following:

    sandbox: {
      type: 'external',
      chains: 5,
      accounts: devnetAccounts.accounts.map((account) => account.privateKey),
      chainIdOffset: 1789,
      chainwebChainIdOffset: 20,
      externalHostUrl: "http://localhost:1848/chainweb/0.0/evm-development",
      etherscan: {
        apiKey: 'abc', // Any non-empty string works for Blockscout
        apiURLTemplate: 'http://chain-{cid}.evm.kadena.internal:8000/api/',
        browserURLTemplate: 'http://chain-{cid}.evm.kadena.internal:8000/',
      },
   },

7. Save your changes and close the hardhat.config.js or hardhat.config.ts file.

Compiling and testing integration

After configuring your Hardhat project to use the Chainweb EVM development environment, you can compile, test, and deploy the project using standard hardhat commands. For example, you can compile the project by running the following command:

npx hardhat compile

You should see that your project compiles successfully:

Compiled 1 Solidity file successfully (evm target: prague).

Alternatively, you can use the npm convenience scripts. For example, to deploy a Hardhat project on the Chainweb EVM you have configured for development:

npm run deploy:hardhat

Specifying the Chainweb EVM development environment

One of the primary advantages of using the @kadena/hardhat-chainweb plugin is that it is specifically designed to enable you to interact with multiple Chainweb chains. By default, you can configure multiple networks for Hardhat, but not multiple chains in the same network. With the @kadena/hardhat-chainweb plugin, you can configure the Chainweb EVM development environment to run as a typical Hardhat network. You can maintain Hardhat as the default network and deploy a project using a specific set of Chainweb EVM configuration settings—like the sandbox settings in the solidity project—with a command like this:

npx hardhat run scripts/deploy.js --chainweb sandbox

In this command, the --chainweb command-line option behaves like the Hardhat --network option to specify the environment you want to deploy into. If you want to deploy into the Chainweb EVM sandbox environment by default, you can add a defaultChainweb key to your Hardhat configuration file.

To run scripts against the Chainweb EVM development sandbox environment:

1. Open the hardhat.config.js or hardhat.config.ts file for your Hardhat project in your code editor.

2. Add defaultChainweb to the network settings:

   For example:

   chainweb: {
      hardhat: {
        chains: 2,
      },
    sandbox: {
      type: 'external',
      chains: 5,
      accounts: devnetAccounts.accounts.map((account) => account.privateKey),
      chainIdOffset: 1789,
      chainwebChainIdOffset: 20,
      externalHostUrl: "http://localhost:1848/chainweb/0.0/evm-development/"
    },
   },
   defaultChainweb: 'sandbox',

3. Run hardhat deployment script or the npm run deploy command:

   For example, if you are using a hardhat deployment script:

   npx hardhat run scripts/deploy.js

   For more information and examples of using the @kadena/hardhat-chainweb plugin, see the Kadena Hardhat Chainweb plugin.

   For more information about deterministic deployment to Chainweb EVM chains, see the Kadena Hardhat Create2 plugin.

Signing transactions and switching chains

By default, when you call a Solidity smart contract from a test file or a script using ethers, the transaction is executed by the first signer address and private key for the local development environment. This is true whether the local development environment is the default Hardhat network or the Kadena Chainweb EVM development environment. For example, the following transferCrossChain transaction is signed by the account that corresponds to the first address in the list of addresses for the current network context:

const tx = await token0.transferCrossChain(receiver.address, amount, token1Info.chain);

This address is the msg.sender for the transaction and is displayed as the deploying signer when you execute the SimpleToken tests. The address is retrieved by calling the getSigners function in the solidity/test/utils/utils.js file.

Typically, if you wanted to call a smart contract function using a different signer—for example, alice—you could call the function like this:

const tx = await token0.connect(alice).transferCrossChain(receiver.address, amount, token1Info.chain);

In ethers tests, this call creates a new contract instance using the new signer alice in the background. It's important to note, however, that the signer address always has a network context associated with it.

For contracts deployed on Chainweb EVM, the network context is slightly more complex because you must know the Chainweb chain identifier where the contract is deployed to get the correct signing address.

For example, if you want to call a contract with a specific signer, you must call await chainweb.switchChain(chainId); to switch to the correct chain so that you get signers with the correct network context for that chain.

However, if you install the @kadena/hardhat-chainweb plugin, you can use the runOverChains function to handle the chain switching for you. You can find examples of switching chains in the solidity/test/SimpleToken.test.js and solidity/test/SimpleToken.integration.test.js test files.

Blockscout

You can explore the Chainweb EVM development network chains using the optional Blockscout application. Blockscout is a blockchain monitoring service that provides a user experience that is similar to Etherscan.

For additional information, see the Blockscout README.

To use Blockscout:

1. Open a terminal shell and change to the kadena-evm-sandbox directory, if needed.

2. Pull the latest images by running the following command:

   ./network blockscout pull

3. Add blockscout domains to the /etc/hosts file by running the following command:

   ./network blockscout add-domains

   This command adds the following records to the /etc/hosts file:

   • 127.0.0.1 chain-20.evm.kadena.local
   • 127.0.0.1 chain-21.evm.kadena.local
   • 127.0.0.1 chain-22.evm.kadena.local
   • 127.0.0.1 chain-23.evm.kadena.local
   • 127.0.0.1 chain-24.evm.kadena.local

4. Start a Blockscout instance by running the following command:

   ./network blockscout start

   After running this command, it can take several minutes before you can open Blockscout in a browser.

5. Open the appropriate URL for the chain you want to explore:

   chain 20: http://chain-20.evm.kadena.local:8000
   chain 21: http://chain-21.evm.kadena.local:8000
   chain 22: http://chain-22.evm.kadena.local:8000
   chain 23: http://chain-23.evm.kadena.local:8000
   chain 24: http://chain-24.evm.kadena.local:8000

   You can view transactions executed on Chainweb EVM chains using Blockscout and the following URLs.

   • Chainweb EVM chain 20
   • Chainweb EVM chain 21
   • Chainweb EVM chain 22
   • Chainweb EVM chain 23
   • Chainweb EVM chain 24

Account allocations in the development network

The chain specifications include the initial account allocations for the genesis block. All of the initial accounts are generated from a BIP-44 wallet using a seed entropy value of 0x0000 0000 0000 0000 0000 0000 0000 0000 (16 zero bytes). You can view details about how the wallet is generated in the allocations/wallet.mjs file.

You can view the addresses, private keys, and starting balances by running the following command:

./network devnet allocations

The allocations in the genesis block use the following path values:

• m/44'/1'/0'/0/0 (address: 0x8849BAbdDcfC1327Ad199877861B577cEBd8A7b6)
• m/44'/1'/0'/0/1 (address: 0xFB8Fb7f9bdc8951040a6D195764905138F7462Ed)
• m/44'/1'/0'/0/2 (address: 0x28f2d8ef4e0fe6B2E945cF5C33a0118a30a62354)
• m/44'/1'/0'/0/3 (address: 0xa24a79678c9fffEF3E9A1f3cb7e51f88F173B3D5)
• m/44'/1'/0'/0/4 (address: 0x47fAE86F6416e6115a80635238AFd2F18D69926B)
• m/44'/1'/0'/0/5 (address: 0x87466A8266b9DFB3Dc9180a9c43946c4AB2c2cb2)
• m/44'/1'/0'/0/6 (address: 0xA310Df9740eb6CC2F5E41C59C87e339142834eA4)
• m/44'/1'/0'/0/7 (address: 0xD4EECE51cf451b60F59b271c5a748A8a9F16bC01)
• m/44'/1'/0'/0/8 (address: 0xE08643a1C4786b573d739625FD268732dBB3d033)
• m/44'/1'/0'/0/9 (address: 0x33018A42499f10B54d9dBCeBB71831C805D64cE3)
• m/44'/1'/0'/0/10 (address: 0xa3659D39C901d5985450eE18a63B5b0811fDa521)
• m/44'/1'/0'/0/11 (address: 0x7e99c2f1731D3750b74A2a0623C1F1DcB8cCa45e)
• m/44'/1'/0'/0/12 (address: 0xFd70Bef78778Ce8554e79D97521b69183960C574)
• m/44'/1'/0'/0/13 (address: 0xEE2722c39db6014Eacc5FBe43601136825b00977)
• m/44'/1'/0'/0/14 (address: 0xeDD5a9185F9F1C04a011117ad61564415057bf8F)
• m/44'/1'/0'/0/15 (address: 0x99b832eb3F76ac3277b00beADC1e487C594ffb4c)
• m/44'/1'/0'/0/16 (address: 0xda1380825f827C6Ea92DFB547EF0a341Cbe21d77)
• m/44'/1'/0'/0/17 (address: 0xc201d4A5E6De676938533A0997802634E859e78b)
• m/44'/1'/0'/0/18 (address: 0x03e95Af0fC4971EdCa12E6d2d1540c28314d15d5)
• m/44'/1'/0'/0/19 (address: 0x3492DA004098d728201fD82657f1207a6E5426bd)

The mining accounts are:

• m/44'/1'/1'/0/0 (address: 0xd42d71cdc2A0a78fE7fBE7236c19925f62C442bA)
• m/44'/1'/1'/0/1 (address: 0x38a6BD13CC381c68751BE2cef97BD79EBcb2Bb31)