You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Start eth_sign implementation
* Update eth_sign to new event loop convention
* Draft a proper implementation of #privateKey
* Fix build-node error
* Change storage configuration of account keys
* Check for nonexistent account in eth_sign call
* web3: more specific error message
Copy file name to clipboardExpand all lines: krypto.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,7 @@ module KRYPTO
14
14
-`Sha256` takes a String and returns a 64-character hex-encoded string of the 32-byte SHA2-256 hash of the string.
15
15
-`RipEmd160` takes a String and returns a 40-character hex-encoded string of the 20-byte RIPEMD160 hash of the string.
16
16
-`ECDSARecover` takes a 32-character byte string of a message, v, r, s of the signed message and returns the 64-character public key used to sign the message.
17
+
-`ECDSASign` takes a 32-character byte string of a message hash, a 32-character byte string of a private key, and returns the 65 byte hex-encoded signature in [r,s,v] form
17
18
See [this StackOverflow post](https://ethereum.stackexchange.com/questions/15766/what-does-v-r-s-in-eth-gettransactionbyhash-mean) for some information about v, r, and s.
18
19
19
20
In all functions above, input `String` is interpreted as byte array, e.g. it is NOT hex-encoded.
@@ -23,6 +24,7 @@ In all functions above, input `String` is interpreted as byte array, e.g. it is
0 commit comments