rise-node
rise-node copied to clipboard
:rainbow: RISE blockchain node
- Checking that it() descriptions are meaningful. - Rewriting all the beforeEach() if they don't are not using container for to create the stubs classes. - To fix small issues.
Some methods are always called by passing a certain parameter with a fixed value. EXAMPLE: in modules/blocks/process, `loadBlocksOffset`, `verify` is always passed as true Check if static analysis tools can...
There are some TODO and FIXME in the code which we should check. Some may be solved already. When solution is complex this should become a GitHub issue.
There are a lot of services coming out that rely on nodes with open APIs. Currently most crypto (dPoS) have nodes with open APIs that are managed by node owners....
**Problem**: Currently if `A` needs to send a transaction to `B` and `B` is in the same network he could: - MITM - Collect the signed transaction on its way...
**Current** A round is *numDelegates* long. When the last block in a round gets forged, all the fees collected during the round are equally distributed among all forgers partecipating such...
Testing **countById()** function at logic/transfer module, I've noticed that if **self.scope.db.one()** returns a reject Promise, the code fail when try to call to... `this.scope.logger.error(err.stack);` because the "**this**" inside the "**catch()**"...
Testing logic/transaction module I've noticed that verify() function is using a variable named 'requester' but never is declared. https://github.com/RiseVision/rise-node/blob/development/logic/transaction.js#L439 Researching about this issue I've discovered that on Lisk version this...
After test logic/vote I've noticed that the method dbRead() of logic/vote is not validating properly if raw.v_votes is a string and if we don't receive a string it will threw...