marioevz / blobber Goto Github PK

We need an endpoint to be able to automate the verification of slashing due to equivocating block header in the blobs.

The minimum should be:

• An API endpoint to set a proposal action on a running blobber, in order to be able to dynamically change the proposal action to a single blobber using an external automation tool
• An API to query action results, in order to the external automation tool to be able to determine whether the action has already been executed or not, and also to get information about which validator key was used to perform the action (to know which validator we need to verify slashing for). Potentially we need to come up with a Proposal-Action-ID perhaps to be able to query for specific actions that only this external automation tool instructed?
• Introduce one-shot-actions which are removed after being successfully executed once.

• Equivocating block slot action might be affected because the graffiti modification does affect the state root (Block is invalid)
• Refactor the remaining slot actions: ExtraBlobs, ConflictingBlobs (Might be unnecessary due to EquivocatingBlockHeaderInBlobs), SwapBlobs

Introduce a logging action which would not interrupt any block request from the validator client, relay it verbatim instead, and log every request's contents.

Plz add this.