From 7adb4cf30761a13d7bd4d10ad7cc6176a5102791 Mon Sep 17 00:00:00 2001 From: serinko <97586125+serinko@users.noreply.github.com> Date: Mon, 23 Dec 2024 12:39:59 +0100 Subject: [PATCH] edit migration page --- .../snippets/gateway-migrate-tab-snippet.mdx | 3 ++- .../outputs/api-scraping-outputs/time-now.md | 2 +- documentation/docs/next-env.d.ts | 2 +- .../docs/pages/operators/nodes/nym-node/setup.mdx | 11 ++++++++--- 4 files changed, 12 insertions(+), 6 deletions(-) diff --git a/documentation/docs/components/operators/snippets/gateway-migrate-tab-snippet.mdx b/documentation/docs/components/operators/snippets/gateway-migrate-tab-snippet.mdx index 101dbca21cc..72dce528ca2 100644 --- a/documentation/docs/components/operators/snippets/gateway-migrate-tab-snippet.mdx +++ b/documentation/docs/components/operators/snippets/gateway-migrate-tab-snippet.mdx @@ -5,7 +5,7 @@ Migrate your `nym-gateway` to `nym-node --mode entry-gateway` or `--mode exit-ga ###### 1. Move relevant info from `config.toml` ```sh -./nym-node migrate --config-file ~/.nym/gateways//config/config.toml gateway +./nym-node migrate --config-file ~/.nym/gateways//config/config.toml gateway ``` ###### 2. Initialise with new `nym-node` config chosing one of the options below: @@ -19,5 +19,6 @@ Migrate your `nym-gateway` to `nym-node --mode entry-gateway` or `--mode exit-ga ```sh ./nym-node run --id --mode exit-gateway --public-ips "$(curl -4 https://ifconfig.me)" --hostname --http-bind-address 0.0.0.0:8080 --mixnet-bind-address 0.0.0.0:1789 --location --accept-operator-terms-and-conditions --wireguard-enabled true ``` + diff --git a/documentation/docs/components/outputs/api-scraping-outputs/time-now.md b/documentation/docs/components/outputs/api-scraping-outputs/time-now.md index 6fd75a4e876..f6b75163808 100644 --- a/documentation/docs/components/outputs/api-scraping-outputs/time-now.md +++ b/documentation/docs/components/outputs/api-scraping-outputs/time-now.md @@ -1 +1 @@ -Wednesday, December 18th 2024, 17:36:44 UTC +Monday, December 23rd 2024, 11:36:26 UTC diff --git a/documentation/docs/next-env.d.ts b/documentation/docs/next-env.d.ts index 4f11a03dc6c..a4a7b3f5cfa 100644 --- a/documentation/docs/next-env.d.ts +++ b/documentation/docs/next-env.d.ts @@ -2,4 +2,4 @@ /// // NOTE: This file should not be edited -// see https://nextjs.org/docs/basic-features/typescript for more information. +// see https://nextjs.org/docs/pages/building-your-application/configuring/typescript for more information. diff --git a/documentation/docs/pages/operators/nodes/nym-node/setup.mdx b/documentation/docs/pages/operators/nodes/nym-node/setup.mdx index 33e7e3f6c34..8654616321e 100644 --- a/documentation/docs/pages/operators/nodes/nym-node/setup.mdx +++ b/documentation/docs/pages/operators/nodes/nym-node/setup.mdx @@ -168,19 +168,24 @@ In such case, you can `run` a node to initalise it or try if everything works, b ### Migrate -Migration is a must for all deprecated nodes (`nym-mixnode`, `nym-gateway`). These binaries from version 1.1.35 (`nym-gateway`) and 1.1.37 (`nym-mixnode`) onwards will no longer have `init` command and `nym-node` is the only binary to use for `gateway` or `mixnode` fucntionalities. +**Legacy binaries `nym-mixnode` and `nym-gateway` had been deprecated, [`nym-node`](../nym-node.mdx) is the only binary to use for `gateway` or `mixnode` functionalities!** -**Nym cannot promise 100% serialisation for operators migrating from long outdated versions to the newest ones. If you are about to migrate, start with [`nym-node v1.1.0`](https://github.com/nymtech/nym/releases/tag/nym-binaries-v2024.3-eclipse) and keep upgrading version by version all the way to the latest one.** +From `2024.14-crunch` release (`nym-node v1.2.0`) onward, `nym-node` binary does *not* have `migrate` command included. In case you are still running a legacy node and want to migrate, [download](https://github.com/nymtech/nym/releases) an older `nym-node` binary and upgrade to the latest after migrating. + +Furthermore, giving that legacy nodes had been deprecated for several months, Nym cannot promise 100% serialisation for operators migrating from long outdated versions. If you are about to migrate, start with [`nym-node v1.1.0`](https://github.com/nymtech/nym/releases/tag/nym-binaries-v2024.3-eclipse) and keep upgrading version by version all the way to the latest one. Operators who are about to migrate their nodes need to configure their [VPS](vps-setup.md) and setup `nym-node` which can be downloaded as a [pre-built binary](../binaries/pre-built-binaries.md) or compiled from [source](../binaries/building-nym.md). -To migrate a `nym-mixnode` or a `nym-gateway` to `nym-node` is fairly simple, use the `migrate` command with `--config-file` flag pointing to the original `config.toml` file, with a conditional argument defining which type of node this configuration belongs to. Examples are below. +To migrate a `nym-mixnode` or a `nym-gateway` to `nym-node` use, the `migrate` command with `--config-file` flag pointing to the original `config.toml` file, with a conditional argument defining which type of node this configuration belongs to. The exact steps are below. Make sure to use `--deny-init` flag to prevent initialisation of a new node. +**After you upgraded your node to the latest release of `nym-node`, make sure that you also follow [the steps to migrate your node in the Mixnet smart contract](bonding#migrate-to-nym-node-in-mixnet-smart-contract), othewise your node will never receive any rewards.** + + ### Next steps If there are any problems checkout the troubleshooting section or report an issue.