-
### Expected behavior
Transactions should be processed the same way as in the previous versions (for example `1.6.0`) so backward compatibility is preserved.
### Actual behavior
Transactions are pr…
-
## Fixing fork cause 5 -- Double Forging
### What is double forging?
Double forging occurs when two or more nodes on the network have the same delegate(s) enabled to forge. This has the potentia…
-
Following issues are identified and required to be fixed after restructuring to SDK.
- [x] The command `lerna bootstrap` lead a huge difference int the `framework/package-lock.json`
- [x] Referen…
-
### Expected behavior
With every custom transaction we should be able to specify some distinct fee for it. And that should not involve passing any configuration at application level.
```js
cla…
-
I think current Lisk DPoS is way to centralised and vulnerable to many attacks. One person with big wallet can possibly up vote all his 101 delegates to top 101 forging with current implementation. Th…
ghost updated
5 years ago
-
### Expected behavior
We should make use of the `code` variable after defining it or get rid of it, if it's not needed.
### Actual behavior
code argument provided to `cleanup` method were never use…
yatki updated
5 years ago
-
### Expected behavior
Expect it to not error
### Actual behavior
```
WARNING: Creating a duplicate QueryFile object for the same file -
--
| /opt/app-root/src/framework/src/components/…
-
### Expected behavior
I'm not sure how this should work, but probably it shouldn't modify existing behavior in such a way.
### Actual behavior
It's wrapping functions passed to `jobsQueue`:
```
N…
-
comment from @diego-G:
> After LiskHQ/lisk: Issue #2148
comment from @shuse2:
> This should be carefully considered, because once documented as interface, it's really hard to change
-
### 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…