ChainSafe / ChainSafe/gossamer

Support more than one protocol per message type at `RegisterNotificationsProtocol`

Open
#3,846 0 comments 0 reactions 0 assignees View on GitHub
A-design C-complex P-low S-network
Dominant language
Go
Stars
454
Forks
144
PR merge metrics
No merged PRs in 30d

Description

## Issue summary

- Currently, Substrate can register up-to-date protocol id's as well as legacy protocol id's for backward compatibility between older nodes, and in Gossamer our `RegisterNotificationsProtocol` cannot hold more than one protocol id since it is bounded by message type which means that we cannot have an up-to-date and a legacy protocol for the same message type

- I would suggest supporting more than one protocol per message type

## Other information and links
N/A

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.