-
Notifications
You must be signed in to change notification settings - Fork 700
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
Bridge: added free headers submission support to the substrate-relay #4157
Conversation
…of_ex + check it from the transaction extension
… to RefundBridgedGrandpaMessages
… messages transactions
…ty (this is not used yet - see next commit)
…ge GRANDPA transactions are obsolete and, if not, it may apply priority boost to
…coming from CheckAndBoostBridgeGrandpaTransactions
…de of tx body, it is `None` and otherwise it is `Some`
…`improved_by` from extension code
…g in HeadersToRelay::Free mode
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.
also needs prdoc
- breaking/major change for a number of crates
@acatangiu I've added prdoc, but there's no "audience" that is suitable for us. Most suitable in this case is "Node Dev", but I guess everyone who's watching bridge can get all updates from |
// if we see that the header schedules GRANDPA change, we need to submit it | ||
if self.sync_params.only_mandatory_headers { | ||
if self.sync_params.headers_to_relay == HeadersToRelay::Mandatory { |
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 about allowing here also HeadersToRelay::All
?
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.
Sorry, I don't get what you mean. Can you, please, elaborate? All
and Free
are handled later, in the selector.select
call.
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.
nvm, I need to walk through the entire PR first :)
…4157) Original PR: paritytech/parity-bridges-common#2884. Since chain-specific code lives in the `parity-bridges-common` repo, some parts of original PR will require another PR --------- Co-authored-by: Adrian Catangiu <adrian@parity.io>
…aritytech#4157) Original PR: paritytech/parity-bridges-common#2884. Since chain-specific code lives in the `parity-bridges-common` repo, some parts of original PR will require another PR --------- Co-authored-by: Adrian Catangiu <adrian@parity.io>
Original PR: paritytech/parity-bridges-common#2884. Since chain-specific code lives in the
parity-bridges-common
repo, some parts of original PR will require another PR