Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Fix isChainIDAvailable to also check for the mainchain id #8190

Closed
Tracked by #7210
ishantiw opened this issue Feb 24, 2023 · 0 comments · Fixed by #8302
Closed
Tracked by #7210

Fix isChainIDAvailable to also check for the mainchain id #8190

ishantiw opened this issue Feb 24, 2023 · 0 comments · Fixed by #8302
Assignees
Milestone

Comments

@ishantiw
Copy link
Contributor

ishantiw commented Feb 24, 2023

Expected behavior

  • isChainIDAvailable should return false for mainchainID
  • isChainIDAvailable should only be available on mainchain
  • It should also check for the networkByte(first byte of the chainID) of the chainID, if not the correct networkByte then return false

Actual behavior

  • isChainIDAvailable can return true on sidechain for the mainchain

Steps to reproduce

  • Run a sidechain node where mainchain is not registered and query isChainIDAvailable endpoint

Which version(s) does this affect? (Environment, OS, etc...)

v6.0.0-alpha.14

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants