feat: Add Avalanche Local chain support and fix HRP for local networks #316
+35
−27
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.
Summary
avalancheLocalchain definition for local/tmpnet developmentsignXPTransactionto query the actual network ID from the node instead of relying onchain.testnetflagLOCAL_NETWORK_IDconstant from 1337 to 12345 to match avalanchejs and tmpnetProblem
When using the SDK with local networks (tmpnet), transactions failed with:
The root cause was:
signXPTransactioncheckedclient.chain?.testnetand if true, assumed network ID 5 (Fuji)isTestnet ? "fuji" : "avax"for HRP, never supporting "local"Solution
getContextFromURI()getHRP(networkId)which properly maps network IDs to HRP strings including "local" for 12345LOCAL_NETWORK_IDconstant to 12345 for consistency with avalanchejsTest plan