trezor: sign message explicitly with ethereum path
Calling this function instead of the generic one makes it open up the derivation
paths users are most likely to be hitting. The custom path case is still prone
to getting tripped up by the "forbidden path" security check though.
commit976258ca20c7b77aae216909b78b7ebe63ccc885
authorfang <git@fang.io>
dateThu 7 Jan 2021, 19:50 (6 years ago)
parentfa1d192
src/lib/trezor.js+1−1
@@ -37,7 +37,7 @@ const trezorSignTransaction = async (txn, hdpath) => {
3737};
3838
3939export const trezorSignMessage = async (message, hdPath) => {
40− const sig = await TrezorConnect.signMessage({
40+ const sig = await TrezorConnect.ethereumSignMessage({
4141 path: hdPath,
4242 message,
4343 });