Fuel cryptographic primitives

Overview

Fuel Crypto

build crates.io docs discord

Fuel cryptographic primitives.

Compile features

  • std: Unless set, the crate will link to the core-crate instead of the std-crate. More info here.
  • random: Implement no-std rand features for the provided types.
  • serde-types: Add support for serde for the provided types.
  • serde-types-minimal: Add support for no-std serde for the provided types.
Comments
  • Add verifiable signature

    Add verifiable signature

    Secp contains two classes of signatures: recoverable and unrecoverable.

    Prior to this commit, only the recoverable variant was used. However, the consensus will require signature verification, so the introduction of the two classes of signatures is required.

    opened by vlopes11 10
  • Signer

    Signer

    Signing with private key of validator is needed in a few places:

    • Consensus: Sign new block
    • Consensus: Sign consensus vote
    • Relayer: Sign eth transaction for committing new block.

    We would like to have only one place where we load private key, and that place should have the ability to sign arbitrary hash that it receives from other parts of code. The proposed way is to have tokio::sync::mpsc for incoming requests that would contain tokio::sync::oneshot to return signature in that way there is no exposing of secret info.

    opened by rakita 5
  • Migrate mnemonic logic from fuel-rs to fuel-crypto

    Migrate mnemonic logic from fuel-rs to fuel-crypto

    mnemonics aren't exclusive to SDK/Wallet use-cases, so to avoid requiring the whole SDK we should move core logic related to mnemonic->SecretKey utilities to fuel-crypto.

    cc @digorithm

    opened by Voxelot 1
  • Re-export mnemonic deps

    Re-export mnemonic deps

    We used types from third party libraries in our APIs which weren't re-exported. This means consumers of the library would have to include these same deps with matching versions in their own crates to use the secret key mnemonic api.

    opened by Voxelot 0
  • Bump to v0.6.0

    Bump to v0.6.0

    What's Changed

    • Move mnemonic logic from the SDK by @digorithm in https://github.com/FuelLabs/fuel-crypto/pull/28

    New Contributors

    • @digorithm made their first contribution in https://github.com/FuelLabs/fuel-crypto/pull/28

    Full Changelog: https://github.com/FuelLabs/fuel-crypto/compare/v0.5.0...v0.6.0

    opened by vlopes11 0
  • Move mnemonic logic from the SDK

    Move mnemonic logic from the SDK

    Closes https://github.com/FuelLabs/fuel-crypto/issues/27.

    Note that these changes include some dependencies updates that were forced onto us because of conflicting deps' versions in the bip32/bip39 crates.

    With these dependencies updates, some updates on our end had to be done as well. Small things such as replacing deprecated methods with new ones, etc.

    enhancement 
    opened by digorithm 0
  • Add static secp256k1 for sig w/ benches

    Add static secp256k1 for sig w/ benches

    The secp256k1 provider shouldn't be instantiated on every request. Instead, it should be instantiated once, with a lazy strategy, and made available for signature requests.

    This commit introduces lazy_static to achieve that. Lazy is still experimental in std, so we need to wait for its stabilization before requiring it.

    In order to increase the robustness of the secp provider, we introduce rand-std for secp256k1. This feature will boost the entropy of the blinders, further protecting the implementation from side-channel attacks. This will not remove the deterministic nonce requirement, as defined in the RFC-6979 and the fuel crypto specs.

    Include benchmarks comparing fuel-crypto, secp256k1 and k256

    Resolves #3

    enhancement 
    opened by vlopes11 0
  • make docs feature aware on docs.rs

    make docs feature aware on docs.rs

    Leverage special nightly features enabled on docs.rs which allow denoting feature flags in our docs. fuel-crypto-docs

    To test out the docs as docs.rs would render them use: RUSTDOCFLAGS="--cfg docsrs" cargo +nightly doc --all-features --open

    opened by Voxelot 0
  • Add `From<Hasher>` to signature `Message`

    Add `From` to signature `Message`

    Hasher is a cryptographic secure hasher and is allowed to produce signature inputs.

    Signatures are secure only if the input is pre-image checked and non-malleable; this is a hard requirement for any signature protocol.

    enhancement 
    opened by vlopes11 0
  • Bump fuel-types to v0.3

    Bump fuel-types to v0.3

    Even though this crate doesn't actually use anything in the new fuel-types version, it's needed in order to prevent crate version mismatch downstream.

    opened by adlerjohn 0
  • Add `Signer` to `no-std`

    Add `Signer` to `no-std`

    Signer can be represented as trait in no-std without a provided implementation.

    This is desirable to define the abstraction of the trait in no-std consumers such as fuel-bft.

    opened by vlopes11 0
  • feat: expose more methods to WASM builds

    feat: expose more methods to WASM builds

    This PR builds upon #26 and @vlopes11's comment to actually make WASM builds of fuel-crypto meaningfully usable. It requires reorganization of code in #[cfg(feature = "std")] blocks, as WASM is a no-std environment.

    I imagine this PR to be unpleasant to review through diffs, so I'll list what methods were made available here when it's done™.

    opened by Br1ght0ne 0
  • Consider using 32 bytes representation for `PublicKey`

    Consider using 32 bytes representation for `PublicKey`

    Currently we use raw uncompressed 64 bytes. To get 32 bytes, we hash the affine representation of the point.

    However, we might be able to store the 32 bytes in compressed form. This will allow us to skip the hash and consume less bytes of storage, since the public key will already be a 32 bytes representation that can be used as address.

    The compressed point holds an extra byte to encode the parity of elements.

    As in sec1-v2, we might be able to use the last bit of n[32] to encode that information and then apply 2.3.4.2.3 mutation. However, that needs to be confirmed.

    Other point to check is the fuel specs and fuels implementation: https://github.com/FuelLabs/fuel-crypto/pull/9#issuecomment-1039701064

    opened by vlopes11 3
  • Consider using `derive_more`

    Consider using `derive_more`

    All of these new-type passthrough methods (Deref, AsRef, Into, From, LowerHex, UpperHex, etc) could be automatically generated using the derive_more crate.

    it supports no_std out of the box

    Originally posted by @Voxelot in https://github.com/FuelLabs/fuel-crypto/pull/2#discussion_r801152338

    enhancement good first issue help wanted tech-debt 
    opened by vlopes11 0
  • Add fuzzy tests to signature

    Add fuzzy tests to signature

    This seems quite costly to exhaustively fuzz the entire search space every test run. Using prop-tests we could randomly sample the distribution on each test run and easily track which input params cause a failure:

    
    use proptest::prelude::{
        prop::test_runner::{RngAlgorithm, TestRng}, *,
    };
    prop_compose! {
        fn arb_rng()(
            bytes: [u8; 32],
        ) -> TestRng {
            TestRng::from_seed(RngAlgorithm::ChaCha, &bytes)
        }
    }
    
    proptest! {
        #![proptest_config(ProptestConfig::with_cases(50))]
        #[test]
        fn corrupted_signature(
            mut rng in arb_rng(),
            position in 0..Signature::LEN,
            bit in 0..7,
        ) {
            let message = b"When life itself seems lunatic, who knows where madness lies?";
            let message = Message::new(message);
    
            let secret = SecretKey::random(&mut rng);
            let public = secret.public_key();
    
            let signature = Signature::sign(&secret, &message);
    
            // Tamper a random bit of the signature
            //
            // The recover and verify operations should fail in all cases.
    
            let mut s = signature;
            let m = 1u8 << bit;
            s.as_mut()[position] ^= m;
    
            // check recover
            match s.recover(&message) {
                Ok(pk) => assert_ne!(public, pk),
                Err(Error::InvalidSignature) => (),
                Err(e) => panic!("Unexpected error: {}", e),
            }
    
            // check verify
            assert!(s.verify(&public, &message).is_err());
        }
    
        #[test]
        fn corrupted_public_key(
            mut rng in arb_rng(),
            position in 0..PublicKey::LEN,
            bit in 0..7,
        ) {
            let message = b"When life itself seems lunatic, who knows where madness lies?";
            let message = Message::new(message);
    
            let secret = SecretKey::random(&mut rng);
            let mut public = secret.public_key();
    
            let signature = Signature::sign(&secret, &message);
    
            // Tamper a random bit of the public key.
            //
            // The verify operations should fail in all cases.
            let m = 1u8 << bit;
            public.as_mut()[position] ^= m;
            assert!(signature.verify(&public, &message).is_err());
        }
    }
    
    

    Originally posted by @Voxelot in https://github.com/FuelLabs/fuel-crypto/pull/2#discussion_r801197967

    enhancement good first issue help wanted 
    opened by vlopes11 0
  • Use native verify

    Use native verify

    To simplify the initial implementation, we are using a plain recover for the verify operation.

    However, recover is more expensive than verify. After https://github.com/FuelLabs/fuel-crypto/issues/3 , we should compare the performance gain of using native verify instead of recover, pk == pk_p

    The pseudocode for the native verify with secp256k1 backend is:

            pub fn verify(mut self, pk: &PublicKey, message: &Message) -> Result<(), Error> {
                self.truncate_recovery_id();
    
                let signature = Secp256k1Signature::from_compact(self.as_ref())?;
    
                let message = message.to_secp();
                let pk = pk.to_secp()?;
    
                Secp256k1::verification_only().verify(&message, &signature, &pk)?;
    
                Ok(())
            }
    
    enhancement good first issue help wanted 
    opened by vlopes11 1
Releases(v0.6.2)
  • v0.6.2(Oct 25, 2022)

    What's Changed

    • Re-export mnemonic deps by @Voxelot in https://github.com/FuelLabs/fuel-crypto/pull/33
    • release re-exported deps by @Voxelot in https://github.com/FuelLabs/fuel-crypto/pull/34

    Full Changelog: https://github.com/FuelLabs/fuel-crypto/compare/v0.6.1...v0.6.2

    Source code(tar.gz)
    Source code(zip)
  • v0.6.1(Oct 25, 2022)

  • v0.6.0(Aug 4, 2022)

    What's Changed

    • Move mnemonic logic from the SDK by @digorithm in https://github.com/FuelLabs/fuel-crypto/pull/28
    • Bump to v0.6.0 by @vlopes11 in https://github.com/FuelLabs/fuel-crypto/pull/29

    New Contributors

    • @digorithm made their first contribution in https://github.com/FuelLabs/fuel-crypto/pull/28

    Full Changelog: https://github.com/FuelLabs/fuel-crypto/compare/v0.5.0...v0.6.0

    Source code(tar.gz)
    Source code(zip)
  • v0.5.0(May 13, 2022)

    What's Changed

    • reexport dependencies used in the public api by @Voxelot in https://github.com/FuelLabs/fuel-crypto/pull/20
    • make docs feature aware on docs.rs by @Voxelot in https://github.com/FuelLabs/fuel-crypto/pull/21
    • Add static secp256k1 for sig w/ benches by @vlopes11 in https://github.com/FuelLabs/fuel-crypto/pull/22
    • Update features set to new optional deps schema by @vlopes11 in https://github.com/FuelLabs/fuel-crypto/pull/23
    • Update fuel-types to v0.5 by @vlopes11 in https://github.com/FuelLabs/fuel-crypto/pull/24
    • Bump to v0.5.0 by @vlopes11 in https://github.com/FuelLabs/fuel-crypto/pull/25

    New Contributors

    • @Voxelot made their first contribution in https://github.com/FuelLabs/fuel-crypto/pull/20

    Full Changelog: https://github.com/FuelLabs/fuel-crypto/compare/v0.4.2...v0.5.0

    Source code(tar.gz)
    Source code(zip)
  • v0.4.2(Mar 30, 2022)

    What's Changed

    • Add From<Hasher> to signature Message by @vlopes11 in https://github.com/FuelLabs/fuel-crypto/pull/18
    • Bump to 0.4.2 by @vlopes11 in https://github.com/FuelLabs/fuel-crypto/pull/19

    Full Changelog: https://github.com/FuelLabs/fuel-crypto/compare/v0.4.1...v0.4.2

    Source code(tar.gz)
    Source code(zip)
  • v0.4.1(Mar 29, 2022)

    What's Changed

    • Add Cargo.toml linting to the CI pipeline by @Dentosal in https://github.com/FuelLabs/fuel-crypto/pull/15
    • Add impl FromStr for Signature by @Br1ght0ne in https://github.com/FuelLabs/fuel-crypto/pull/16
    • Bump to 0.4.1 by @Br1ght0ne in https://github.com/FuelLabs/fuel-crypto/pull/17

    New Contributors

    • @Dentosal made their first contribution in https://github.com/FuelLabs/fuel-crypto/pull/15
    • @Br1ght0ne made their first contribution in https://github.com/FuelLabs/fuel-crypto/pull/16

    Full Changelog: https://github.com/FuelLabs/fuel-crypto/compare/v0.4.0...v0.4.1

    Source code(tar.gz)
    Source code(zip)
  • v0.4.0(Mar 8, 2022)

    What's Changed

    • Add Signer to no-std by @vlopes11 in https://github.com/FuelLabs/fuel-crypto/pull/12
    • Bump to v0.4.0 by @vlopes11 in https://github.com/FuelLabs/fuel-crypto/pull/14

    Full Changelog: https://github.com/FuelLabs/fuel-crypto/compare/v0.3.0...v0.4.0

    Source code(tar.gz)
    Source code(zip)
  • v0.3.0(Mar 1, 2022)

    What's Changed

    • Add Signer trait by @vlopes11 in https://github.com/FuelLabs/fuel-crypto/pull/9
    • Bump fuel-types to v0.3 by @adlerjohn in https://github.com/FuelLabs/fuel-crypto/pull/13
    • Bump to v0.3.0 by @vlopes11 in https://github.com/FuelLabs/fuel-crypto/pull/11

    New Contributors

    • @adlerjohn made their first contribution in https://github.com/FuelLabs/fuel-crypto/pull/13

    Full Changelog: https://github.com/FuelLabs/fuel-crypto/compare/v0.2.0...v0.3.0

    Source code(tar.gz)
    Source code(zip)
  • v0.2.0(Feb 9, 2022)

    What's Changed

    • Add verifiable signature by @vlopes11 in https://github.com/FuelLabs/fuel-crypto/pull/2
    • Bump version to v0.2.0 by @vlopes11 in https://github.com/FuelLabs/fuel-crypto/pull/8

    Full Changelog: https://github.com/FuelLabs/fuel-crypto/compare/v0.1.0...v0.2.0

    Source code(tar.gz)
    Source code(zip)
  • v0.1.0(Jan 26, 2022)

    What's Changed

    • Initial impl of hasher and ECC key pair by @vlopes11 in https://github.com/FuelLabs/fuel-crypto/pull/1

    New Contributors

    • @vlopes11 made their first contribution in https://github.com/FuelLabs/fuel-crypto/pull/1

    Full Changelog: https://github.com/FuelLabs/fuel-crypto/commits/v0.1.0

    Source code(tar.gz)
    Source code(zip)
