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

Reevaluate balance guard values for Polkadot <> Kusama #1300

Closed
svyatonik opened this issue Jan 31, 2022 · 0 comments · Fixed by #1308
Closed

Reevaluate balance guard values for Polkadot <> Kusama #1300

svyatonik opened this issue Jan 31, 2022 · 0 comments · Fixed by #1308
Assignees
Labels

Comments

@svyatonik
Copy link
Contributor

We'll be running headers-and-messages bridge in planned P<>K deployment. It means that the relayer account will be submitting both finality (free if only mandatory headers are used) and messages transactions (never free). Current balance guard values (here and here) are made for separate finality relays even prior to making mandatory headers finality submission free-of-charge.

The idea is to simply set it some larger (significant) value instead. Ideally, we shall provide this value through CLI, but it may be done later.

@svyatonik svyatonik added this to the Kusama <> Polkadot Release milestone Jan 31, 2022
@svyatonik svyatonik self-assigned this Jan 31, 2022
svyatonik pushed a commit that referenced this issue Jul 17, 2023
* Fixup after dir re-org

* Update scripts/benchmarks-ci.sh

Co-authored-by: Chevdor <chevdor@users.noreply.github.com>

* Update scripts/benchmarks-ci.sh

Co-authored-by: Chevdor <chevdor@users.noreply.github.com>

* Update scripts/benchmarks-ci.sh

Co-authored-by: Chevdor <chevdor@users.noreply.github.com>

* fix typo

Co-authored-by: Chevdor <chevdor@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant