> 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/for-other-full-node-operators.md).

# For other full node operators

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

For non-validator nodes, or for validator nodes who cannot join the upgrade process, you may setup a [full node](/validator/likecoin-chain-node/setup-a-node.md) or replace your current full node after the upgrade is finished.

1. Clone the software if you haven't already have one:

   ```
   git clone https://github.com/likecoin/likecoin-chain
   ```
2. Switch to the `fotan-1` branch:

   ```
   git checkout fotan-1
   ```
3. Backup `docker-compose.yml` if you have one:

   ```
   cp docker-compose.yml docker-compose.yml.sheungwan
   ```
4. Setup `docker-compose.yml` and `.env` file:

   ```
   cp docker-compose.yml.template docker-compose.yml
   cp .env.template .env
   ```
5. Get the genesis URL, which will be generated (uploaded) during the upgrade process by validators.
6. Setup `.env` file according to the chain parameter:
   * `LIKECOIN_DOCKER_IMAGE`: `"likecoin/likecoin-chain:fotan-1"`
   * `LIKECOIN_CHAIN_ID`: `"likecoin-mainnet-2"`
   * `LIKECOIN_UID`: normally keep it as `"1000"` is fine, but if you are using root user under Linux (e.g. in some VPS) then you should change it to `"0"`.
   * `LIKECOIN_MONIKER`: the original moniker (in `.liked/config/config.toml`, search for `moniker`). If not sure, any name indicating your node is OK.
   * `LIKECOIN_GENESIS_URL`: `https://gist.githubusercontent.com/williamchong/de1bdf2b2a8f3bce50a4b5e46af26959/raw/4e21bff586771c849d22e1916bcb88c6463fbaa0/genesis.json`
   * `LIKECOIN_SEED_NODES`: `913bd0f4bea4ef512ffba39ab90eae84c1420862@34.82.131.35:26656,e44a2165ac573f84151671b092aa4936ac305e2a@nnkken.dev:26656`
7. Backup the original node if you have one:

   ```
   mv .liked .liked.bak
   ```
8. Initialize the node with new software:

   ```
   docker-compose run --rm init
   ```
9. Re-import the keys and address books from the old node if you have one:

   ```
   cp \
     .liked.bak/config/node_key.json \
     .liked.bak/config/priv_validator_key.json \
     .liked.bak/config/addrbook.json \
     .liked/config
   ```
10. Start up the node:

    ```
    docker-compose up -d
    ```
11. Wait for synchronization, which you may check by going to <http://localhost:26657/status> and see `result.sync_info.catching_up` . If it shows `false` then the node has caught up.
12. If you have keystore, you may migrate the keys by running the following command:

    ```
    docker-compose run liked-command keys migrate /host/.likecli
    ```


---

# 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/validator/previous-upgrades/fotan-upgrade-mainnet/for-other-full-node-operators.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.