Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reject Dash-specific messages from obsolete peers #1983

Merged
merged 1 commit into from
Mar 15, 2018

Conversation

UdjinM6
Copy link

@UdjinM6 UdjinM6 commented Mar 12, 2018

Same logic as for MIN_PEER_PROTO_VERSION but using specific proto versions for each submodule. Sends REJECT msg back to the peer we received the original message from.

And send REJECT msg back to the peer we received the original message from.
Same logic as for MIN_PEER_PROTO_VERSION but using specific proto versions for each submodule.
Copy link

@codablock codablock left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

@UdjinM6 UdjinM6 merged commit 08033ff into dashpay:develop Mar 15, 2018
andvgal pushed a commit to energicryptocurrency/gen2-energi that referenced this pull request Jan 6, 2019
And send REJECT msg back to the peer we received the original message from.
Same logic as for MIN_PEER_PROTO_VERSION but using specific proto versions for each submodule.
CryptoCentric pushed a commit to absolute-community/absolute that referenced this pull request Feb 28, 2019
And send REJECT msg back to the peer we received the original message from.
Same logic as for MIN_PEER_PROTO_VERSION but using specific proto versions for each submodule.
@UdjinM6 UdjinM6 deleted the rejects branch November 26, 2020 11:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants