This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
Update genesis asset schema for interoperability #8151
Comments
This was referenced Mar 6, 2023
ishantiw
added a commit
that referenced
this issue
Mar 24, 2023
…ccounts and terminatedOutboxAccounts (#8238) ### What was the problem? This PR resolves #8151 (ONLY mainchain) Sidechain PR: #8256 ### How was it solved? Verification checks applied per [LIP](https://github.com/LiskHQ/lips/blob/main/proposals/lip-0045.md#mainchain) Relevant PR: #8239 **Note:** - To reduce size of PR, this task is split into multiple PRs - This PR only covers mainchain part ### How was it tested? - Test cases added to `module.spec.ts` - To check/verify schema at example path: - cd lisk-sdk/examples/pos-mainchain - ./bin/run genesis-block:create --output=config/default --assets-file=./config/default/genesis_assets.json - To run example app - ./bin/run start --api-ipc --api-http --port 9001 - if it fails with `Error: Genesis block does not match.`, run `rm -rf ~/.lisk/pos-mainchain` (**Note:**, it's not `rm -rf ~/.lisk/dpos-mainchain`)
ishantiw
added a commit
that referenced
this issue
Mar 24, 2023
…unts and terminatedOutboxAccounts (#8239) ### What was the problem? This PR resolves #8151 (ONLY mainchain) Relevant PR: #8238 ### How was it solved? Verification checks applied per [LIP](https://github.com/LiskHQ/lips/blob/main/proposals/lip-0045.md#mainchain) ### How was it tested? Test cases added to `module.spec.ts`
This was referenced Mar 26, 2023
|
Reopening the issue as still #8317 needs to be merged |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Update
genesisInteroperabilityStoreSchemabased on LIP PR so that genesis-assets are consistent with genesis-assets of other modules.Another update
If "ownChainName" is not the empty string and "ownChainNonce != 0"LIP PRReference for genesisInteroperabilityStoreSchema:
LIP0045:genesisInteroperabilityStoreSchemaAcceptance Criteria
The text was updated successfully, but these errors were encountered: