Deploying a DApp instance

You can use Evernode developer kit to deploy your HotPocket DApps on Evernode. Evernode developer kit internally interacts with Evernode (via Xahau) to create Evernode instances and deploy your DApps on the Evernode network.

You have learned how to develop and test your DApps locally with hpdevkit in the HotPocket tutorials. Now let’s see how you can acquire instances from Evernode and deploy the DApp you’ve implemented.

Install Evernode developer kit

Follow installation instructions to install Evernode developer kit on your PC.

Acquire an instance

Note: For following steps you can choose either mainnet or testnet. Default will be mainnet, If you want change you need to set the environment variable as follows.

# Windows (command prompt)
set EV_NETWORK=testnet

# Windows (powershell)
$env:EV_NETWORK=testnet

# Linux (bash)
export EV_NETWORK=testnet

First you need to have an Xahau account with EVRs for the tenant. For the Evernode testnet, you can generate an account with 6000 EVRs using the test account generator (Use EV_NETWORK, EV_SERVER env variables to specify custom network or server).
Then you need to prepare a user key pair for the Evernode instance.

Run below command to prepare a new key pair.
```
evdevkit keygen
```

This will output the generated key pair as follows.

New key pair generated {
   privateKey: 'ed797ecd191b0364db559896c648c21cda7763db551a97577ed9ffb0ebb41881d8f9d1af6ff29af9287b0411758aac472016fb186220ef39db7959294c28857909',
   publicKey: 'edf9d1af6ff29af9287b0411758aac472016fb186220ef39db7959294c28857909'
}

Now you need to set environment variables for tenant secret and user private key.

# Windows (command prompt)
set EV_TENANT_SECRET=snmyH19JLWVaUJKtM4cNxTT6t38eA
set EV_USER_PRIVATE_KEY=ed797ecd191b0364db559896c648c21cda7763db551a97577ed9ffb0ebb41881d8f9d1af6ff29af9287b0411758aac472016fb186220ef39db7959294c28857909

# Windows (powershell)
$env:EV_TENANT_SECRET=snmyH19JLWVaUJKtM4cNxTT6t38eA
$env:EV_USER_PRIVATE_KEY=ed797ecd191b0364db559896c648c21cda7763db551a97577ed9ffb0ebb41881d8f9d1af6ff29af9287b0411758aac472016fb186220ef39db7959294c28857909

# Linux (bash)
export EV_TENANT_SECRET=snmyH19JLWVaUJKtM4cNxTT6t38eA
export EV_USER_PRIVATE_KEY=ed797ecd191b0364db559896c648c21cda7763db551a97577ed9ffb0ebb41881d8f9d1af6ff29af9287b0411758aac472016fb186220ef39db7959294c28857909

Let’s override the HotPocket configuration in the Evernode instance. You can skip this step if you do not want to.

Create a new json file anywhere you prefer.

Add following the content inside the file.

{
  "contract": {
    "consensus": {
      "roundtime": 6000
    }
  },
  "mesh": {
    "peer_discovery": {
      "enabled": true,
      "interval": 10000
    }
  }
}

See Hotpocket configuration reference for more details.

Now set the json file path as EV_HP_INIT_CFG_PATH environment variable.

# Windows (command prompt)
set EV_HP_INIT_CFG_PATH=<Path to your initial HotPocket configuration file>

# Windows (powershell)
$env:EV_HP_INIT_CFG_PATH=<Path to your initial HotPocket configuration file>

# Linux (bash)
export EV_HP_INIT_CFG_PATH=<Path to your initial HotPocket configuration file>

Now you are ready to acquire an Evernode instance. Use the acquire command and pass the Xahau address of the host as a parameter to acquire an instance. You can check the available hosts by using the Community Dashboards or the list command.

Run the following command to acquire. Replace <host Xahau address> with the host address.
```
evdevkit acquire <host-Xahau-address>
```

This will create an Evernode instance in a random host and outputs the instance details

...
Instance created! {
   name: '00010000414A6FB83385362D61A89FDE24414914AE05FCB8AACE82C400000029',
   pubkey: 'edbf186b1bbedf0a3e7351ec969d0aeee40b45831fd924db0a129663ec5920992d',
   contract_id: '020e552d-11f9-4707-a8c0-eecd6f4289da',
   peer_port: '22861',
   user_port: '8081',
   gp_tcp_port: '36525',
   gp_udp_port: '39064',
   domain: 'node2.aksumwealth.xyz',
   outbound_ip: '5.78.76.104',
   created_timestamp: 1695605217865
}

You can specify more options (Ex: -m specify life moments) to the acquire command. Check the supported options using the below command.
```
evdevkit acquire --help
```

At this point, you have acquired an Evernode instance successfully and you have the instance details including public key, IP, ports etc.

Create deployable DApp package

If you have already implemented the DApp, you can proceed. Otherwise, go through HotPocket tutorials.
Build your DApp and note down the build path.

Let’s override the contract section HotPocket configuration in the Evernode instance. You can skip this step if you do not want to.

Create a new json file anywhere you prefer.

Add following content inside the file.

{
  "contract": {
    "consensus": {
      "roundtime": 2000
    }
  }
}

See Hotpocket configuration reference for more details.

Now set the json file path as EV_HP_OVERRIDE_CFG_PATH environment variable.

# Windows (command prompt)
set EV_HP_OVERRIDE_CFG_PATH=<Path to your override HotPocket configuration file>

# Windows (powershell)
$env:EV_HP_OVERRIDE_CFG_PATH=<Path to your override HotPocket configuration file>

# Linux (bash)
export EV_HP_OVERRIDE_CFG_PATH=<Path to your override HotPocket configuration file>

Now you can create the DApp package
- Run the following command. Assuming this is a node contract last binary path and binary args parameters will be /usr/bin/node and index.js.
```
evdevkit bundle $HOME/contract edbf186b1bbedf0a3e7351ec969d0aeee40b45831fd924db0a129663ec5920992d /usr/bin/node -a index.js
```
  - Note:
    - Replace $HOME/contract with your contract directory path (Path to build directory of contract binaries).
    - Replace edbf186b1bbedf0a3e7351ec969d0aeee40b45831fd924db0a129663ec5920992d with your instance’s public key.
    - Replace /usr/bin/node index.js with your binary path and arguments.
- This will bundle your DApp and outputs the path to the zip file.
```
...
Archive finished. (location: $HOME/bundle/bundle.zip)
```

Deploy DApp to the Evernode instance

Now you have the deployable contract bundle, We can deploy this bundle to the acquired Evernode instance.
EV_USER_PRIVATE_KEY is required for this step. Since we’ve already set this in acquire instance step, we do not need to set this again.
- Make sure you use the same user keys that you’ve set when acquiring the instance, Otherwise you won’t be allowed to upload this bundle.
Now let’s upload the bundle to the Evernode instance.
- Run the following command to upload the bundle.
```
evdevkit deploy $HOME/bundle/bundle.zip 66.42.63.218 8081
```
- This will deploy the contract and output following if successfully uploaded.
```
...
Contract bundle uploaded!
```
You can test the uploaded contract by implementing a user client same as you did in HotPocket basics tutorial.

Acquire and deploy an instance in one go

Using Evernode devkit you can acquire and deploy Evenode instances using one command.

First you need to follow the same 1, 2, 3 steps in “Acquire an instance” here as well.
Pick a host to acquire an instance from. You can check the available hosts by using the Community Dashboards or the list command.
If you are going to override the HotPocket config contract section, follow 3rd step in “Create deployable DApp package”.

Now you can just run the following command to acquire and deploy.

Run this command.
```
evdevkit acquire-and-deploy $HOME/contract /usr/bin/node r9kCyGhhwGj3KaSGemFrrPVpXkzVtT2b1N -a index.js
```
- Note:
  - Replace $HOME/contract with your contract directory path (Path to build directory of contract binaries).
  - Replace /usr/bin/node index.js with your binary path and arguments.
  - Replace r9kCyGhhwGj3KaSGemFrrPVpXkzVtT2b1N with the Xahau address of the host you want to acquire an instance from.

This will output the following after deploying the contract.

...
Instance created! {
   name: '000100004B2CDD9D208422C913DFB2EDB880FCA30D653644920E65060000006B',
   pubkey: 'ede6d05dc23bf9aba9cabf6de65d280acc0ba3f2a356484af28b140a125308705d',
   contract_id: '7902171c-3d34-4c10-a5f7-d436e3525852',
   peer_port: '22861',
   user_port: '8081',
   domain: 'node2.aksumwealth.xyz',
   outbound_ip: '5.78.76.104',
   created_timestamp: 1695605219865
}
...
Archive finished. (location: $HOME/bundle/bundle.zip)
...
Contract bundle uploaded!
Contract deployed!

You can specify more options (Ex: -c specify a Contract id) to the acquire-and-deploy command. Check the supported options using below command.
```
evdevkit acquire-and-deploy --help
```

Next: Deploying a cluster