You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: