From 84e7c0aff996fffdc71f1ee325a71c172bb448d8 Mon Sep 17 00:00:00 2001 From: Brian Pearce Date: Mon, 12 Aug 2024 16:13:45 +0200 Subject: [PATCH] feat!: ledger metadata signature with receiver adress confirmation (#6462) Description --- Send the user spend public key to the ledger for script generation and user validation via the ledger device. Motivation and Context --- Initially we though we would need to send all the parts to the ledger, instead we will change the format by hashing the script, and hashing all other fields, then hashing those hashes. This allows us to hash the other fields, and send just the hash to the ledger instead of serializing all the independent parts (covenants, encrypted data, etc.) As they have variable lengths and it gets messy quick. Then we can send just the receiver public spend key to the ledger, and use it to generate the entire TariScript for the message, after the user has verified the address on the ledger screen. How Has This Been Tested? --- What process can a PR reviewer use to test or verify this change? --- Breaking Changes --- - [ ] None - [ ] Requires data directory on base node to be deleted - [ ] Requires hard fork - [X] Other - Please specify