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
Currently to illustrate how to verify your finality provider has successfully been created we instruct them to go to the Babylon chain with the TX hash to verify. This isn't the best way as we are instructing them to leave the current setup. We want a native way of verifying.
The text was updated successfully, but these errors were encountered:
closes: #172
Previously In the docs we asked the operators to look at the bbn chain
to verify the hash. I added this instruction so they can see their
status, which is what we ultimately wanted them to check with the
verification of the hash
Summary
Currently to illustrate how to verify your finality provider has successfully been created we instruct them to go to the Babylon chain with the TX hash to verify. This isn't the best way as we are instructing them to leave the current setup. We want a native way of verifying.
The text was updated successfully, but these errors were encountered: