diff options
| author | @RandyMcMillan <randy.lee.mcmillan@gmail.com> | 2024-05-10 09:39:56 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-05-10 09:39:56 -0400 |
| commit | 99435fa0b5160f90242ed1cbe852fe17cf291cfb (patch) | |
| tree | 47e01a84a6cc39754906269deb9fb67b94c7af86 | |
| parent | cc2a9c71a0917236d95e61765b1618a26bb9c2c0 (diff) | |
| download | bips-99435fa0b5160f90242ed1cbe852fe17cf291cfb.tar.xz | |
bip-0388.mediawiki:proof of registration
| -rw-r--r-- | bip-0388.mediawiki | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0388.mediawiki b/bip-0388.mediawiki index 4efc588..511e27c 100644 --- a/bip-0388.mediawiki +++ b/bip-0388.mediawiki @@ -85,7 +85,7 @@ Once a policy is registered, the hardware signing device can perform the typical * showing addresses on the secure screen; * sign transactions spending from a wallet, while correctly identifying change addresses and computing the transaction fees. -Before any of the actions mentioned above, the hardware signing device will retrieve the policy from its permanent storage if stateful; if stateless it will validate the _proof of registration_ before using the wallet policy provided by the client. +Before any of the actions mentioned above, the hardware signing device will retrieve the policy from its permanent storage if stateful; if stateless it will validate the '''proof of registration''' before using the wallet policy provided by the client. Once the previously registered policy is correctly identified and approved by the user (for example by showing its name), and as long as the policy registration was executed securely, hardware signing devices can provide a user experience similar to the usual one for single-signature transactions. |