Slashing: on-chain evaluation of misbehavior reports from the BFT and statement table subsystems

[rphmeier]

...and automatically generate transactions with any witnessed misbehavior.

Should be simple enough:

• Each misbehavior report must be accompanied by some security bond.
• Each report contains a validator who misbehaved, the block hash they were building on when they misbehaved, and the proof of misbehavior
• A report is valid iff the validator was a validator at the given block hash and the misbehavior given is true.

BFT misbehavior reports could be managed at the substrate level.
Parachain Statement Table misbehavior can only be managed in the polkadot runtime -- and will often require proofs of group membership at a block in recent history. We will need to make sure that all duty rosters within some range of history are computable.

[gavofyork]

@rphmeier i can help out on this regarding runtime logic and slashing, but will need help on logic for determining if "the misbehavior given is true"

[smisty]

What does that mean?

…

On Tue, Feb 16, 2021, 4:24 PM Robert Habermeier ***@***.***> wrote: Closed #81 <#81>. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#81 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARSJH44CFGPAR5PBAU5RPE3S7LWBNANCNFSM4ESBBMOQ> .