> 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/faq-1.md).

# Miscellaneous

{% 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 %}

## Halt time and sheungwan-2

The mainnet currently is using Cosmos SDK v0.37.4, which unfortunately doesn't support the `halt-time` option. Therefore, before upgrading to `fotan-1` software, validators need to upgrade the image of their node to the `sheungwan-2` software (`likecoin/likecoin-chain:sheungwan-2` in Docker Hub). The `sheungwan-2` software is compatible with the current network, so no proposal or upgrade process is needed.

## Performing machine changes during upgrade

Some validators may want to perform machine changes (e.g. moving to a higher class machine) during the chain upgrade. After stopping the node software, they may move the whole `.liked` and `.likecli` folder to the new machine, and see if they can catch up the upgrade process. If not, then they may simply setup a new node using the new software and new genesis state produced during the upgrade process (see [For other full node operators](/validator/previous-upgrades/fotan-upgrade-mainnet/for-other-full-node-operators.md)).

## Managing incidents during upgrade

During the testnet upgrade, we encountered a problem on software bug, resulting in panic when initializing the chain (see [the recording on the public testnet upgrade](https://www.youtube.com/watch?v=RCt8zkwT_Z4) for details). Our blockchain developer debugged and provided a genesis file mitigating the problem. However, as validator Rick Mak (from Oursky) pointed out, a more decentralized way should be providing procedures for validators to generate the fixed genesis file from the problematic one, instead of providing the genesis file directly. Also, such mitigation may not be suitable for the upgrade, as it is untested and may result in other unexpected and more serious bugs (e.g. state corruption). Therefore, in the mainnet upgrade, if we met incidents like this, we would prefer halting the upgrade and restarting the old chain instead of live fixing it.

## Keystore

The new software moved the keystore to the `liked` command, and provided new option for using the OS keystore instead of in file. If you are operating on Linux, then it may not be an issue as the OS keystore is not supported on Linux, so the software will simply fallback to file keystore. However, some validators using Ledger may operate their key on local machine, and for macOS users, the default keystore is the one from the OS. Therefore when migrating the key onto Linux server, users may find that they are not able to find the key from the `.liked` folder. In this case, the `--keyring-backend file` option may help.


---

# 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/faq-1.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.