feat: add --network option#425
Merged
Merged
Conversation
commit: |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds
--network mainnet|testnetand checks the challenge chain against the connected RPC before signing.This came up while dogfooding
mppxwith Hermes Agent. The agent hit a testnet MPP ping challenge but was configured with the mainnet RPC, and later hit a mainnetfalchallenge while trying the testnet RPC. In both cases the CLI could still sign/broadcast on the wrong chain, which turned into confusing errors like token initialization failures, payment rejected, or verification failed.Now the CLI fails before signing if the challenge says one chain and the RPC is connected to another.