-
**Describe the bug**
When trying to initialise the `SignClient` on Android Emulator, I'm getting the following errors:
```
WARN `new NativeEventEmitter()` was called with a non-null argument with…
-
### Description
SidechainCrossChainUpdate execute method's [ccmContext](https://github.com/LiskHQ/lisk-sdk/blob/89e7504ef5eb6183aefe576a93be3d6052e56038/framework/src/modules/interoperability/sidec…
-
### Expected behavior
When loading the plugins in the child process, the application should start normally.
### Actual behavior
When loading the plugins in the child process, the application …
-
### Expected behavior
A log file is created under `~/.lisk/lisk-core/logs/`
The config is set to info by default so a log file should exist...
### Actual behavior
No log file found, anywhe…
-
### Expected behavior
Input to the validators method and endpoint should be validated although in the mainchain protocol, it is indirectly validated in the commands which calls the methods.
### Ac…
-
### Expected behavior
All the params must be validated against the schema at some point.
Consider moving the schema validation into state machine where the params is decoded
### Actual behavior
…
-
### Description
// framework/src/modules/interoperability/mainchain/commands/submit_mainchain_cross_chain_update.ts
```
private _verifyLivenessConditionForRegisteredChains(
context: CommandVeri…
-
### Description
Due to a lack of validation, the `InitializeMessageRecoveryCommand` can receive the params.channel parameter as an empty string. An empty string on the value field of a query, makes…
-
### Description
The `RegisterMainchainCommand` class of the interoperability module uses the `mainchainRegParams` schema to validate several parameters, including a `signature` field, which is of t…
-
### Expected behavior
When a plugin is loaded as childProcess it should be able to expose the registered endpoints.
### Actual behavior
When a plugin is loaded as childProcess it is not able …