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
Bridge relayers read storage from multiple chains (AHs, BHs, Relays, Ethereum, etc), and use storage proofs to submit to other chains.
To guarantee compatibility, we currently use runtime version guards to make sure relayers don't operate on newer runtimes (newer than the ones they were compiled agains).
The problem with this approach is that relayer operators need to update and redeploy the relayer stack for each chain runtime upgrade, and because runtime upgrades are asynchronous, this operational overhead is significant.
This issue is to track a solution for minimizing this operational overhead. One idea to do so is to develop smarter relayers that can run compatibility checks for "newer" runtimes, and only request manual update+redeployment when they do detect some compatibility problem.
Description
Bridge relayers read storage from multiple chains (AHs, BHs, Relays, Ethereum, etc), and use storage proofs to submit to other chains.
To guarantee compatibility, we currently use runtime version guards to make sure relayers don't operate on newer runtimes (newer than the ones they were compiled agains).
The problem with this approach is that relayer operators need to update and redeploy the relayer stack for each chain runtime upgrade, and because runtime upgrades are asynchronous, this operational overhead is significant.
This issue is to track a solution for minimizing this operational overhead. One idea to do so is to develop smarter relayers that can run compatibility checks for "newer" runtimes, and only request manual update+redeployment when they do detect some compatibility problem.
The text was updated successfully, but these errors were encountered: