* Add dkg crate
* Remove F_len and G_len
They're generally no longer used.
* Replace hash_to_vec with a provided method around associated type H: Digest
Part of trying to minimize this trait so it can be moved elsewhere. Vec,
which isn't std, may have been a blocker.
* Encrypt secret shares within the FROST library
Reduces requirements on callers in order to be correct.
* Update usage of Zeroize within FROST
* Inline functions in key_gen
There was no reason to have them separated as they were. sign probably
has the same statement available, yet that isn't the focus right now.
* Add a ciphersuite package which provides hash_to_F
* Set the Ciphersuite version to something valid
* Have ed448 export Scalar/FieldElement/Point at the top level
* Move FROST over to Ciphersuite
* Correct usage of ff in ciphersuite
* Correct documentation handling
* Move Schnorr signatures to their own crate
* Remove unused feature from schnorr
* Fix Schnorr tests
* Split DKG into a separate crate
* Add serialize to Commitments and SecretShare
Helper for buf = vec![]; .write(buf).unwrap(); buf
* Move FROST over to the new dkg crate
* Update Monero lib to latest FROST
* Correct ethereum's usage of features
* Add serialize to GeneratorProof
* Add serialize helper function to FROST
* Rename AddendumSerialize to WriteAddendum
* Update processor
* Slight fix to processor
* Create message types for FROST key gen
Taking in reader borrows absolutely wasn't feasible. Now, proper types
which can be read (and then passed directly, without a mutable borrow)
exist for key_gen. sign coming next.
* Move FROST signing to messages, not Readers/Writers/Vec<u8>
Also takes the nonce handling code and makes a dedicated file for it,
aiming to resolve complex types and make the code more legible by
replacing its previously inlined state.
* clippy
* Update FROST tests
* read_signature_share
* Update the Monero library to the new FROST packages
* Update processor to latest FROST
* Tweaks to terminology and documentation
Unbeknowst to me, height doesn't have a universal definition of the
chain length.
Bitcoin defines height as the block number, with getblockcount existing
for the chain length.
Ethereum uses the unambiguous term "block number".
Monero defines height as both the block number and the chain length.
Instead of arguing about who's right, it's agreed it referring to both
isn't productive. While we could provide our own definition, taking a
side, moving to the unambiguous block number prevents future hiccups.
height is now only a term in the Monero code, where it takes its
Monero-specific definition, as documented in the processor.
Ensures random functions never return zero. This, combined with a check
commitments aren't 0, causes no serialized elements to be 0.
Also directly reads their vectors.
* add file
* builds + caching fixed
* bitcoin orchestration
* remove default entrypoint
* eth image and cleanup
* working monero
* remove signature file
* cleanup on aisle eth
* cleanup on aisle btc
* eth working
* remove docker ignore
* remove bitcoin image readme
* fix serai builds
* serai clusters
* added readme for docker
* formatting
* share the image
* newlines at EOF
* add multi profile example
* coin order
* coin order
* profile order
* fix grammar
* fix whitespace
* reduce trusted signature set, require at least 3 signatures.
* remove echo
* update comment to ref trusted keys
* comment fix
* use 16 keys, check for laanwj, name compose
* don't use bash
* monero fingerprints & eth fixes
* eth fixes
* remove extra eth keys
* kubernetes deployment implemented with helm charts
* deleted helmignores & added new lines at the end of the file
* deleted duplications & delete unnecessary comments & deactivated service accounts
* deleted generators files
* added a new line to monero/values.yaml
* deleted support for old kubernetes version - ingress.yaml
* added new like to serai/values.yaml
* serai's port name changed
* serai's port name changed
* release name limit was changed to 253
* README.md updated
* fixed Makefile
* deleted platform dependant instructions
* deleted appVersion from .yamls
* added -i parameter for deleting process
* added \ for Makefile
Co-authored-by: TheArchitect108 <75815740+TheArchitect108@users.noreply.github.com>
Co-authored-by: TheArchitect <TheArchitect108@protonmail.com>
* Update to the latest Serai Substrate
* Add Protobuf to build dependencies
Docker shouldn't need updating as this should've been added to the image
in
2dbace5b01.
* Get substrate to build
* Correct protoc build step
* Remove the benchmarking code
There's some macro resolution error that isn't apparent. I worked on it
for about half an hour but...
* Remove unnecessary clone
* Correct runtime-benchmarks flag usage
Apparently, GitHub doesn't write back to the cache, leading to massive
build times a few moments after its initialization (when a change
happens invalidating it). While this forces a new cache whenever
dependencies change, it'll restore from an older set of dependencies in
that case, still minimizing build times.
