ethrex-crypto 17.0.0

Cryptographic primitives and precompile backends for the ethrex Ethereum execution client
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

use crate::provider::Crypto;

/// Native crypto implementation using system libraries.
///
/// Most method bodies live as defaults on the [`Crypto`] trait itself. The
/// P-256 (secp256r1) verify is overridden here to use the assembly-optimized
/// `aws-lc-rs` backend when the `aws-lc-rs` feature is enabled, since the
/// portable `p256` default does two constant-time scalar muls with no
/// Shamir/basepoint optimization and is a P256VERIFY hot-path outlier. On the
/// host the BLS12-381 (EIP-2537) defaults likewise route through the
/// assembly-optimized `blst` backend (the `blst` feature, default-on); zkVM
/// guest builds compile both backends out and use their own `Crypto` providers
/// instead of this type. This
/// struct exists so callers outside zkVM contexts have a concrete type to
/// instantiate.
#[derive(Debug)]
pub struct NativeCrypto;

#[cfg(not(feature = "aws-lc-rs"))]
impl Crypto for NativeCrypto {}

#[cfg(feature = "aws-lc-rs")]
impl Crypto for NativeCrypto {
    fn secp256r1_verify(&self, msg: &[u8; 32], sig: &[u8; 64], pk: &[u8; 64]) -> bool {
        crate::p256_awslc::secp256r1_verify(msg, sig, pk)
    }
}