Timeline for ECDSA: (v, r, s), what is v?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2021 at 7:34 | history | edited | CommunityBot |
replaced https://tools.ietf.org/html/rfc with https://www.rfc-editor.org/rfc/rfc
|
|
| Aug 1, 2015 at 11:04 | comment | added | Wizard Of Ozzie | @DavidGrayson yeah, have amended title :) | |
| Aug 1, 2015 at 0:47 | comment | added | David Grayson |
Yeah, so v has to do with signing, not RFC6979.
|
|
| Jul 31, 2015 at 23:10 | comment | added | Pieter Wuille | secp256k1_ecdsa_sign_compact (old API) or secp256k1_pubkey_serialize_compact (new API) do return the recovery id (the value v, but without the 27 constant term). See my answer. | |
| Jul 2, 2015 at 1:33 | comment | added | David Grayson |
The only other implementation I have seen is libsecp256k1, which does not return a v number. That library provides a function named secp256k1_nonce_function_rfc6979 whose only output is a 32-byte buffer of data.
|
|
| Jul 2, 2015 at 0:42 | comment | added | Wizard Of Ozzie |
Right, but does v appear across implementations? Pybitcointools isn't the only implementation to use it, I believe.
|
|
| Jul 1, 2015 at 21:36 | history | answered | David Grayson | CC BY-SA 3.0 |