From 6a3f36075a723bd756b01dbe9bdaf3ce0d809ef3 Mon Sep 17 00:00:00 2001 From: bkchr Date: Tue, 30 Jan 2024 00:49:22 +0000 Subject: [PATCH] deploy: 34d26ff1aa343b0cc980afbf2f40c1d5b6a781ea --- print.html | 22 +++++-------------- .../0046-metadata-for-offline-signers.html | 22 +++++-------------- searchindex.js | 2 +- searchindex.json | 2 +- 4 files changed, 12 insertions(+), 36 deletions(-) diff --git a/print.html b/print.html index 5f5c9e7..fbacb55 100644 --- a/print.html +++ b/print.html @@ -1631,7 +1631,8 @@ is the correct way of introducing this change.

Summary

-

Add a metadata digest value (33-byte constant within fixed spec_version) to Signed Extensions to supplement signer party with proof of correct extrinsic interpretation. The digest value is generated once before release and is well-known and deterministic. The digest mechanism is designed to be modular and flexible. It also supports partial metadata transfer as needed by the signing party's extrinsic decoding mechanism. This considers signing devices potentially limited communication bandwidth and/or memory capacity.

+

Add a metadata digest value to signed data to supplement signer party with proof of correct extrinsic interpretation. This would ensure that hardware wallets always use correct metadata to decode the information for the user.

+

The digest value is generated once before release and is well-known and deterministic. The digest mechanism is designed to be modular and flexible. It also supports partial metadata transfer as needed by the signing party's extrinsic decoding mechanism. This considers signing devices potentially limited communication bandwidth and/or memory capacity.

Motivation

Background

While all blockchain systems support (at least in some sense) offline signing used in air-gapped wallets and lightweight embedded devices, only few allow simultaneously complex upgradeable logic and full message decoding on the cold off-line signer side; Substrate is one of these heartening few, and therefore - we should build on this feature to greatly improve transaction security, and thus in general, network resilience.

@@ -1649,7 +1650,7 @@ is the correct way of introducing this change.