> 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/validator/previous-upgrades/fotan-upgrade-mainnet/software-changes-overview.md). # Software Changes Overview {% hint style="warning" %} The documentation is designed for Liker Land and LikeCoin v2. For information on [3ook.com](https://3ook.com/) and LikeCoin v3, please visit [docs.3ook.com](https://docs.3ook.com) and [dao.like.co](https://dao.like.co/). {% endhint %} ### liked & likecli * `liked` and `likecli` commands are combined into one single command (`liked`). * Key storage format changed, storage is moved into `.liked`, any access (including listing keys) would require user to provide the key vault password . * Multiple keyring backends are supported from `--keyring-backend` parameter, however when using Docker, only traditional file storage will be supported. You may compile standalone `liked` executable for other backends if needed. * As `likecli` is gone, lite client does not have a standalone process anymore. API server would need to be manually enabled in `app.toml` from the chain node. ### Transactions & Queries * Balance is moved into the `bank` module, so you may need to run`liked query bank balances` instead of `likecli query account`. * Many old APIs are deprecated. See for details. ### Docker setup * In SheungWan, we used separate Docker images for root and non-root. Turns out it is not necessary, as Docker and Docker-Compose can specify the runtime user. So in FoTan the images are unified, and `LIKECOIN_UID` is introduced in `.env`. * Variables (`seed nodes`, `users`) are specified in the `.env` file. * Commands are now run by `docker-compose run` , so configs in `docker-compose.yml` (e.g. `volumes`, `users`) could be reused. no need to re-type every time. ### Scripts * Scripts are rewritten and combined with Docker Compose profiles (We now require Docker Compose ≥1.28). --- # 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.v2.like.co/validator/previous-upgrades/fotan-upgrade-mainnet/software-changes-overview.md?ask=&goal= ``` `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.