Owner
Fuel Labs
Fuel Labs is a group focused on sustainable blockchain scaling with optimistic rollups.
Fuel Labs
Lockstitch is an incremental, stateful cryptographic primitive for symmetric-key cryptographic operations in complex protocols.

Lockstitch is an incremental, stateful cryptographic primitive for symmetric-key cryptographic operations (e.g. hashing, encryption, message authentication codes, and authenticated encryption) in complex protocols.

Coda Hale 4 Dec 2, 2022
A Rust port of the password primitives used in Django Project.

Rust DjangoHashers A Rust port of the password primitives used in Django Project. Django's django.contrib.auth.models.User class has a few methods to

Ronaldo Ferreira 52 Nov 17, 2022
A Rust port of the password primitives used in Django Project.

Rust DjangoHashers A Rust port of the password primitives used in Django Project. Django's django.contrib.auth.models.User class has a few methods to

Ronaldo Ferreira 52 Nov 17, 2022
Easy to use cryptographic framework for data protection: secure messaging with forward secrecy and secure data storage. Has unified APIs across 14 platforms.

Themis provides strong, usable cryptography for busy people General purpose cryptographic library for storage and messaging for iOS (Swift, Obj-C), An

Cossack Labs 1.6k Nov 29, 2022
A (mostly) pure-Rust implementation of various cryptographic algorithms.

