diff options
| author | willcl-ark <will@256k1.dev> | 2024-04-29 13:50:08 +0100 |
|---|---|---|
| committer | willcl-ark <will@256k1.dev> | 2024-05-03 08:36:57 +0100 |
| commit | fb9f150759b22772dd48983a2be1ea397245e289 (patch) | |
| tree | 64afa0324cec6e7714ef3dbe72fa62440686b9d1 /src/qt/forms | |
| parent | a46065e36cf868265c909dc5edf29dc17be53c1f (diff) | |
gui: fix misleading signmessage error with segwit
As described in #10542 (and numerous other places), message signing in
Bitcoin Core only supports message signing using P2PKH addresses, at
least until a new message-signing standard is agreed upon.
Therefore update the possibly-misleading error message presented to the
user in the GUI to detail more specifically the reason their message
cannot be signed, in the case that a non P2PKH address is entered.
Diffstat (limited to 'src/qt/forms')
| -rw-r--r-- | src/qt/forms/signverifymessagedialog.ui | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/qt/forms/signverifymessagedialog.ui b/src/qt/forms/signverifymessagedialog.ui index f42d19093b..b72360b586 100644 --- a/src/qt/forms/signverifymessagedialog.ui +++ b/src/qt/forms/signverifymessagedialog.ui @@ -30,7 +30,7 @@ <item> <widget class="QLabel" name="infoLabel_SM"> <property name="text"> - <string>You can sign messages/agreements with your addresses to prove you can receive bitcoins sent to them. Be careful not to sign anything vague or random, as phishing attacks may try to trick you into signing your identity over to them. Only sign fully-detailed statements you agree to.</string> + <string>You can sign messages/agreements with your legacy (P2PKH) addresses to prove you can receive bitcoins sent to them. Be careful not to sign anything vague or random, as phishing attacks may try to trick you into signing your identity over to them. Only sign fully-detailed statements you agree to.</string> </property> <property name="textFormat"> <enum>Qt::PlainText</enum> |