You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
Genesis block should be created based on lisk-core instance
Actual behavior
Currently, genesis block is created based on default application instance. This results in the error when starting node with migrated genesis block:
2023-08-29T08:05:34.629Z INFO Himanshus-MBP.fritz.box application 85680 Registered legacy module has command registerKeys
2023-08-29T08:05:34.646Z INFO Himanshus-MBP.fritz.box application 85680 [stateRoot=c87b4dca0c82e31455f28984322c189b33c19216ccae19be5f6a5c90a7201682 height=20171933] Start caching genesis state
Error: Invalid state root `Not matching with expected`
2023-08-29T08:05:37.445Z INFO Himanshus-MBP.fritz.box application 85680 [errorCode=2 message=process.exit] Application shutdown started
Steps to reproduce
Create genesis block using migrator (testnet or mainnet)
Expected behavior
Genesis block should be created based on
lisk-core
instanceActual behavior
Currently, genesis block is created based on default application instance. This results in the error when starting node with migrated genesis block:
Steps to reproduce
testnet
ormainnet
)Which version(s) does this affect? (Environment, OS, etc...)
v2.0.0-beta.2
The text was updated successfully, but these errors were encountered: