absolutebi/serai
1
0
Fork 0
mirror of https://github.com/serai-dex/serai.git synced 2025-12-08 20:29:23 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
2be69b23b1bc36389d2870e8853f73d75fca8fb4
serai/tests/no-std/Cargo.toml

69 lines
2.2 KiB
TOML
Raw Normal View History

Add no_std support to transcript, dalek-ff-group, ed448, ciphersuite, multiexp, schnorr, and monero-generators transcript, dalek-ff-group, ed449, and ciphersuite are all usable with no_std alone. The rest additionally require alloc. Part of #279.
2023-04-22 04:38:47 -04:00
[package]
Split up tests in CI to avoid node storage limits
2023-07-14 13:02:58 -04:00
name = "serai-no-std-tests"
Add no_std support to transcript, dalek-ff-group, ed448, ciphersuite, multiexp, schnorr, and monero-generators transcript, dalek-ff-group, ed449, and ciphersuite are all usable with no_std alone. The rest additionally require alloc. Part of #279.
2023-04-22 04:38:47 -04:00
version = "0.1.0"
description = "A crate to test no-std builds of Serai crates work"
license = "MIT"
Split up tests in CI to avoid node storage limits
2023-07-14 13:02:58 -04:00
repository = "https://github.com/kayabaNerve/serai/tree/develop/tests/no-std"
Add no_std support to transcript, dalek-ff-group, ed448, ciphersuite, multiexp, schnorr, and monero-generators transcript, dalek-ff-group, ed449, and ciphersuite are all usable with no_std alone. The rest additionally require alloc. Part of #279.
2023-04-22 04:38:47 -04:00
authors = ["Luke Parker <lukeparker5132@gmail.com>"]
Corrections to prior commit
2023-07-14 13:10:30 -04:00
keywords = ["nostd", "no_std", "alloc"]
Add no_std support to transcript, dalek-ff-group, ed448, ciphersuite, multiexp, schnorr, and monero-generators transcript, dalek-ff-group, ed449, and ciphersuite are all usable with no_std alone. The rest additionally require alloc. Part of #279.
2023-04-22 04:38:47 -04:00
edition = "2021"
publish = false
[package.metadata.docs.rs]
all-features = true
rustdoc-args = ["--cfg", "docsrs"]
Add workspace lints
2023-12-16 20:54:24 -05:00
[lints]
workspace = true
Add no_std support to transcript, dalek-ff-group, ed448, ciphersuite, multiexp, schnorr, and monero-generators transcript, dalek-ff-group, ed449, and ciphersuite are all usable with no_std alone. The rest additionally require alloc. Part of #279.
2023-04-22 04:38:47 -04:00
[dependencies]
Expose `std_shims::io` on `core` The `io::Write` trait is somewhat worthless, being implemented for nothing, yet `Read` remains fully functional. This also allows using its polyfills _without_ requiring `alloc`. Opportunity taken to make `schnorr-signatures` not require `alloc`. This will require a version bump before being published due to newly requiring the `alloc` feature be specified to maintain pre-existing behavior. Enables resolving https://github.com/monero-oxide/monero-oxide/issues/48.
2025-09-15 21:21:30 -04:00
std-shims = { path = "../../common/std-shims", default-features = false }
Correct no-std builds
2023-10-31 07:55:25 -04:00
flexible-transcript = { path = "../../crypto/transcript", default-features = false, features = ["recommended", "merlin"] }
Add no_std support to transcript, dalek-ff-group, ed448, ciphersuite, multiexp, schnorr, and monero-generators transcript, dalek-ff-group, ed449, and ciphersuite are all usable with no_std alone. The rest additionally require alloc. Part of #279.
2023-04-22 04:38:47 -04:00
Tweak `multiexp` to compile on `core` On `core`, it'll use a serial implementation of no benefit other than the fact that when `alloc` _is_ enabled, it'll use the multi-scalar multiplication algorithms. `schnorr-signatures` was prior tweaked to include a shim for `SchnorrSignature::verify` which didn't use `multiexp_vartime` yet this same premise. Now, instead of callers writing these shims, it's within `multiexp`.
2025-09-15 22:37:59 -04:00
multiexp = { path = "../../crypto/multiexp", default-features = false }
Differentiate `no-std` from `alloc` within `tests/no-std` Fixes `no-std` builds for packages which intended to be `no-std` (without `alloc`). Updates a variety of MSRVs to 1.73 due to `flexible-transcript` no longer using `std-shims` to achieve 1.66 (as `std-shims` requires `alloc`). A future improvement would be for `std-shims` to have an `alloc` feature and only provide MSRV shims without it.
2025-08-29 01:07:11 -04:00
Correct no-std builds
2023-10-31 07:55:25 -04:00
dalek-ff-group = { path = "../../crypto/dalek-ff-group", default-features = false }
minimal-ed448 = { path = "../../crypto/ed448", default-features = false }
Add no_std support to transcript, dalek-ff-group, ed448, ciphersuite, multiexp, schnorr, and monero-generators transcript, dalek-ff-group, ed449, and ciphersuite are all usable with no_std alone. The rest additionally require alloc. Part of #279.
2023-04-22 04:38:47 -04:00
Differentiate `no-std` from `alloc` within `tests/no-std` Fixes `no-std` builds for packages which intended to be `no-std` (without `alloc`). Updates a variety of MSRVs to 1.73 due to `flexible-transcript` no longer using `std-shims` to achieve 1.66 (as `std-shims` requires `alloc`). A future improvement would be for `std-shims` to have an `alloc` feature and only provide MSRV shims without it.
2025-08-29 01:07:11 -04:00
ciphersuite = { path = "../../crypto/ciphersuite", default-features = false }
Add no_std support to transcript, dalek-ff-group, ed448, ciphersuite, multiexp, schnorr, and monero-generators transcript, dalek-ff-group, ed449, and ciphersuite are all usable with no_std alone. The rest additionally require alloc. Part of #279.
2023-04-22 04:38:47 -04:00
Expose `std_shims::io` on `core` The `io::Write` trait is somewhat worthless, being implemented for nothing, yet `Read` remains fully functional. This also allows using its polyfills _without_ requiring `alloc`. Opportunity taken to make `schnorr-signatures` not require `alloc`. This will require a version bump before being published due to newly requiring the `alloc` feature be specified to maintain pre-existing behavior. Enables resolving https://github.com/monero-oxide/monero-oxide/issues/48.
2025-09-15 21:21:30 -04:00
schnorr-signatures = { path = "../../crypto/schnorr", default-features = false }
Add no_std support to transcript, dalek-ff-group, ed448, ciphersuite, multiexp, schnorr, and monero-generators transcript, dalek-ff-group, ed449, and ciphersuite are all usable with no_std alone. The rest additionally require alloc. Part of #279.
2023-04-22 04:38:47 -04:00
Differentiate `no-std` from `alloc` within `tests/no-std` Fixes `no-std` builds for packages which intended to be `no-std` (without `alloc`). Updates a variety of MSRVs to 1.73 due to `flexible-transcript` no longer using `std-shims` to achieve 1.66 (as `std-shims` requires `alloc`). A future improvement would be for `std-shims` to have an `alloc` feature and only provide MSRV shims without it.
2025-08-29 01:07:11 -04:00
prime-field = { path = "../../crypto/prime-field", default-features = false }
short-weierstrass = { path = "../../crypto/short-weierstrass", default-features = false }
Move the contents of the `evrf/` folder to the `crypto/` folder It was justified when it had several libraries, which it no longer does thanks to the upstreaming with monero-oxide.
2025-08-28 23:55:05 -04:00
secq256k1 = { path = "../../crypto/secq256k1", default-features = false }
embedwards25519 = { path = "../../crypto/embedwards25519", default-features = false }
Downstream the eVRF libraries from FCMP++ Also adds no-std support to secq256k1 and embedwards25519.
2025-01-29 22:29:40 -05:00
Differentiate `no-std` from `alloc` within `tests/no-std` Fixes `no-std` builds for packages which intended to be `no-std` (without `alloc`). Updates a variety of MSRVs to 1.73 due to `flexible-transcript` no longer using `std-shims` to achieve 1.66 (as `std-shims` requires `alloc`). A future improvement would be for `std-shims` to have an `alloc` feature and only provide MSRV shims without it.
2025-08-29 01:07:11 -04:00
dkg = { path = "../../crypto/dkg", default-features = false, optional = true }
Smash the singular `Ciphersuite` trait into multiple This helps identify where the various functionalities are used, or rather, not used. The `Ciphersuite` trait present in `patches/ciphersuite`, facilitating the entire FCMP++ tree, only requires the markers _and_ canonical point decoding. I've opened a PR to upstream such a trait into `group` (https://github.com/zkcrypto/group/pull/68). `WrappedGroup` is still justified for as long as `Group::generator` exists. Moving `::generator()` to its own trait, on an independent structure (upstream) would be massively appreciated. @tarcieri also wanted to update from `fn generator()` to `const GENERATOR`, which would encourage further discussion on https://github.com/zkcrypto/group/issues/32 and https://github.com/zkcrypto/group/issues/45, which have been stagnant. The `Id` trait is occasionally used yet really should be first off the chopping block. Finally, `WithPreferredHash` is only actually used around a third of the time, which more than justifies it being a separate trait. --- Updates `dalek_ff_group::Scalar` to directly re-export `curve25519_dalek::Scalar`, as without issue. `dalek_ff_group::RistrettoPoint` also could be replaced with an export of `curve25519_dalek::RistrettoPoint`, yet the coordinator relies on how we implemented `Hash` on it for the hell of it so it isn't worth it at this time. `dalek_ff_group::EdwardsPoint` can't be replaced for an re-export of `curve25519_dalek::SubgroupPoint` as it doesn't implement `zeroize`, `subtle` traits within a released, non-yanked version. Relevance to https://github.com/serai-dex/serai/issues/201 and https://github.com/dalek-cryptography/curve25519-dalek/issues/811#issuecomment-3247732746. Also updates the `Ristretto` ciphersuite to prefer `Blake2b-512` over `SHA2-512`. In order to maintain compliance with FROST's IETF standard, `modular-frost` defines its own ciphersuite for Ristretto which still uses `SHA2-512`.
2025-09-03 12:25:37 -04:00
dkg-evrf = { path = "../../crypto/dkg/evrf", default-features = false, features = ["secp256k1", "ed25519"], optional = true }
Correct various no_std definitions
2023-05-13 04:03:56 -04:00
# modular-frost = { path = "../../crypto/frost", default-features = false }
# frost-schnorrkel = { path = "../../crypto/schnorrkel", default-features = false }
Add no_std support to transcript, dalek-ff-group, ed448, ciphersuite, multiexp, schnorr, and monero-generators transcript, dalek-ff-group, ed449, and ciphersuite are all usable with no_std alone. The rest additionally require alloc. Part of #279.
2023-04-22 04:38:47 -04:00
Differentiate `no-std` from `alloc` within `tests/no-std` Fixes `no-std` builds for packages which intended to be `no-std` (without `alloc`). Updates a variety of MSRVs to 1.73 due to `flexible-transcript` no longer using `std-shims` to achieve 1.66 (as `std-shims` requires `alloc`). A future improvement would be for `std-shims` to have an `alloc` feature and only provide MSRV shims without it.
2025-08-29 01:07:11 -04:00
bitcoin-serai = { path = "../../networks/bitcoin", default-features = false, features = ["hazmat"], optional = true }
[features]
alloc = [
Expose `std_shims::io` on `core` The `io::Write` trait is somewhat worthless, being implemented for nothing, yet `Read` remains fully functional. This also allows using its polyfills _without_ requiring `alloc`. Opportunity taken to make `schnorr-signatures` not require `alloc`. This will require a version bump before being published due to newly requiring the `alloc` feature be specified to maintain pre-existing behavior. Enables resolving https://github.com/monero-oxide/monero-oxide/issues/48.
2025-09-15 21:21:30 -04:00
"std-shims/alloc",
Tweak `multiexp` to compile on `core` On `core`, it'll use a serial implementation of no benefit other than the fact that when `alloc` _is_ enabled, it'll use the multi-scalar multiplication algorithms. `schnorr-signatures` was prior tweaked to include a shim for `SchnorrSignature::verify` which didn't use `multiexp_vartime` yet this same premise. Now, instead of callers writing these shims, it's within `multiexp`.
2025-09-15 22:37:59 -04:00
"multiexp/alloc",
"multiexp/batch",
Differentiate `no-std` from `alloc` within `tests/no-std` Fixes `no-std` builds for packages which intended to be `no-std` (without `alloc`). Updates a variety of MSRVs to 1.73 due to `flexible-transcript` no longer using `std-shims` to achieve 1.66 (as `std-shims` requires `alloc`). A future improvement would be for `std-shims` to have an `alloc` feature and only provide MSRV shims without it.
2025-08-29 01:07:11 -04:00
"dalek-ff-group/alloc",
"minimal-ed448/alloc",
"ciphersuite/alloc",
Expose `std_shims::io` on `core` The `io::Write` trait is somewhat worthless, being implemented for nothing, yet `Read` remains fully functional. This also allows using its polyfills _without_ requiring `alloc`. Opportunity taken to make `schnorr-signatures` not require `alloc`. This will require a version bump before being published due to newly requiring the `alloc` feature be specified to maintain pre-existing behavior. Enables resolving https://github.com/monero-oxide/monero-oxide/issues/48.
2025-09-15 21:21:30 -04:00
"schnorr-signatures/alloc",
Differentiate `no-std` from `alloc` within `tests/no-std` Fixes `no-std` builds for packages which intended to be `no-std` (without `alloc`). Updates a variety of MSRVs to 1.73 due to `flexible-transcript` no longer using `std-shims` to achieve 1.66 (as `std-shims` requires `alloc`). A future improvement would be for `std-shims` to have an `alloc` feature and only provide MSRV shims without it.
2025-08-29 01:07:11 -04:00
"prime-field/alloc",
"short-weierstrass/alloc",
"secq256k1/alloc",
"embedwards25519/alloc",
"dkg",
"dkg-evrf",
"bitcoin-serai",
]
Reference in New Issue Copy Permalink