ecdc9a9 · bridge · git.iko.soy

login: update hardware wallets copy

commitecdc9a9b6020c07b788654239d2d5bba0dc82830 authorLiam Fitzgerald <liam@urizen.co> dateTue 31 Mar 2020, 09:24 (7 years ago) parentf877a8a

3 files changed+6−3

unifiedsplit

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.ethereumSignTransaction({

40+ const sig = await TrezorConnect.signMessage({

4141 path: hdPath,

4242 message,

4343 });

src/views/Login/Ledger.js+2−1

@@ -164,7 +164,8 @@ export default function Ledger({ className, goHome }) {

164164 application. If you're running on older firmware, make sure the "browser

165165 support" option is turned on. To sign transactions, you'll also need to

166166 enable the "contract data" option. You will be prompted to sign a

167− message. This allows Bridge to operate correctly.

167+ message. This allows Bridge to operate correctly. Never sign this hash

168+ outside of Bridge.

168169 </Grid.Item>

169170

170171 <BridgeForm

src/views/Login/Trezor.js+3−1

@@ -104,7 +104,9 @@ export default function Trezor({ className, goHome }) {

104104 <Grid className={className}>

105105 <Grid.Item full as={Text} className="f6 gray4 mb3">

106106 Connect and authenticate to your Trezor. If you'd like to use a custom

107− derivation path, you may enter it below.

107+ derivation path, you may enter it below. Upon login, you will prompted

108+ to sign the message "Bridge Authentication Token". This allows Bridge to

109+ operate correctly. Never sign this message outside of Bridge.

108110 </Grid.Item>

109111

110112 <BridgeForm