> For the complete documentation index, see [llms.txt](https://docs.kiiglobal.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiiglobal.io/docs/validate-the-network/run-a-validator-full-node/step-by-step-guide/recovering-legacy-addresses.md).

# Recovering Legacy Addresses

With the upcoming Kiichain upgrade, wallet key handling is changing to support Ethereum-compatible tooling and address formats. This guide explains what's changing and how to recover your old wallets safely.

## What’s Changing?

#### **1. New Key Type**

* Old Type: `secp256k1` 
* New Type: `eth_secp256k1` 

> This enables Ethereum-compatible signatures (e.g., MetaMask, Keplr EVM support).

**2. New Coin Type**

* Old Coin Type: `118` (standard Cosmos)
* New Coin Type: `60` (Ethereum standard)

> This changes the way addresses are derived from your mnemonic.

## Recovering Existing Wallets

To recover old wallets (e.g., validator rewards wallets or delegator accounts) that were created before the upgrade:

```bash
kiichaind keys add <key_name> \
  --keyring-backend test \
  --recover \
  --coin-type 118 \
  --key-type secp256k1
```

* Replace `<key_name>` with your desired key name.
* Input your existing **mnemonic** when prompted.

## Need to Check What Type a Key Was Created With?

Unfortunately, `kiichaind keys list` **does not show the coin type**. You’ll need to recall which mnemonic was created with which derivation path. To avoid confusion:

* Use **clear key names** like `validator_old`, `wallet_eth`.
* Document the **coin type** and **key type** when generating keys.


---

# 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:

```
GET https://docs.kiiglobal.io/docs/validate-the-network/run-a-validator-full-node/step-by-step-guide/recovering-legacy-addresses.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.