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

Use chainID from genesis config instead of ownChainAccount #8356

Closed
Tracked by #7210
ishantiw opened this issue Apr 13, 2023 · 0 comments · Fixed by #8358
Closed
Tracked by #7210

Use chainID from genesis config instead of ownChainAccount #8356

ishantiw opened this issue Apr 13, 2023 · 0 comments · Fixed by #8358
Assignees
@ishantiw
Labels
framework-plugins/chain_connector type: bug
Milestone
Sprint 93

Comments

@ishantiw
Copy link
Contributor

Expected behavior

Since sidechain initially can have empty ownChainAccount we should use chainID from the genesisConfig.

Actual behavior

Currently we are getting chainID of the sendingChain by calling ownChainAccount RPC

Steps to reproduce

Start an app with Chain connector plugin

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

v6.0.0-alpha.19
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@ishantiw ishantiw

Labels
framework-plugins/chain_connector type: bug
Projects
None yet
Milestone
Sprint 93
Development

Successfully merging a pull request may close this issue.

Use chainID from genesisConfig and fix ccm selection LiskArchive/lisk-sdk
1 participant
@ishantiw