Skip to content

Commit 20d6464

Browse files
Update eth_sign reference (#1741)
1 parent 21abb3c commit 20d6464

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

wallet/concepts/signing-methods.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,11 @@ The text prefix of `personal_sign` makes signatures expensive to verify onchain.
3131
If onchain verifiability cost is not a priority, you can
3232
[use `personal_sign`](../how-to/sign-data/index.md#use-personal_sign).
3333

34+
:::note
35+
MetaMask implements `personal_sign` similarly to the Go Ethereum client's updated `eth_sign` implementation.
36+
MetaMask's `personal_sign` doesn't accept a password.
37+
:::
38+
3439
## Deprecated signing methods
3540

3641
:::caution important

wallet/how-to/sign-data/index.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -194,11 +194,6 @@ It's often used for signature challenges that are authenticated on a web server,
194194

195195
</p>
196196

197-
Some other signers implement `personal_sign` as `eth_sign`, because the Go Ethereum client changed
198-
the behavior of its `eth_sign` method.
199-
Because MetaMask supports existing applications, MetaMask implements both `personal_sign` and `eth_sign`.
200-
You might need to check what method your supported signers use for a given implementation.
201-
202197
:::caution important
203198

204199
- Don't use this method to display binary data, because the user wouldn't be able to understand what

0 commit comments

Comments
 (0)