> For the complete documentation index, see [llms.txt](https://docs-old.zus.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-old.zus.network/guides/setup-a-blockchain/step-5-register-a-wallet-using-zboxcli.md).

# Step 5 : Create a wallet using zwalletcli

This part assumes that your sharder, and miner containers are perfectly running. In this part, we will create a wallet using zwalletcli and then start the blobber using the wallet id.

1. [Install zwalletcli ](https://docs.zus.network/guides/zwallet-cli/get-started#install-zwalletcli), [configure zwallet network](/guides/zwallet-cli/get-started.md#configure-zwallet-network) and [create wallet](https://docs.zus.network/guides/zwallet-cli/get-started#creating-a-wallet). 
2. Once the wallet is created . Navigate back to the .zcn folder

```
cd $HOME/.zcn/
```

3. Open the `wallet.json` file. It should be similar to the similar to the output below:

```
{"client_id":"xxxxxxxxxxxxxxxxxxxxxxxx",
"client_key":"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"keys":[{"public_key":"xxxxxxxxxxxxxxxxxxxxxxxxxxxxx">
"private_key":"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"}],
"mnemonics":"xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
"version":"1.0","date_created":"xxxxxxxxxxxxxxxxxxxxxx"}
```

4. Copy the wallet `client_id` value and paste it into blobbers and validators settings. These are found in `blobber/config` directory. 
5. Navigate to the blobber config directory :

```
cd blobber/config
```

You will see blobber and validation files listed

```
~/blobber/config$ ls
0chain_blobber.yaml  0chain_validator.yaml  localhost.crt  localhost.key
```

6. Open both the configuration files `0chain_blobber.yaml` `0chain_validator.yaml` and edit the `delegate_wallet` value with `client_id` copied from wallet.\
   \
   Here is a sample configuration file below:

```
# [configurations above]

# for testing
#  500 MB - 536870912
#    1 GB - 1073741824
#    2 GB - 2147483648
#    3 GB - 3221225472
capacity: 1073741824 # 1 GB bytes total blobber capacity
read_price: 0.01     # token / GB for reading
write_price: 1.00    # token / GB for writing
# min_lock_demand is value in [0; 1] range; it represents number of tokens the
# blobber earned even if a user will not read or write something
# to an allocation; the number of tokens will be calculated by the following
# formula
#
#     allocation_size * write_price * min_lock_demand
#
min_lock_demand: 0.1
# max_offer_duration restrict long contacts where,
# in the future, prices can be changed
max_offer_duration: 744h # 31 day
challenge_completion_time: 1m # 15m # duration to complete a challenge

# delegate wallet for all rewards, if it's empty, then blobber ID used
delegate_wallet: 'b145bf241eab00c9865a3551b18028a6d12b3ef84df8b4a5c317c8d184a82412'
```

7. Create a `network.yaml` file in your `~/.zcn` directory and add the following lines of code 

   <pre class="language-yaml" data-line-numbers><code class="lang-yaml">miners:
     - http://localhost:7071
     - http://localhost:7072
     - http://localhost:7073
   sharders:
     - http://localhost:7171
   </code></pre>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs-old.zus.network/guides/setup-a-blockchain/step-5-register-a-wallet-using-zboxcli.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.