Timeline for While using myetherwallet to generate offline transaction hash, can developer steal my private key?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 14, 2018 at 0:33 | vote | accept | user37661 | ||
| Apr 14, 2018 at 0:33 | |||||
| Apr 13, 2018 at 23:53 | vote | accept | user37661 | ||
| Apr 14, 2018 at 0:32 | |||||
| Apr 11, 2018 at 21:32 | history | edited | Thorkil Værge | CC BY-SA 3.0 |
added 8 characters in body
|
| Apr 11, 2018 at 20:55 | comment | added | user37661 | ok, i got it... | |
| Apr 11, 2018 at 20:52 | comment | added | Thorkil Værge | They will not be completely identical. The last three fields in the signed transaction (last 67 bytes or last 134 hex characters) will differ since they represent the signature and the signing algorithm (ECDSA) takes a random number as input and produces different signatures for each random number. But if they differ other places than that, you should be worried. | |
| Apr 11, 2018 at 20:48 | comment | added | user37661 | Thanks for point me to the right direction. I think to solve this issue, I can: 1) use ethereum-tx-decoder to check the data field to ensure there is nothing there looks suspicious. or 2) find another sign transaction js package to generate a seperated rawTX. compare the one with MEW, as long as they are identical. If either 1 or 2 is true, my final step is to save them to the output file. Can someone point me another script package to run offline to sign transaction? | |
| Apr 11, 2018 at 12:34 | history | edited | Thorkil Værge | CC BY-SA 3.0 |
added 190 characters in body
|
| Apr 11, 2018 at 12:27 | history | answered | Thorkil Værge | CC BY-SA 3.0 |