Skip to content
This repository was archived by the owner on Nov 30, 2018. It is now read-only.
This repository was archived by the owner on Nov 30, 2018. It is now read-only.

Improve security of consensus #25

@clawoflight

Description

@clawoflight

Because of the way we currently handle the consensus, we don't have any metric for how often it was committed vs the next most common hash.

This could e.g. be remedied by:

  • using the difference between the most common hash and the second most common hash
  • using a factor of the most common hash and the second most common hash
  • ?

We could add this as an additional metric, or replace our current return value with it.

The worst case is we only mention this as a possible improvement in the evaluation section of the paper, but we'd be much more secure if we added that.
What do you think?

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions