Make various InvalidUnslashable block reports more specifically identifiable from client side

Description

Currently all of the following validity check failures become an InvalidUnslashableBlock. It is nice to have them grouped as an InvalidUnslashableBlock because unlike most other validity conditions these aren't slashable. However, they make it hard to debug as to which of the conditions failed from only client side messages (note the message is "Failure! Invalid block: InvalidUnslashableBlock" specifically).

1 2 3 4 if (!validFormat) (InvalidUnslashableBlock, dag).pure[F] else if (!validSig) (InvalidUnslashableBlock, dag).pure[F] else if (!validSender) (InvalidUnslashableBlock, dag).pure[F] else if (!validVersion) (InvalidUnslashableBlock, dag).pure[F]

Status

Assignee

Daniyar Itegulov

Reporter

Kent Shikama

Components

Story Points

5

Epic Link

None

Sprint

Fix versions

Priority

Medium