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
The docs for from_seckey_slice, from_seckey_str and from_seckey_str_global state that the functions fail if the "the corresponding public key is not even". I don't see why that would be true. The underlying C-function secp256k1_keypair_create does not fail in that case.
aaf5fee fix: Invalid secret key (Christian Lewe)
d1d4ff9 doc: Keypair constructors accept odd keys (Christian Lewe)
Pull request description:
Clarify the conditions when `Keypair` construction fails and correct the error variant that is returned in one of the constructors. Fixes#758
ACKs for top commit:
Kixunil:
ACK aaf5fee
apoelstra:
ACK aaf5fee; successfully ran local tests
Tree-SHA512: 9b27c4ee1424619f9041183801e7c1214838f0b8d529e9c10a3e1f55264624b6b42b881e369bd9521bfa117d3dd5ce072caed4b8ee51c40e1016fc5be59a2894
The docs for
from_seckey_slice
,from_seckey_str
andfrom_seckey_str_global
state that the functions fail if the "the corresponding public key is not even". I don't see why that would be true. The underlying C-functionsecp256k1_keypair_create
does not fail in that case.Discovered by @uncomputable
The text was updated successfully, but these errors were encountered: