From b30e3934a1b67e9d20cf6b4845df1d43b4e4df38 Mon Sep 17 00:00:00 2001 From: Paul Hauner Date: Wed, 16 Feb 2022 11:08:35 +1100 Subject: [PATCH] Clarify `validationError` usage --- src/engine/specification.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/engine/specification.md b/src/engine/specification.md index d6db0afdc91..42c123a4d73 100644 --- a/src/engine/specification.md +++ b/src/engine/specification.md @@ -171,7 +171,7 @@ This structure contains the result of processing a payload. The fields are encod - `status`: `enum` - `"VALID" | "INVALID" | "SYNCING" | "ACCEPTED" | "INVALID_BLOCK_HASH" | "INVALID_TERMINAL_BLOCK"` - `latestValidHash`: `DATA|null`, 32 Bytes - the hash of the most recent *valid* block in the branch defined by payload and its ancestors -- `validationError`: `String|null` - a message providing additional details on the validation error if the payload is deemed `INVALID` +- `validationError`: `String|null` - a message providing additional details on the validation error if the payload is classified as `INVALID`, `INVALID_BLOCK_HASH` or `INVALID_TERMINAL_BLOCK.` ### TransitionConfigurationV1