Rust-Crypto A (mostly) pure-Rust implementation of various common cryptographic algorithms. Rust-Crypto seeks to create practical, auditable, pure-Rus

null 1.2k Nov 24, 2022
Sodium Oxide: Fast cryptographic library for Rust (bindings to libsodium)

sodiumoxide |Crate|Documentation|Gitter| |:---:|:-----------:|:--------:|:-----:|:------:|:----:| |||| NaCl (pronounced "salt") is a new easy-to-use h

sodiumoxide 642 Nov 12, 2022
Collection of cryptographic hash functions written in pure Rust

RustCrypto: hashes Collection of cryptographic hash functions written in pure Rust. All algorithms reside in the separate crates and implemented using

Rust Crypto 1.1k Nov 25, 2022
Modern Cryptographic Firmware

Trussed® Modern Cryptographic Firmware Status Very much WIP. Actively developed. Unstable APIs.

Trussed® 298 Dec 1, 2022
Secure storage for cryptographic secrets in Rust

secrets secrets is a library to help Rust programmers safely held cryptographic secrets in memory. It is mostly an ergonomic wrapper around the memory

Stephen Touset 163 Oct 31, 2022
Pure Rust implementation of the RNCryptor cryptographic format by Rob Napier

rncryptor Rust Implementation of the RNCryptor spec This library implements the specification for the RNCryptor encrypted file format by Rob Napier. d

null 7 Jun 29, 2022
Pure-Rust traits and utilities for constant-time cryptographic implementations.

subtle Pure-Rust traits and utilities for constant-time cryptographic implementations. It consists of a Choice type, and a collection of traits using

dalek cryptography 193 Oct 27, 2022
Cryptographic Primitive Code Generation by Fiat

Fiat-Crypto: Synthesizing Correct-by-Construction Code for Cryptographic Primitives Building This repository requires Coq 8.11 or later. Note that if

Programming Languages and Verification Group at MIT CSAIL 511 Nov 19, 2022
Cryptographic signature algorithms: ECDSA, Ed25519

RustCrypto: signatures Support for digital signatures, which provide authentication of data using public-key cryptography. All algorithms reside in th

Rust Crypto 289 Nov 21, 2022
the official Rust and C implementations of the BLAKE3 cryptographic hash function

BLAKE3 is a cryptographic hash function that is: Much faster than MD5, SHA-1, SHA-2, SHA-3, and BLAKE2. Secure, unlike MD5 and SHA-1. And secure again

BLAKE3 team 3.7k Nov 25, 2022
Fastmurmur3 - Fast non-cryptographic hash, with the benchmarks to prove it.

Fastmurmur3 Murmur3 is a fast, non-cryptographic hash function. fastmurmur3 is, in my testing, the fastest implementation of Murmur3. Usage let bytes:

Kurt Wolf 14 Sep 22, 2022
Dexios-Core is a library used for managing cryptographic functions and headers that adhere to the Dexios format.

What is it? Dexios-Core is a library used for managing cryptographic functions and headers that adhere to the Dexios format. Security Dexios-Core uses

brxken 3 Jul 4, 2022
Common cryptographic library used in software at Mysten Labs.

[fastcrypto] fastcrypto is a common cryptography library used in software at Mysten Labs. It is published as an independent crate to encourage reusabi

Mysten Labs 76 Nov 26, 2022
The underlying cryptographic primitives for Manta Ecosystem

manta crypto The underlying cryptography that manta ecosystem relies on. It comes with the following traits: checksum: definitions for message digest.

Manta Network 10 Nov 10, 2021
A set of cryptographic primitives for building a multi-hop Proxy Re-encryption scheme, known as Transform Encryption.

recrypt A pure-Rust library that implements a set of cryptographic primitives for building a multi-hop Proxy Re-encryption scheme, known as Transform

IronCore Labs 121 Nov 28, 2022
Lockstitch is an incremental, stateful cryptographic primitive for symmetric-key cryptographic operations in complex protocols.

Lockstitch is an incremental, stateful cryptographic primitive for symmetric-key cryptographic operations (e.g. hashing, encryption, message authentication codes, and authenticated encryption) in complex protocols.

Coda Hale 4 Dec 2, 2022