> For the complete documentation index, see [llms.txt](https://docs.mayaprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mayaprotocol.com/deep-dive/guides/setting-up-a-maya-wallet/how-to-create-a-maya-address-through-mayanode-cli.md).

# Through MAYANode cli

How to create a MAYAChain address through MAYANode cli

#### Create Maya address and mnemonic

1. [**Install**](https://go.dev/doc/install) `go 1.20+.`
2. Clone the [**Maya repository**](https://gitlab.com/mayachain/mayanode)**.**
3. Install [**docker**](https://docs.docker.com/engine/install/)**.**
4. Install [**protobuf**](https://grpc.io/docs/protoc-installation/) `$ git clone https://gitlab.com/mayachain/mayanode`
5. Change to the mainnet branch `$ git checkout mainnet`
6. Build the binary`$ TAG=mainnet make build && TAG=mainnet make install`
7. To add a mnemonic that you already own

```bash
$ mayanode keys add [key name] --recover
> Enter your bip39 mnemonic
[paste/write your mnemonic]
```

8. You’re done! It should look as follows:

<pre><code><strong>$ mayanode keys add [key name] --recover
</strong><strong>- name: mywallet
</strong>  type: local
  address: tmaya1gp27t2hcj603p8448qwkhfh0v4y0r3jkmdgsyn
  pubkey: '{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"A0LirKOHGVq0y1JBcadN10UvqtnvYNvg8QOn4Mj5Gy31"}'
  mnemonic: ""
</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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mayaprotocol.com/deep-dive/guides/setting-up-a-maya-wallet/how-to-create-a-maya-address-through-mayanode-cli.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.