Struct flow_sdk::algorithms::secp256k1::Secp256k1 [−][src]
pub struct Secp256k1<C> where
C: Context, { /* fields omitted */ }
Expand description
The secp256k1 engine, used to execute all signature operations
Implementations
Creates a new Secp256k1 context that can only be used for signing
Creates a new Secp256k1 context that can only be used for verification
Lets you create a context with preallocated buffer in a generic manner(sign/verify/all)
pub fn preallocated_new(
buf: &'buf mut [AlignedType]
) -> Result<Secp256k1<AllPreallocated<'buf>>, Error>
pub fn preallocated_new(
buf: &'buf mut [AlignedType]
) -> Result<Secp256k1<AllPreallocated<'buf>>, Error>
Creates a new Secp256k1 context with all capabilities
Uses the ffi secp256k1_context_preallocated_size
to check the memory size needed for a context
pub unsafe fn from_raw_all(
raw_ctx: *mut Context
) -> ManuallyDrop<Secp256k1<AllPreallocated<'buf>>>
pub unsafe fn from_raw_all(
raw_ctx: *mut Context
) -> ManuallyDrop<Secp256k1<AllPreallocated<'buf>>>
Create a context from a raw context.
Safety
This is highly unsafe, due to the number of conditions that aren’t checked.
raw_ctx
needs to be a valid Secp256k1 context pointer. that was generated by exactly the same code/version of the libsecp256k1 used here.- The capabilities (All/SignOnly/VerifyOnly) of the context must match the flags passed to libsecp256k1 when generating the context.
- The user must handle the freeing of the context(using the correct functions) by himself.
- Violating these may lead to Undefined Behavior.
pub fn preallocated_signing_only(
buf: &'buf mut [AlignedType]
) -> Result<Secp256k1<SignOnlyPreallocated<'buf>>, Error>
pub fn preallocated_signing_only(
buf: &'buf mut [AlignedType]
) -> Result<Secp256k1<SignOnlyPreallocated<'buf>>, Error>
Creates a new Secp256k1 context that can only be used for signing
Uses the ffi secp256k1_context_preallocated_size
to check the memory size needed for the context
pub unsafe fn from_raw_signining_only(
raw_ctx: *mut Context
) -> ManuallyDrop<Secp256k1<SignOnlyPreallocated<'buf>>>
pub unsafe fn from_raw_signining_only(
raw_ctx: *mut Context
) -> ManuallyDrop<Secp256k1<SignOnlyPreallocated<'buf>>>
Create a context from a raw context.
Safety
This is highly unsafe, due to the number of conditions that aren’t checked.
raw_ctx
needs to be a valid Secp256k1 context pointer. that was generated by exactly the same code/version of the libsecp256k1 used here.- The capabilities (All/SignOnly/VerifyOnly) of the context must match the flags passed to libsecp256k1 when generating the context.
- The user must handle the freeing of the context(using the correct functions) by himself.
- This list is not exhaustive, and any violation may lead to Undefined Behavior.,
pub fn preallocated_verification_only(
buf: &'buf mut [AlignedType]
) -> Result<Secp256k1<VerifyOnlyPreallocated<'buf>>, Error>
pub fn preallocated_verification_only(
buf: &'buf mut [AlignedType]
) -> Result<Secp256k1<VerifyOnlyPreallocated<'buf>>, Error>
Creates a new Secp256k1 context that can only be used for verification
Uses the ffi secp256k1_context_preallocated_size
to check the memory size needed for the context
pub unsafe fn from_raw_verification_only(
raw_ctx: *mut Context
) -> ManuallyDrop<Secp256k1<VerifyOnlyPreallocated<'buf>>>
pub unsafe fn from_raw_verification_only(
raw_ctx: *mut Context
) -> ManuallyDrop<Secp256k1<VerifyOnlyPreallocated<'buf>>>
Create a context from a raw context.
Safety
This is highly unsafe, due to the number of conditions that aren’t checked.
raw_ctx
needs to be a valid Secp256k1 context pointer. that was generated by exactly the same code/version of the libsecp256k1 used here.- The capabilities (All/SignOnly/VerifyOnly) of the context must match the flags passed to libsecp256k1 when generating the context.
- The user must handle the freeing of the context(using the correct functions) by himself.
- This list is not exhaustive, and any violation may lead to Undefined Behavior.,
Create a schnorr signature without using any auxiliary random data.
Create a Schnorr signature using the given auxiliary random data.
Create a schnorr signature using the given random number generator to generate the auxiliary random data. Requires compilation with “rand” feature.
Verify a Schnorr signature.
Generates a random Schnorr KeyPair and its associated Schnorr PublicKey.
Convenience function for schnorrsig::KeyPair::new
and
schnorrsig::PublicKey::from_keypair
; call those functions directly for
batch key generation. Requires a signing-capable context. Requires compilation
with the “rand” feature.
Getter for the raw pointer to the underlying secp256k1 context. This shouldn’t be needed with normal usage of the library. It enables extending the Secp256k1 with more cryptographic algorithms outside of this crate.
Returns the required memory for a preallocated context buffer in a generic manner(sign/verify/all)
(Re)randomizes the Secp256k1 context for cheap sidechannel resistance; see comment in libsecp256k1 commit d2275795f by Gregory Maxwell. Requires compilation with “rand” feature.
(Re)randomizes the Secp256k1 context for cheap sidechannel resistance given 32 bytes of cryptographically-secure random data; see comment in libsecp256k1 commit d2275795f by Gregory Maxwell.
Constructs a signature for msg
using the secret key sk
and RFC6979 nonce
Requires a signing-capable context.
Constructs a signature for msg
using the secret key sk
, RFC6979 nonce
and “grinds” the nonce by passing extra entropy if necessary to produce
a signature that is less than 71 - bytes_to_grund bytes. The number
of signing operation performed by this function is exponential in the
number of bytes grinded.
Requires a signing capable context.
Constructs a signature for msg
using the secret key sk
, RFC6979 nonce
and “grinds” the nonce by passing extra entropy if necessary to produce
a signature that is less than 71 bytes and compatible with the low r
signature implementation of bitcoin core. In average, this function
will perform two signing operations.
Requires a signing capable context.
Generates a random keypair. Convenience function for key::SecretKey::new
and key::PublicKey::from_secret_key
; call those functions directly for
batch key generation. Requires a signing-capable context. Requires compilation
with the “rand” feature.
Checks that sig
is a valid ECDSA signature for msg
using the public
key pubkey
. Returns Ok(())
on success. Note that this function cannot
be used for Bitcoin consensus checking since there may exist signatures
which OpenSSL would verify but not libsecp256k1, or vice-versa. Requires a
verify-capable context.
let message = Message::from_slice(&[0xab; 32]).expect("32 bytes");
let sig = secp.sign(&message, &secret_key);
assert_eq!(secp.verify(&message, &sig, &public_key), Ok(()));
let message = Message::from_slice(&[0xcd; 32]).expect("32 bytes");
assert_eq!(secp.verify(&message, &sig, &public_key), Err(Error::IncorrectSignature));
Trait Implementations
Signs a 256 bit hashed data with the secret key.
Converts a secret key to its public counterpart.
Serializes a public key. Excluding the leading 0x04.
Creates a signature by consuming a populated hasher and a secret key.
Auto Trait Implementations
impl<C> RefUnwindSafe for Secp256k1<C> where
C: RefUnwindSafe,
impl<C> UnwindSafe for Secp256k1<C> where
C: UnwindSafe,
Blanket Implementations
Mutably borrows from an owned value. Read more
Compare self to key
and return true
if they are equal.
Wrap the input message T
in a tonic::Request
Attaches the provided Subscriber
to this type, returning a
WithDispatch
wrapper. Read more
Attaches the current default Subscriber
to this type, returning a
WithDispatch
wrapper. Read more