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
At the moment, we check the contract versions for chains by querying their RPC endpoint, and we the contract version checks return TRUE if gov-approved and FALSE otherwise.
However, we don't actually persist or display the version number. This is a detail that the Growth team would like to add to the upcoming SCR frontend, and though they’ve agreed to drop the requirement for the v0, it would be great to have this available for a future iteration of the SCR frontend.
This may also prove useful when doing things like confirming which chains are actually at Stage 1 (see #332).
At the moment, we check the contract versions for chains by querying their RPC endpoint, and we the contract version checks return TRUE if gov-approved and FALSE otherwise.
However, we don't actually persist or display the version number. This is a detail that the Growth team would like to add to the upcoming SCR frontend, and though they’ve agreed to drop the requirement for the v0, it would be great to have this available for a future iteration of the SCR frontend.
This may also prove useful when doing things like confirming which chains are actually at Stage 1 (see #332).
Example in chainList.json:
Example in a chain config file:
The text was updated successfully, but these errors were encountered: