status-im
/
secp256k1
mirror of https://github.com/status-im/secp256k1.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Make no-float policy explicit 

We don't want floating types for various reasons, e.g.,
 - Their representation and often their behavior is implementation-defined.
 - Many targets don't support them.
This commit is contained in:
Tim Ruffing 2019-11-01 10:39:41 +01:00 committed by GitHub
parent 770b3dcd6f
commit bae1bea3c4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
README.md
View File

@ -23,6 +23,7 @@ Implementation details
* Extensive testing infrastructure. * Extensive testing infrastructure.
* Structured to facilitate review and analysis. * Structured to facilitate review and analysis.
* Intended to be portable to any system with a C89 compiler and uint64_t support. * Intended to be portable to any system with a C89 compiler and uint64_t support.
* No use of floating types, except in benchmarks.
* Expose only higher level interfaces to minimize the API surface and improve application security. ("Be difficult to use insecurely.") * Expose only higher level interfaces to minimize the API surface and improve application security. ("Be difficult to use insecurely.")
* Field operations * Field operations
* Optimized implementation of arithmetic modulo the curve's field size (2^256 - 0x1000003D1). * Optimized implementation of arithmetic modulo the curve's field size (2^256 - 0x1000003D1).