2024-04-24 09:25:11 -04:00
|
|
|
use std::path::Path;
|
2024-02-09 02:48:44 -05:00
|
|
|
|
2024-03-22 16:06:56 -04:00
|
|
|
use zeroize::Zeroizing;
|
2025-08-20 04:50:37 -04:00
|
|
|
use dalek_ff_group::Ristretto;
|
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
|
|
|
use ciphersuite::{group::ff::PrimeField, WrappedGroup};
|
2024-03-22 16:06:56 -04:00
|
|
|
|
2024-02-09 02:48:44 -05:00
|
|
|
use crate::{Network, Os, mimalloc, os, build_serai_service, write_dockerfile};
|
|
|
|
|
|
2024-03-22 16:06:56 -04:00
|
|
|
pub fn serai(
|
|
|
|
|
orchestration_path: &Path,
|
|
|
|
|
network: Network,
|
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
|
|
|
serai_key: &Zeroizing<<Ristretto as WrappedGroup>::F>,
|
2024-03-22 16:06:56 -04:00
|
|
|
) {
|
2024-02-09 02:48:44 -05:00
|
|
|
// Always builds in release for performance reasons
|
2024-05-21 00:29:33 -04:00
|
|
|
let setup = mimalloc(Os::Debian).to_string() + &build_serai_service("", true, "", "serai-node");
|
2024-02-24 22:51:06 +03:00
|
|
|
let setup_fast_epoch =
|
2024-05-21 00:29:33 -04:00
|
|
|
mimalloc(Os::Debian).to_string() + &build_serai_service("", true, "fast-epoch", "serai-node");
|
2024-02-09 02:48:44 -05:00
|
|
|
|
2024-03-22 16:06:56 -04:00
|
|
|
let env_vars = [("KEY", hex::encode(serai_key.to_repr()))];
|
|
|
|
|
let mut env_vars_str = String::new();
|
|
|
|
|
for (env_var, value) in env_vars {
|
2024-03-22 17:11:44 -04:00
|
|
|
env_vars_str += &format!(r#"{env_var}=${{{env_var}:="{value}"}} "#);
|
2024-03-22 16:06:56 -04:00
|
|
|
}
|
|
|
|
|
|
2024-02-09 02:48:44 -05:00
|
|
|
let run_serai = format!(
|
|
|
|
|
r#"
|
|
|
|
|
# Copy the Serai binary and relevant license
|
|
|
|
|
COPY --from=builder --chown=serai /serai/bin/serai-node /bin/
|
|
|
|
|
COPY --from=builder --chown=serai /serai/AGPL-3.0 .
|
|
|
|
|
|
|
|
|
|
# Run the Serai node
|
2024-03-22 16:06:56 -04:00
|
|
|
EXPOSE 30333 9944
|
2024-02-09 02:48:44 -05:00
|
|
|
|
|
|
|
|
ADD /orchestration/{}/serai/run.sh /
|
2024-03-22 16:06:56 -04:00
|
|
|
CMD {env_vars_str} "/run.sh"
|
2024-02-09 02:48:44 -05:00
|
|
|
"#,
|
2024-03-22 02:19:09 -04:00
|
|
|
network.label(),
|
2024-02-09 02:48:44 -05:00
|
|
|
);
|
|
|
|
|
|
|
|
|
|
let run = os(Os::Debian, "", "serai") + &run_serai;
|
|
|
|
|
let res = setup + &run;
|
2024-02-24 22:51:06 +03:00
|
|
|
let res_fast_epoch = setup_fast_epoch + &run;
|
2024-02-09 02:48:44 -05:00
|
|
|
|
|
|
|
|
let mut serai_path = orchestration_path.to_path_buf();
|
|
|
|
|
serai_path.push("serai");
|
2024-02-24 22:51:06 +03:00
|
|
|
|
|
|
|
|
let mut serai_fast_epoch_path = serai_path.clone();
|
|
|
|
|
|
2024-02-09 02:48:44 -05:00
|
|
|
serai_path.push("Dockerfile");
|
2024-02-24 22:51:06 +03:00
|
|
|
serai_fast_epoch_path.push("Dockerfile.fast-epoch");
|
2024-02-09 02:48:44 -05:00
|
|
|
|
|
|
|
|
write_dockerfile(serai_path, &res);
|
2024-02-24 22:51:06 +03:00
|
|
|
write_dockerfile(serai_fast_epoch_path, &res_fast_epoch);
|
2024-02-09 02:48:44 -05:00
|
|
|
}
|