Is your feature request related to a problem?

The Notifier module is responsible for handling topology changes and ensuring data replication across the correct storage nodes. Currently, it compares the set of prev_available_nodes, new_available_nodes, and unavailable_nodes to determine how the topology should change. However, this logic is outdated, as the Notifier no longer needs to explicitly consider unavailable_nodes.

Additionally, the Notifier does not handle scenarios where a node’s GeoPatch changes. A GeoPatch update impacts the election of storage nodes and validation nodes, requiring the network to reorganize data responsibilities. Without support for GeoPatch updates, storage elections and data distribution may become inconsistent.

Describe the solution you’d like

We need to refactor the Notifier module with the following changes:

1. Refactor Notifier Logic: Removing the dependency on unavailable_nodes in election and topology change calculations. Focusing exclusively on prev_available_nodes and new_available_nodes to simplify the logic and reflect current system needs.

2. Enhancing GeoPatch Handling to update the P2P context: by using the Notifier to systematically update storage nodes’ responsibilities and trigger data replication for impacted transactions whenever a node transaction with GeoPatch update is validated.

Additional context

Epic