rbsecp256k1 5.1.1 → 6.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3f0c0d659103f52aa0a9762d464bfacd9a656d90dfd38815b7b954c863aa5bb2
-  data.tar.gz: 7e74a91710993a87a4a931be6091e16af32960e91ebe67a731ffb0ee498593ba
+  metadata.gz: 6a9f1c61d2e9881ffc8ba67ad800fe73d5b54b0e03728a18886c11cb865e00d4
+  data.tar.gz: 007d212fbc0d6a669f2fc9fc944c9e6b823c67cca59d98401c1840bc424f1944
 SHA512:
-  metadata.gz: 69cdae2b446230a9908aa0b799b4c36d09bf5486c118468a43be4ffa128f304e7cf608bab222bebb8acdbb1bf7848619dd2a55e583ce07b14a851d3657cc0d6b
-  data.tar.gz: 52b48f20f66ac1635358e924fcc9a1c47bf53962610ecbaca099611d69c42d994f4c8c886a172ed1e3402c241be86e6977edd9b674960b1f5acedc30c5d8326a
+  metadata.gz: 35c81811e74cecf9d268d447296956aefccb8de97dbf877b83b43f9ad09fcdccd8c4e93ae55dd24939227933835715336d6eac42753a9d762c2e939df0859580
+  data.tar.gz: f86d36d6c52ff5c9ed2d08c90d62170dd9dc66c411ff6c374c3904c57497940137415f5281a3f0080f54b53478813494f289ad3a66300f8ffe0ad896879112e4

data/LICENSE

@@ -0,0 +1,24 @@
+This is free and unencumbered software released into the public domain.
+
+Anyone is free to copy, modify, publish, use, compile, sell, or
+distribute this software, either in source code form or as a compiled
+binary, for any purpose, commercial or non-commercial, and by any
+means.
+
+In jurisdictions that recognize copyright laws, the author or authors
+of this software dedicate any and all copyright interest in the
+software to the public domain. We make this dedication for the benefit
+of the public at large and to the detriment of our heirs and
+successors. We intend this dedication to be an overt act of
+relinquishment in perpetuity of all present and future rights to this
+software under copyright law.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR
+OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
+ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
+OTHER DEALINGS IN THE SOFTWARE.
+
+For more information, please refer to <https://unlicense.org>

data/README.md

@@ -1,157 +1,129 @@
-# rbsecp256k1
-
-[![Spec](https://github.com/etscrivner/rbsecp256k1/actions/workflows/spec.yml/badge.svg?branch=master)](https://github.com/etscrivner/rbsecp256k1/actions/workflows/spec.yml) [![Gem Version](https://badge.fury.io/rb/rbsecp256k1.svg)](https://badge.fury.io/rb/rbsecp256k1) [![Maintainability](https://api.codeclimate.com/v1/badges/d4b6e27bfa00030ca412/maintainability)](https://codeclimate.com/github/etscrivner/rbsecp256k1/maintainability)
-
-Native extension gem for secp256k1 ECDSA. Wraps [libsecp256k1](https://github.com/bitcoin-core/secp256k1). In
-rbsecp256k1 3.0.0 and later libsecp256k1 is bundled with the gem.
-
-* [Documentation](https://github.com/etscrivner/rbsecp256k1/blob/master/documentation/index.md)
-* [Examples](https://github.com/etscrivner/rbsecp256k1/blob/master/examples/README.md)
-
-### Why wrap libsecp256k1?
-
-[libsecp256k1](https://github.com/bitcoin-core/secp256k1) is an extremely optimized implementation of public key derivation,
-signing, and verification with the secp256k1 elliptic curve. It comes with its
-own set of benchmarks, but from [benchmarking done by Peter Wuille](https://www.reddit.com/r/Bitcoin/comments/2weymr/experiment_bitcoin_core_0100_initial_sync_time/coqghm2) it is ~4.9x
-faster than the OpenSSL implementation of the same curve. It is the only library
-that provides constant time signing of this curve and has been deployed as part
-of Bitcoin since [v0.10.0](https://bitcoin.org/en/release/v0.10.0#improved-signing-security)
-
-Natively wrapping the library in an extension gem means users don't have to
-worry about compiling or locating the library, unlike many [FFI](https://github.com/ffi/ffi) based gems.
-
-## Installation
-
-The simplest installation:
-
-```
-gem install rbsecp256k1
-```
-
-## Requirements
-
-If you want to use your system version of libsecp256k1 rather than the bundled
-version use the `--with-system-libraries` flag:
-
-```
-gem install rbsecp256k1 -- --with-system-libraries
-```
-
-#### Linux
-
-Install the dependencies for building libsecp256k1 and this library:
-
-```
-sudo apt-get install build-essential automake pkg-config libtool \
-  libffi-dev libssl-dev libgmp-dev python3-dev
-```
-
-**NOTE:** If you have installed libsecp256k1 but the gem cannot find it. Ensure
-you have run `ldconfig` so that your library load paths have been updated.
-
-#### macOS
-
-Dependencies for building libsecp256k1 and this library:
-
-```
-brew install automake openssl libtool pkg-config gmp libffi
-```
-
-## Features
-
-See [rbsecp256k1 documentation](https://github.com/etscrivner/rbsecp256k1/blob/master/documentation/index.md) for examples and complete list of supported functionality.
-
-## Development
-
-### Cloning
-
-To clone the repository and its submodules you'll need to the following:
-
-```
-git clone git@github.com:etscrivner/rbsecp256k1.git
-```
-
-### Setup
-
-Development is largely facilitated by a makefile. After download you should run
-the following command to set up your local environment:
-
-```
-make setup
-```
-
-### Compiling Extension
-
-To compile the extension gem run the following (this is required to run tests):
-
-```
-make build
-```
-
-### Running Tests
-
-```
-make test
-```
-
-To test with recovery functionality disabled run:
-
-```
-make test WITH_RECOVERY=0
-```
-
-To test with ECDH functionality disabled run:
-
-```
-make test WITH_ECDH=0
-```
-
-To test with both disabled run:
-
-```
-make test WITH_RECOVERY=0 WITH_ECDH=0
-```
-
-Testing for memory leaks with valgrind:
-
-```
-make memcheck
-```
-
-### Building Gem
-
-```
-make gem
-```
-
-### Installing Gem Locally
-
-To install the gem locally and verify builds you can run:
-
-```
-make install
-```
-
-### Uninstall Gem Locally
-
-You can similarly uninstall the local gem by running the following:
-
-```
-make uninstall
-```
-
-### Cleaning Up
-
-To clean up and do a fresh build:
-
-```
-make clean
-```
-
-### Running YARD Documentation Server
-
-To run the [YARD](https://yardoc.org/) documentation server:
-
-```
-make docserver
-```
+# rbsecp256k1
+
+[![Spec](https://github.com/etscrivner/rbsecp256k1/actions/workflows/spec.yml/badge.svg?branch=master)](https://github.com/etscrivner/rbsecp256k1/actions/workflows/spec.yml) [![Gem Version](https://badge.fury.io/rb/rbsecp256k1.svg)](https://badge.fury.io/rb/rbsecp256k1) [![Maintainability](https://api.codeclimate.com/v1/badges/d4b6e27bfa00030ca412/maintainability)](https://codeclimate.com/github/etscrivner/rbsecp256k1/maintainability)
+
+Native extension gem for secp256k1 ECDSA and Schnorr signatures. Wraps [libsecp256k1](https://github.com/bitcoin-core/secp256k1) without the need for FFI.
+
+* [Documentation](https://github.com/etscrivner/rbsecp256k1/blob/master/documentation/index.md)
+* [Examples](https://github.com/etscrivner/rbsecp256k1/blob/master/examples/README.md)
+
+### Features
+
+* Native extension gem wrapping [libsecp256k1](https://github.com/bitcoin-core/secp256k1), no FFI.
+* Schnorr signature support.
+
+### Why wrap libsecp256k1?
+
+[libsecp256k1](https://github.com/bitcoin-core/secp256k1) is an extremely optimized implementation of public key derivation,
+signing, and verification with the secp256k1 elliptic curve. It comes with its
+own set of benchmarks, but from [benchmarking done by Peter Wuille](https://www.reddit.com/r/Bitcoin/comments/2weymr/experiment_bitcoin_core_0100_initial_sync_time/coqghm2) it is ~4.9x
+faster than the OpenSSL implementation of the same curve. It is the only library
+that provides constant time signing of this curve and has been deployed as part
+of Bitcoin since [v0.10.0](https://bitcoin.org/en/release/v0.10.0#improved-signing-security)
+
+Natively wrapping the library in an extension gem means users don't have to
+worry about compiling or locating the library, unlike many [FFI](https://github.com/ffi/ffi) based gems.
+
+## Installation
+
+The simplest installation:
+
+```
+gem install rbsecp256k1
+```
+
+## Requirements
+
+If you want to use your system version of libsecp256k1 rather than the bundled
+version use the `--with-system-libraries` flag:
+
+```
+gem install rbsecp256k1 -- --with-system-libraries
+```
+
+#### Linux
+
+Install the dependencies for building libsecp256k1 and this library:
+
+```
+sudo apt-get install build-essential automake pkg-config libtool \
+  libffi-dev libssl-dev libgmp-dev python3-dev
+```
+
+**NOTE:** If you have installed libsecp256k1 but the gem cannot find it. Ensure
+you have run `ldconfig` so that your library load paths have been updated.
+
+#### macOS
+
+Dependencies for building libsecp256k1 and this library:
+
+```
+brew install automake openssl libtool pkg-config gmp libffi
+```
+
+## Features
+
+See [rbsecp256k1 documentation](https://github.com/etscrivner/rbsecp256k1/blob/master/documentation/index.md) for examples and complete list of supported functionality.
+
+## Development
+
+### Cloning
+
+To clone the repository and its submodules you'll need to the following:
+
+```
+git clone git@github.com:etscrivner/rbsecp256k1.git
+```
+
+### Setup
+
+Development is largely facilitated by a makefile. After download you should run
+the following command to set up your local environment:
+
+```
+make setup
+```
+
+### Compiling Extension
+
+To compile the extension gem run the following (this is required to run tests):
+
+```
+make build
+```
+
+### Running Tests
+
+```
+make test
+```
+
+To test with recovery functionality disabled run:
+
+```
+make test WITH_RECOVERY=0
+```
+
+### Uninstall Gem Locally
+
+You can similarly uninstall the local gem by running the following:
+
+```
+make uninstall
+```
+
+### Cleaning Up
+
+To clean up and do a fresh build:
+
+```
+make clean
+```
+
+### Running YARD Documentation Server
+
+To run the [YARD](https://yardoc.org/) documentation server:
+
+```
+make docserver
+```

data/Rakefile

@@ -1,18 +1,18 @@
-# frozen_string_literal: true
-
-require "rake/extensiontask"
-require "ruby_memcheck"
-require "rspec/core/rake_task"
-require 'ruby_memcheck/rspec/rake_task'
-
-RubyMemcheck.config(binary_name: "rbsecp256k1")
-
-# See: https://guides.rubygems.org/gems-with-extensions/
-Rake::ExtensionTask.new "rbsecp256k1" do |ext|
-  ext.lib_dir = 'lib/rbsecp256k1'
-end
-
-RSpec::Core::RakeTask.new(:spec)
-namespace :spec do
-  RubyMemcheck::RSpec::RakeTask.new(valgrind: :spec)
-end
+# frozen_string_literal: true
+
+require "rake/extensiontask"
+require "ruby_memcheck"
+require "rspec/core/rake_task"
+require 'ruby_memcheck/rspec/rake_task'
+
+RubyMemcheck.config(binary_name: "rbsecp256k1")
+
+# See: https://guides.rubygems.org/gems-with-extensions/
+Rake::ExtensionTask.new "rbsecp256k1" do |ext|
+  ext.lib_dir = 'lib/rbsecp256k1'
+end
+
+RSpec::Core::RakeTask.new(:spec)
+namespace :spec do
+  RubyMemcheck::RSpec::RakeTask.new(valgrind: :spec)
+end

data/documentation/context.md

@@ -1,81 +1,98 @@
-[Index](index.md)
-
-Secp256k1::Context
-==================
-
-Secp256k1::Context represents a libsecp256k1 context object. Contexts are
-thread-safe and initialization is expensive, so a single context should be used
-for multiple operations as much as possible.
-
-Initializers
-------------
-
-#### new(context_randomization_bytes: nil)
-
-Returns a newly initialized libsecp256k1 context. The context is randomized at
-initialization if given `context_randomization_bytes`. The
-`context_randomization_bytes` argument can optionally take a string containing
-32 bytes of random data, if not provided then the Context is not randomized and
-may be vulnerable to side-channel attacks.
-
-Class Methods
--------------
-
-#### create
-
-Creates and returns a new randomized `Context` using `SecureRandom` for the
-random initialization bytes. This is the recommended method for initialization.
-
-#### create_unrandomized
-
-Creates a new unrandomized `Context`.
-
-Instance Methods
-----------------
-
-#### ecdh(point, scalar)
-
-**Requires:** libsecp256k1 was built with the experimental ECDH module.
-
-Takes a `point` ([PublicKey](public_key.md)) and a `scalar` ([PrivateKey](private_key.md)) and returns a new
-[SharedSecret](shared_secret.md) containing the 32-byte shared secret. Raises a `Secp256k1::Error` if
-the `scalar` is invalid (zero or causes an overflow).
-
-#### generate_key_pair
-
-Generates and returns a new [KeyPair](key_pair.md) using a cryptographically
-secure random number generator (CSRNG) provided by OpenSSL.
-
-#### key_pair_from_private_key(private_key_data)
-
-Returns a new [KeyPair](key_pair.md) from the given `private_key_data`. The
-`private_key_data` is expected to be a binary string. Raises a `Secp256k1::Error`
-if the private key is invalid or key derivation fails.
-
-#### recoverable_signature_from_compact(compact_signature, recovery_id)
-
-**Requires:** libsecp256k1 was build with recovery module.
-
-Attempts to load a [RecoverableSignature](recoverable_signature.md) from the given `compact_signature`
-and `recovery_id`. Raises a `Secp256k1::DeserializationError` if the signature data or recovery ID are invalid.
-
-#### sign(private_key, hash32)
-
-Signs the SHA-256 hash given by `hash32` using `private_key` and returns a new
-[Signature](signature.md). The `private_key` is expected to be a [PrivateKey](private_key.md)
-object and `data` can be either a binary string or text.
-
-#### sign_recoverable(private_key, hash32)
-
-**Requires:** libsecp256k1 was build with recovery module.
-
-Signs the data represented by the SHA-256 hash `hash32` using `private_key` and returns a
-new [RecoverableSignature](recoverable_signature.md). The `private_key` is expected to be a [PrivateKey](private_key.md) and
-`data` can be either a binary string or text.
-
-#### verify(signature, public_key, hash32)
-
-Verifies the given `signature` ([Signature](signature.md)) was signed by
-the private key corresponding to `public_key` ([PublicKey](public_key.md)) and signed `hash32`. Returns `true`
-if `signature` is valid or `false` otherwise. Note that `data` can be either a
-text or binary string.
+[Index](index.md)
+
+Secp256k1::Context
+==================
+
+Secp256k1::Context represents a libsecp256k1 context object. Contexts are
+thread-safe and initialization is expensive, so a single context should be used
+for multiple operations as much as possible.
+
+Initializers
+------------
+
+#### new(context_randomization_bytes: nil)
+
+Returns a newly initialized libsecp256k1 context. The context is randomized at
+initialization if given `context_randomization_bytes`. The
+`context_randomization_bytes` argument can optionally take a string containing
+32 bytes of random data, if not provided then the Context is not randomized and
+may be vulnerable to side-channel attacks.
+
+Class Methods
+-------------
+
+#### create
+
+Creates and returns a new randomized `Context` using `SecureRandom` for the
+random initialization bytes. This is the recommended method for initialization.
+
+#### create_unrandomized
+
+Creates a new unrandomized `Context`.
+
+Instance Methods
+----------------
+
+#### ecdh(point, scalar)
+
+Takes a `point` ([PublicKey](public_key.md)) and a `scalar` ([PrivateKey](private_key.md)) and returns a new
+[SharedSecret](shared_secret.md) containing the 32-byte shared secret. Raises a `Secp256k1::Error` if
+the `scalar` is invalid (zero or causes an overflow).
+
+#### generate_key_pair
+
+Generates and returns a new [KeyPair](key_pair.md) using Ruby's built-in
+`SecureRandom` cryptographically secure random number generator. This method
+simply invokes `key_pair_from_private_key` with the value from
+`SecureRandom.random_bytes`.
+
+#### key_pair_from_private_key(private_key_data)
+
+Returns a new [KeyPair](key_pair.md) from the given `private_key_data`. The
+`private_key_data` is expected to be a binary string. Raises a `Secp256k1::Error`
+if the private key is invalid or key derivation fails.
+
+#### recoverable_signature_from_compact(compact_signature, recovery_id)
+
+**Requires:** libsecp256k1 was build with recovery module.
+
+Attempts to load a [RecoverableSignature](recoverable_signature.md) from the given `compact_signature`
+and `recovery_id`. Raises a `Secp256k1::DeserializationError` if the signature data or recovery ID are invalid.
+
+#### sign(private_key, hash32)
+
+Signs the SHA-256 hash given by `hash32` using `private_key` and returns a new
+[Signature](signature.md). The `private_key` is expected to be a [PrivateKey](private_key.md)
+object and `data` can be either a binary string or text.
+
+#### sign_recoverable(private_key, hash32)
+
+**Requires:** libsecp256k1 was build with recovery module.
+
+Signs the data represented by the SHA-256 hash `hash32` using `private_key` and returns a
+new [RecoverableSignature](recoverable_signature.md). The `private_key` is expected to be a [PrivateKey](private_key.md) and
+`data` can be either a binary string or text.
+
+#### sign_schnorr(keypair, message)
+
+Same as `sign_schnorr_custom(keypair, message, auxrand)` but generates
+`auxrand` for you using `SecureRandom`. This should almost always be the method
+used for Schnorr signing.
+
+#### sign_schnorr_custom(keypair, message, auxrand)
+
+Sign the given 32-byte binary string `message` using the given `keypair`. It is
+recommend that `message` be generated using `tagged_sha256`. `auxrand` should
+be 32-bytes of fresh randomness, but can optionally be `nil` if generating
+randomness is expensive.
+
+#### tagged_sha256(tag, message)
+
+Computes the tagged hash as defined in [BIP-340](https://github.com/bitcoin/bips/blob/master/bip-0340.mediawiki). Returns the 32-byte binary string tagged hash.
+
+#### verify(signature, public_key, hash32)
+
+Verifies the given `signature` ([Signature](signature.md)) was signed by
+the private key corresponding to `public_key` ([PublicKey](public_key.md)) and signed `hash32`. Returns `true`
+if `signature` is valid or `false` otherwise. Note that `data` can be either a
+text or binary string.