fix: differentiate chains using the studio from testnet #122
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.
Fixes #dxp-709
What
Added a new isStudio boolean property to the GenLayerChain type to explicitly distinguish between network types:
Updated chain configurations:
localnet: isStudio: true (uses simulator API)
studionet: isStudio: true (uses simulator API)
testnetAsimov: isStudio: false (uses rollup contract)
Fixed in src/transactions/actions.ts:71: Changed condition from client.chain.id === localnet.id to client.chain.isStudio
Why
to fix a bug where clients were calling the consensus smart contracts when using the studio with other ChainiID
Testing done
Decisions made
Changed in src/types/chains.ts: Added isStudio: boolean property to GenLayerChain type
Checks
Summary by CodeRabbit
isStudioflag to chain configurations for consistent studio environment detection across all chain types.