peer, main: allow for queuing multiple invvects #91
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For utreexo tx inv messages, the invvects will be related to each other as the invvect for the tx will be matched with the position invs. It'll look like so: [InvTypeUtreexoTx][TXID1] [InvTypeProofHash][packed positions1.1] (4 positions) [InvTypeProofHash][packed positions1.2] (1 position) At the moment the invvects can only be queued one at a time which may result in the InvTypeProofHash to be separated from the InvTypeUtreexoTx. Allowing for queuing multiple invvects eliminates this problem.
kcalvinalvin
force-pushed
the
2023-12-19-add-ability-to-queue-multiple-invs
branch
from
0e1b6d9 to
4480a0e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For utreexo tx inv messages, the invvects will be related to each other as the invvect for the tx will be matched with the position invs. It'll look like so:
[InvTypeUtreexoTx][TXID1]
[InvTypeProofHash][packed positions1.1] (4 positions) [InvTypeProofHash][packed positions1.2] (1 position)
At the moment the invvects can only be queued one at a time which may result in the InvTypeProofHash to be separated from the InvTypeUtreexoTx. Allowing for queuing multiple invvects eliminates this problem.