-
Notifications
You must be signed in to change notification settings - Fork 129
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
Remove message fee + message send calls #1642
Conversation
messages_relayers, | ||
received_range, | ||
); | ||
|
||
register_relayers_rewards::<T>( | ||
confirmation_relayer, | ||
relayers_rewards, | ||
GetConfirmationFee::get(), | ||
// TODO (https://github.com/paritytech/parity-bridges-common/issues/1318): this shall be fixed |
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.
Shall be fixed either in this PR, or 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.
Left it for later. New relayer rewards scheme will be introduced later && it deserves a separate review
Need to test it locally => back to draft |
|
||
// there's no way to craft XCM of the given size - we'll be using `ExpectPallet` | ||
// instruction, which has byte vector inside | ||
let mut current_vec_size = expected_xcm_size; |
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.
That's the only new code in this PR - since we are now only sending messages using XCM pallet, then the message shall be valid xcm and vec[42; 1024]
won't work here.
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.
@svyatonik
wow, lots of code removed,
very nice, it will also remove lots of my "0/None TODOs" from bridge-hubs :)
* [WIP][ci] Disable auto-fmt and revert cancel-pipeline * fail test-linux-stable * fix test-linux-stable
* remove message fee * it is compiling! * fixes + fmt * more cleanup * more cleanup * restore MessageDeliveryAndDispatchPayment since we'll need relayer rewards * started rational relayer removal * more removal * removed estimate fee subcommand * remove DispatchFeePayment * more removals * removed conversion rates && some metrics * - unneeded associated type * - OutboundMessageFee * fix benchmarks compilation * fmt * test + fix benchmarks * fix send message * clippy
* remove message fee * it is compiling! * fixes + fmt * more cleanup * more cleanup * restore MessageDeliveryAndDispatchPayment since we'll need relayer rewards * started rational relayer removal * more removal * removed estimate fee subcommand * remove DispatchFeePayment * more removals * removed conversion rates && some metrics * - unneeded associated type * - OutboundMessageFee * fix benchmarks compilation * fmt * test + fix benchmarks * fix send message * clippy
resolves some parts of #1638
very wip => draft
Splitting it into separate issues turned out to be hard - removed parts are tightly tied together, so single PR. I'll explicitly add comments where I'd like to have an approval.
UPD: this PR is not touching everything that is related to relayer rewards
UPD2: what this PR removes:
send_message
andincrease_message_fee
calls of the messages pallet + their corresponding benchmarks;estimate-fee
subcommand of relayer