From 4515b52310ec9d50f8cc8c9cb3a372bd7d14eedd Mon Sep 17 00:00:00 2001 From: Gabriel mermelstein Date: Thu, 29 Aug 2024 15:00:02 -0600 Subject: [PATCH] new attempt --- docs/guides/nwaku/upgrade-instructions.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/docs/guides/nwaku/upgrade-instructions.md b/docs/guides/nwaku/upgrade-instructions.md index c5f178b..ab6dc3c 100644 --- a/docs/guides/nwaku/upgrade-instructions.md +++ b/docs/guides/nwaku/upgrade-instructions.md @@ -11,10 +11,12 @@ import { AccordionItem } from '@site/src/components/mdx' Named sharding was deprecated in this version. This means that pubsub topics will only be supported if they comply with the static sharding format: - /waku/2/rs// +``` +/waku/2/rs// +``` - In order to migrate your existing application, you need to: - 1. Make sure that your clients are sending messages to pubsub topics in the required format - 2. When running a node with the `--pubsub-topic` CLI flag, the values provided should compy with the static sharding format - 3. If your application relies on nodes or clients that may not be updated immediately, keep your node on an older version while subscribing to both the currently pubsub topic and the new pubsub topic that will comply with the static sharding format. In that case, you can keep backward compatibility for a migration period. +In order to migrate your existing application, you need to: +1. Make sure that your clients are sending messages to pubsub topics in the required format +2. When running a node with the `--pubsub-topic` CLI flag, the values provided should compy with the static sharding format +3. If your application relies on nodes or clients that may not be updated immediately, keep your node on an older version while subscribing to both the currently pubsub topic and the new pubsub topic that will comply with the static sharding format. In that case, you can keep backward compatibility for a migration period. \ No newline at end of file