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
It's not Public Keys that are used as Addresses, but rather PubKeyHashes.
Since Go's standard library doesn't include a function to reverse a Message + Signature to a Public Key, it's not possible to verify a PubKeyHash against a signature natively in Go.
sha3 "golang.org/x/crypto/sha3"
sign
recover
However, it seems that the primarily function that's causing all of the headache with cross compilation has been written natively in C#, and would not be difficult to port to Go.
It's not Public Keys that are used as Addresses, but rather PubKeyHashes.
Since Go's standard library doesn't include a function to reverse a Message + Signature to a Public Key, it's not possible to verify a PubKeyHash against a signature natively in Go.
However, it seems that the primarily function that's causing all of the headache with cross compilation has been written natively in C#, and would not be difficult to port to Go.
See https://stackoverflow.com/a/20000007/151312
The text was updated successfully, but these errors were encountered: