-
Notifications
You must be signed in to change notification settings - Fork 513
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't find SECP-256k1 description by Gura et al. [2004] + other issues for Appendix F #335
Comments
For formula 214, secp256k1n= 115792089237316195423570985008687907852837564279074904382605163141518161494337, have a footnote to say that this is FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD036 in hexadecimal (which is 78 characters in length, so it is also less than 16^78 = 8.3436994e+93). I noticed that this line is commented out: |
For the added refs, see ethereum#335 For Appendix F: - ECDSAWikipedia and ECDSAcerticom for "we assert the functions ECDSASIGN, ECDSARESTORE and ECDSAPUBKEY. These are formally defined in the literature." ethereum#335 (comment) - secp256k1BitcoinWiki2016 and secp256k1StackExchange2014 for Secp256k1. ethereum#335 (comment) - npmElectrum2017 for Electrum style signatures. ethereum#335 (comment)
This issue contains many points, many of which have materialized into a PR and requires no further discussion here. So it's not trivial to see if anything remains to be answered or discussed here. Suggestion1: open a new issue for each logically independent issue. Suggestion2: keep a list of open points in the first comment of the issue
|
Ah, I see that: 2^256 - 2^32 - 977 = These leading digits of the two numbers are the same: 115 792 089 237 316 195 423 570 985 008 687 907 852 837 564 279 074 904 382 605 163 141 518 161 494 337 |
For the added refs, see ethereum#335 For Appendix F: - ECDSAWikipedia and ECDSAcerticom for "we assert the functions ECDSASIGN, ECDSARESTORE and ECDSAPUBKEY. These are formally defined in the literature." ethereum#335 (comment) - secp256k1BitcoinWiki2016 and secp256k1StackExchange2014 for Secp256k1. ethereum#335 (comment) - npmElectrum2017 for Electrum style signatures. ethereum#335 (comment)
Unresolved comments remain:
I moved most of the original comments to #327 where the changes have been made, except for the below one.
The text was updated successfully, but these errors were encountered: