You need to prase CBOR message in order to determine its size.
CBOR wrapped inside another CBOR is CBOR. This means you don't need any additional memory (as is the case, for example, in Base64) in order to parse the CBOR-encoded object (e.g. transaction) wrapped inside CBOR.
As a consequence, there is no added value, if we pass two separate Meta+Message CBOR-encoded messages to the hardware wallet, so we combine them inside a single Data CBOR-encoded map with metadata and tx fields.
Changes to ADR 14:
metadata
andtx
fields respectively.metadata.chain_context
encoding.Rationale:
As a consequence, there is no added value, if we pass two separate Meta+Message CBOR-encoded messages to the hardware wallet, so we combine them inside a single Data CBOR-encoded map with
metadata
andtx
fields.