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

Shall the message fee include cost of parachain finality transaction? #1620

Closed
svyatonik opened this issue Nov 2, 2022 · 1 comment
Closed
Labels
A-chores Something that has to be done, as part of regular maintenance P-Message Delivery

Comments

@svyatonik
Copy link
Contributor

When we are delivering messages between two relay (or standalone) chains, then we only deal with GRANDPA finality. GRANDPA finality transactions have some cost. To cover these costs, we have two things:

  1. some GRANDPA finality transactions are free - when they're delivering mandatory headers;
  2. there's some additional relayer interest in the message fee, which may (at least partially) cover this cost.

Initial plan for Kusama<>Polkadot relay<>relay bridge was to run only-mandatory-headers finality relay. It means delivery lags, but the cost of running this bridge is zero.

Now we're dealing with parachain <> parachain bridge. It requires additional parachain finality transaction in the pipeline. Shall we add this cost to the message fee? Shall we just increase relayer interest? Shall we make some parachain finality transactions free (Pays::No) - e.g. there's one free transaction every 1024 relay blocks?

We shall think about that after #1318

@svyatonik svyatonik added A-chores Something that has to be done, as part of regular maintenance P-Message Delivery labels Nov 2, 2022
@svyatonik
Copy link
Contributor Author

The final fee idea is that it'll be taken at the source parachain (i.e. not at the bridge hub). We only charge relayers for bridge-hub transactions and then reward them from source/target parachains sovereign accounts on bridge hubs. So we don't have any fee calculations on bridge hubs => this issue is not relevant anymore

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-chores Something that has to be done, as part of regular maintenance P-Message Delivery
Projects
None yet
Development

No branches or pull requests

1 participant