Different MIN_PEER_PROTO_VERSION for Hush and DragonX #345

Open
opened 6 months ago by duke · 3 comments
duke commented 6 months ago
Owner

In the future we will want DragonX and Hush to be able to set different minimum protocol versions which will talk to other nodes, since 3.10.0 is a mandatory update for Hush but optional for DragonX.

This does not need to be done for the 3.10.0 release but will be needed in the next release after that.

In the future we will want DragonX and Hush to be able to set different minimum protocol versions which will talk to other nodes, since 3.10.0 is a mandatory update for Hush but optional for DragonX. This does not need to be done for the 3.10.0 release but will be needed in the next release after that.
duke added the
feature
label 6 months ago
Poster
Owner

After this is done we will also want to update the release process docs to mention there are different minimum peer protocol versions for Hush and Dragonx

After this is done we will also want to update the release process docs to mention there are different minimum peer protocol versions for Hush and Dragonx
duke self-assigned this 3 months ago
Poster
Owner

Looks like this is becoming more important, because Hush 3.10.0 nodes should not attempt to talk to older nodes which are not consensus compatible, but DragonX nodes have never had a consensus change, so they can.

Looks like this is becoming more important, because Hush 3.10.0 nodes should not attempt to talk to older nodes which are not consensus compatible, but DragonX nodes have never had a consensus change, so they can.
Poster
Owner

We need some testing for this code, which is on the dev branch, for both Hush and DragonX

We need some testing for this code, which is on the `dev` branch, for both Hush and DragonX
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.