-
## SCOPE
This issue depends on how https://github.com/LiskHQ/lisk-sdk/issues/3344 is implemented, it's possible that it may not require additional work. The goal of this issue is to make sure that …
-
### Description
The `getUniqueOutboundConnectedPeers` method doesn't fit well with the rest of the P2P library API. Instead, there should be a method to expose all outbound PeerInfo and another met…
-
### Expected behavior
1. Delete all blocks from current chain up to common block C we found (ref. https://github.com/LiskHQ/lisk-sdk/issues/4337 for finding common block) and put them in the `temp_bl…
-
### Expected behavior
The branch `feature/introduce_bft_consensus` has problems syncing to the network as it cannot find delegates. The full log can be found at the bottom of the issue.
### Actual…
-
### Expected behavior
Per https://github.com/LiskHQ/lisk-sdk/issues/4337 we have found the common block and validated the block with the three checks outlined in the issue.
When the checks pass, …
-
### Expected behavior
Latest transactions from Testnest API should be consistent.
### Actual behavior
Latest transactions from Testnest API are not consistent and returns different transactions e…
-
### Expected behavior
Documentation should mention that `libtool,` `automake,` `autoconf` are needed to npm the lisk-sdk. `sudo apt install libtool automake autoconf` fixes it.
### Actual behavio…
-
### Expected behavior
Expect to be able to build lisk in an environment that has a policy of using LTS node versions.
### Actual behavior
Unable to build.
```
npm info it worked if it e…
-
### Expected behavior
Multiple pieces of code have `101` as `ACTIVE_DELEGATES` constant hardcoded which impacts the calculation of fees et al.
### Steps to reproduce
Change `default/constants.js`…
-
### Description
Although the SDK can register a default block processor, Core should register the ones that are going to be in use for Lisk's own network.
### Motivation
The SDK should be unaware o…