hotstuff
hotstuff copied to clipboard
asonnino
Implementation of the HotStuff consensus protocol.
It seems that there is a typo in this following line when reading node parameters https://github.com/asonnino/hotstuff/blob/d771d4868db301bcb5e3deaa915b5017220463f6/benchmark/benchmark/config.py#L94
We currently reply to any sync request we receive, which costs us resources (specifically for the worker). We need to do some accounting to prevent bad nodes from monopolizing our...
The core of consensus and mempool both use the same channel for loopback messages and net messages. This is a problem: a bad node may format their messages as "loopback"...
* Added profile module * Annotated task launch to use the profiler * Added async_profile script to make pretty graphs The profiler requires the package `graphviz` and is used as...
A bad node may make us run out of memory by sending many votes with different round numbers (as long as they are bigger than our current round) or with...
Is it possible to have an upper bound on how much storage is required to run a node for one epoch?
The committee contains an epoch number, but it is never used to reject messages from wrong epochs.
A bad node may make us store a lot of crap. There is currently no limit to how many payload they can send us, and we will store them all.
Safety-critical information such as the last voted round are currently not persisted to storage.