Blockchain Transaction Lifecycle Security Standard Audit Framework

previous: Implement Readability Standards | Contents | next: Present Crucial Information in Readability-optimised form

Render from Signed Bytes

Statement of Requirement

All Actors that provide a user interface MUST derive any rendering of a transaction optimized for human readability from the transaction bytes themselves, and MUST NOT derive it from a request, an intent, or other metadata accompanying them.

See it in the specification

Applicability

All Roles that provide a user interface

Purpose

Ensure that what a person reads describes what the transaction does

Audit Procedure

Determine the source of the data used to produce each human-readable rendering of a transaction.

Present the Role with a transaction whose accompanying metadata disagrees with its bytes, and verify that the rendering follows the bytes.

See also Implement Readability Standards and Verify Received Transactions

Success Criteria

• Renderings are produced by decoding the transaction bytes
• Where metadata accompanying a transaction disagrees with its bytes, the rendering reflects the bytes

Best Practice

The intent declared by the Producer is displayed alongside the rendering, and a disagreement between the two is reported to the person rather than resolved silently.

Failure Criteria

• A rendering is produced from a request, an intent, or other accompanying metadata rather than from the transaction bytes
• A transaction whose accompanying metadata disagrees with its bytes is rendered according to the metadata

Key Evidence

• System documentation
• Source Code
• User interfaces
• Reperformance

previous: Implement Readability Standards | Contents | next: Present Crucial Information in Readability-optimised form