forked from bitcoin/bitcoin
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
feat: broadcast dsq messages using the inventory system #6148
Merged
PastaPastaPasta
merged 1 commit into
dashpay:develop
from
PastaPastaPasta:feat/send-dsq-over-inv
Sep 10, 2024
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
P2P and Network Changes | ||
----------------------- | ||
|
||
The DSQ message, starting in protocol version 70234, is broadcast using the inventory system, and not simply | ||
relaying to all connected peers. This should reduce the bandwidth needs for all nodes, however, this affect will | ||
be most noticeable on highly connected masternodes. (#6148) |
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -87,10 +87,11 @@ EXPECTED_CIRCULAR_DEPENDENCIES=( | |
"evo/deterministicmns -> validationinterface -> evo/deterministicmns" | ||
"logging -> util/system -> sync -> logging/timer -> logging" | ||
|
||
"coinjoin/client -> net_processing -> coinjoin/client" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. can you avoid adding new circulat dependencies? These 2 disappeared just because they have shorter path between coinjoin/client.... coinjoin/client
|
||
"coinjoin/client -> net_processing -> coinjoin/context -> coinjoin/client" | ||
"coinjoin/context -> coinjoin/server -> net_processing -> coinjoin/context" | ||
"coinjoin/server -> net_processing -> coinjoin/server" | ||
"llmq/context -> llmq/ehf_signals -> net_processing -> llmq/context" | ||
"coinjoin/client -> coinjoin/util -> wallet/wallet -> psbt -> node/transaction -> node/context -> coinjoin/context -> coinjoin/client" | ||
"llmq/blockprocessor -> net_processing -> llmq/blockprocessor" | ||
"llmq/chainlocks -> net_processing -> llmq/chainlocks" | ||
"llmq/dkgsession -> net_processing -> llmq/quorums -> llmq/dkgsession" | ||
|
@@ -100,7 +101,6 @@ EXPECTED_CIRCULAR_DEPENDENCIES=( | |
"llmq/blockprocessor -> net_processing -> llmq/context -> llmq/blockprocessor" | ||
"llmq/blockprocessor -> net_processing -> llmq/quorums -> llmq/blockprocessor" | ||
"llmq/chainlocks -> net_processing -> llmq/context -> llmq/chainlocks" | ||
"coinjoin/client -> coinjoin/coinjoin -> llmq/chainlocks -> net_processing -> coinjoin/client" | ||
"rpc/blockchain -> rpc/server -> rpc/blockchain" | ||
) | ||
|
||
|
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What if by any reason
CCoinJoinClientQueueManager
will be initialized beforepeerman
?Should we just change assert here to if?