Skip to content

Commit

Permalink
new attempt
Browse files Browse the repository at this point in the history
  • Loading branch information
gabrielmer committed Aug 29, 2024
1 parent f5a22d0 commit 16647b0
Showing 1 changed file with 7 additions and 5 deletions.
12 changes: 7 additions & 5 deletions docs/guides/nwaku/upgrade-instructions.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,10 +11,12 @@ import { AccordionItem } from '@site/src/components/mdx'
<AccordionItem title="v0.31.0">
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/<CLUSTER_ID>/<SHARD_ID>
```
/waku/2/rs/<CLUSTER_ID>/<SHARD_ID>
```

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.
</AccordionItem>

0 comments on commit 16647b0

Please sign in to comment.