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

inv messages vectors should not be pushed directly #591

Merged
merged 1 commit into from
Aug 31, 2015
Merged

inv messages vectors should not be pushed directly #591

merged 1 commit into from
Aug 31, 2015

Conversation

UdjinM6
Copy link

@UdjinM6 UdjinM6 commented Aug 31, 2015

On mainnet inv vectors are getting way too large to be pushed in one step and receiving node will fail to accept such messages (and ban us). We should use internal inv functionality instead.

@UdjinM6 UdjinM6 added the bug label Aug 31, 2015
eduffield222 pushed a commit that referenced this pull request Aug 31, 2015
inv messages vectors should not be pushed directly
@eduffield222 eduffield222 merged commit 1b4ef1d into dashpay:v0.12.1.x Aug 31, 2015
@eduffield222
Copy link

Ah, that makes sense. Thanks!

@UdjinM6 UdjinM6 deleted the fix_inv branch March 7, 2016 03:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants