-
### Expected behavior
Upgrading an instance name `primary` does not affect the `backup` instance.
### Actual behavior
`~/.lisk/instances/backup/` gets removed by `core:upgrade primary`
###…
-
### Expected behavior
I expect to get the correct list of delegates when calling `Dpos.getRoundDelegates` after a new round is reverted and previous round changes the delegate list.
### Actual beh…
-
### Expected behavior
Blocks/Utils must be pure utility functions without have any dependency on any other module.
### Actual behavior
Currently the `block/utils.js` is requiring `block.js` which i…
-
# Actual behavior
```
1) Integration tests for P2P library
Partially connected network which becomes fully connected: All nodes launch at the same time. The seedPeers list of each node c…
-
Hi,
i want to fork lisk to create my own blaockchain and cryptocurrency.Can u help me with the steps to fork the lisk?
Thank you.
-
For old-time-sake, this is just a heads-up on the database development, since I'm not on the Slack anymore.
The main drive toward the recent release of [pg-promise v9.0.0](https://github.com/vitaly…
-
### Expected behavior
### Scope
The goal of this issue is to make sure that the _newPeers and _triedPeers (address book) does not grow to unlimited size. This should be done according to the LIP…
-
### Expected behavior
The implementation should be written in a more generic way, allowing the user to update whichever property is available and updateable in the state.
For that, we could define…
-
### Expected behavior
Return proper error message when the action is not public.
--> [Referring to discussion leading up to this issue](https://github.com/LiskHQ/lisk-sdk/issues/4070#issuecomment-52…
-
### Expected behavior
Breaking changes should be documented and reflected in tests.
### Actual behavior
Looks like `modules.chain.broadcasts.broadcastLimit` (previously used only for blocks broadca…