Use enum in Parsec constructor to replace interesting_event functor

Description

Currently, we give Parsec clients full control over the defninition of an "interesting event" for an opaque payload by handing them a functor.

Make this API a lot harder to misuse by only giving a couple of options:

  • Reach consensus on Opaque payloads seen by supermajority of peers (only on valid blocks)

  • Reach consensus on all single Opaque payloads

This will be done by replacing the functor by a dumb enum with 2 variants.

Environment

None

Status

Assignee

Jon Haggblad

Reporter

Pierre Chevalier

External issue URL

None

External issue ID

None

Start date

2018/11/21

End date

2018/11/21

Task progress

None

Baseline start date

None

Baseline end date

None

Story Points

4

Components

Priority

Major
Configure