Ecosystem/serai
Ecosystem/serai
1
0
Fork 0
mirror of https://github.com/serai-dex/serai.git synced 2025-01-22 02:34:55 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
Serai is a new DEX, built from the ground up, initially planning on listing Bitcoin, Ethereum, DAI, and Monero, offering a liquidity-pool-based trading experience. Funds are stored in an economically secured threshold-multisig wallet.
1306 commits 18 branches 0 tags 39 MiB
Rust 99.9%
Find a file
Luke Parker e05b77d830
Support multiple key shares per validator (#416) 
* Update the coordinator to give key shares based on weight, not based on existence

Participants are now identified by their starting index. While this compiles,
the following is unimplemented:

1) A conversion for DKG `i` values. It assumes the threshold `i` values used
will be identical for the MuSig signature used to confirm the DKG.
2) Expansion from compressed values to full values before forwarding to the
processor.

* Add a fn to the DkgConfirmer to convert `i` values as needed

Also removes TODOs regarding Serai ensuring validator key uniqueness +
validity. The current infra achieves both.

* Have the Tributary DB track participation by shares, not by count

* Prevent a node from obtaining 34% of the maximum amount of key shares

This is actually mainly intended to set a bound on message sizes in the
coordinator. Message sizes are amplified by the amount of key shares held, so
setting an upper bound on said amount lets it determine constants. While that
upper bound could be 150, that'd be unreasonable and increase the potential for
DoS attacks.

* Correct the mechanism to detect if sufficient accumulation has occured

It used to check if the latest accumulation hit the required threshold. Now,
accumulations may jump past the required threshold. The required mechanism is
to check the threshold wasn't prior met and is now met.

* Finish updating the coordinator to handle a multiple key share per validator environment

* Adjust stategy re: preventing noce reuse in DKG Confirmer

* Add TODOs regarding dropped transactions, add possible TODO fix

* Update tests/coordinator

This doesn't add new multi-key-share tests, it solely updates the existing
single key-share tests to compile and run, with the necessary fixes to the
coordinator.

* Update processor key_gen to handle generating multiple key shares at once

* Update SubstrateSigner

* Update signer, clippy

* Update processor tests

* Update processor docker tests
2023-11-04 19:26:13 -04:00
.github November 2023 - Rust Nightly Update (#413) 2023-11-03 05:28:07 -04:00
audits Add coins/bitcoin audit by Cypher Stack 2023-08-21 01:20:09 -04:00
coins Replace crc dependency with our own crc implementation 2023-11-03 06:44:23 -04:00
common Correct std feature-flagging 2023-10-31 07:44:02 -04:00
coordinator Support multiple key shares per validator (#416) 2023-11-04 19:26:13 -04:00
crypto November 2023 - Rust Nightly Update (#413) 2023-11-03 05:28:07 -04:00
docs Implement a fee on every input to prevent prior described economic attacks 2023-10-22 21:31:13 -04:00
message-queue Correct std feature-flagging 2023-10-31 07:44:02 -04:00
mini Add support for multiple multisigs to the processor (#377) 2023-09-25 09:48:15 -04:00
orchestration Add ca-certificates to processor Docker image 2023-10-28 04:06:00 -04:00
processor Support multiple key shares per validator (#416) 2023-11-04 19:26:13 -04:00
substrate Support multiple key shares per validator (#416) 2023-11-04 19:26:13 -04:00
tests Support multiple key shares per validator (#416) 2023-11-04 19:26:13 -04:00
.gitattributes Correct audit file upload 2023-03-20 17:35:45 -04:00
.gitignore E2E test coordinator KeyGen 2023-08-14 06:54:17 -04:00
.rustfmt.toml .rustmfmt.toml: add edition 2023-07-20 15:28:03 -04:00
AGPL-3.0 Add an initial Substrate instantiation 2022-07-15 00:05:00 -04:00
Cargo.lock Replace crc dependency with our own crc implementation 2023-11-03 06:44:23 -04:00
Cargo.toml Remove the staking pallet for validator-sets alone 2023-10-22 04:00:42 -04:00
CONTRIBUTING.md Clarify identation policy 2022-10-11 00:40:50 -05:00
deny.toml Remove the staking pallet for validator-sets alone 2023-10-22 04:00:42 -04:00
LICENSE Update licenses 2023-01-11 23:05:31 -05:00
README.md README.md: Add links to Reddit, Telegram and Website 2023-10-07 13:32:52 -04:00

README.md

Serai

Serai is a new DEX, built from the ground up, initially planning on listing Bitcoin, Ethereum, DAI, and Monero, offering a liquidity-pool-based trading experience. Funds are stored in an economically secured threshold-multisig wallet.

Getting Started

Layout

  • audits: Audits for various parts of Serai.

  • docs: Documentation on the Serai protocol.

  • common: Crates containing utilities common to a variety of areas under Serai, none neatly fitting under another category.

  • crypto: A series of composable cryptographic libraries built around the ff/group APIs, achieving a variety of tasks. These range from generic infrastructure, to our IETF-compliant FROST implementation, to a DLEq proof as needed for Bitcoin-Monero atomic swaps.

  • coins: Various coin libraries intended for usage in Serai yet also by the wider community. This means they will always support the functionality Serai needs, yet won't disadvantage other use cases when possible.

  • message-queue: An ordered message server so services can talk to each other, even when the other is offline.

  • processor: A generic chain processor to process data for Serai and process events from Serai, executing transactions as expected and needed.

  • coordinator: A service to manage processors and communicate over a P2P network with other validators.

  • substrate: Substrate crates used to instantiate the Serai network.

  • orchestration: Dockerfiles and scripts to deploy a Serai node/test environment.

  • tests: Tests for various crates. Generally, crate/src/tests is used, or crate/tests, yet any tests requiring crates' binaries are placed here.

Security

Serai hosts a bug bounty program via Immunefi. For in-scope critical vulnerabilities, we will reward whitehats with up to $30,000.

Anything not in-scope should still be submitted through Immunefi, with rewards issued at the discretion of the Immunefi program managers.

Links