feat: bitcoin network rpc property #591
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
daniel-savu
force-pushed
the
feature/btc-rpc-prop
branch
from
794fe25
to
3e87349
Compare
gregdhill
approved these changes
May 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Specifying the Bitcoin Network in chainspec properties is useful when troubleshooting interbtc-clients connection errors. In case of a mismatch between the expectation on the client side and that in the chain runtime, a suggestive error can be printed (e.g. "Error: You are trying to connect a Vault compiled with testnet metadata (used on Bitcoin testnet) to a parachain that is using Bitcoin mainnet").