-
### Expected behavior
Unused definitions are removed.
### Actual behavior
Every time node start the warning is being shown:
```
WARNING: NODE_ENV value of 'test' did not match any deployment conf…
-
### Expected behavior
We are rebuilding the blockchain while taking snapshot and ore restoring it by rebuild. Actually that process should take very long time, "blockchain" verification should be don…
-
## Parent https://github.com/LiskHQ/lisk/issues/3153
### Expected behavior
Update the new README file for the framework-level folder. Describe the general idea of the framework-level and a purpose b…
-
The transactions module declares many functions which are just wrapper functions for transaction pool, hence can be replaced. Furthermore, the transactions module declares function getPooledTransactio…
-
### Expected behavior
Postgres should not spawn too many connections
### Actual behavior
When i run rebuild/verification against `2.0.0-alpha.x` version node i see too many process spawned
```
li…
-
### Expected behavior
Transaction fees should be assignable as part of created transactions extending `BaseTransaction` interface, e.g. by creating a new `static FEE` property.
- fees of transact…
-
### Expected behavior
Blockchain verification process should not connect to the network. it should not make any outbound connection or not connect to any peers at all(including itself).
### Actual b…
-
### Expected behavior
Transactions type 4 should be propagated to all nodes of the network.
### Actual behavior
There are issues with the propagation of those transactions. When we query `api/node/…
-
### Expected behavior
In release planned as 2.0 we made a lot of changes to configuration structure. So the `udpate_config.js` must work with that version and make the right changes to user specifi…
-
### Expected behavior
Move required `network` tests from https://github.com/LiskHQ/lisk-sdk/tree/development/framework/test/mocha/network to https://github.com/LiskHQ/lisk-core/tree/master/qa
### Ac…