humanode
humanode copied to clipboard
Humanode Network node code.
At the current moment we use default voting rules for grandpa. But there is a way to define a custom rules options like doing finalisation in every 50 blocks, etc....
Currently, there are two functions `create_extrinsic` in _humanode-peer_ benchmark code and `create_transaction` in _humanode-runtime_ that have overlapping scope. Find a way to refactor unify these two functions
Based on - [Add new hardware and software metrics](https://github.com/paritytech/substrate/commit/5597a93a8c8b1ab578693c68549e3ce1902f3eaf) - [Warn validators with slow hardware](https://github.com/humanode-network/substrate/commit/38ec2d8957d843fa424397f79a484d773eea1454) - [Move slow hardware warning print logic to CLI](https://github.com/humanode-network/substrate/commit/355e4a9c87f85637185c0852bda9aeb3db404b6d)
Based on https://skyharbor.certik.com/report/34dc4ecb-4776-4bf3-9750-b3f0d60c3efc?findingIndex=1669045928236
Check the details - https://skyharbor.certik.com/report/34dc4ecb-4776-4bf3-9750-b3f0d60c3efc?findingIndex=1669134848618 https://skyharbor.certik.com/report/34dc4ecb-4776-4bf3-9750-b3f0d60c3efc?findingIndex=1668082578478
As a follow up of #324 and [discussion](https://github.com/humanode-network/humanode/pull/324#pullrequestreview-984699782).
As a follow up of #510 Related to https://github.com/humanode-network/frontier/commit/2d802a10c9e17bc2585415781fd374ecfea9f8be