> For the complete documentation index, see [llms.txt](https://docs.v2.like.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.v2.like.co/zh/general-guides/community/translate-wallet-prefix.md).

# #translate-wallet-prefix

雙向查詢新舊前綴錢包地址靠 translate wallet prefix

{% hint style="warning" %}
此文檔只適用於 Liker Land 和 LikeCoin v2。如需了解 [3ook.com](http://3ook.com/) 和 LikeCoin v3，請至 [docs.3ook.com](http://docs.3ook.com/) 及 [dao.like.co](https://dao.like.co/)。
{% endhint %}

LikeCoin chain 經已於 2022 年 5 月 4 日成功升級為 LaiChiKok 版本。[升級後 LikeCoin 錢包地址已改為 “like1” 新地址前綴並向後兼容舊的 “cosmos1” 前綴](https://docs.v2.like.co/zh/general-guides/wallet/like-address-prefix.md)。在 #🔁｜translate-wallet-prefix 頻道可讓用戶雙向查詢新舊前綴錢包地址，方便翻查舊記錄。

1\. 進入 #🔁｜translate-wallet-prefix 頻道。如不能輸入文字請先到 #👍｜verify 頻道進行認證。

2\. 輸入 /translate cosmos1xxxxxx，系統會返回對應的 like1xxxxxxx 新地址；相反若輸入 /translate like1xxxxxx，系統則會返回 cosmos1xxxxxx 格式的舊地址。

![輸入 /translate](https://887379602-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LL4mdaVjNgL6A1--PV0-1995411665%2Fuploads%2FGYcwGvnxYLiocMFWLeQq%2Ftranslate-wallet-prefix.png?alt=media\&token=15f8b039-c38e-4a19-8795-0dcefa7a76ea)


---

# 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.v2.like.co/zh/general-guides/community/translate-wallet-prefix.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.
