Ecosystem/serai
Ecosystem/serai
1
0
Fork 0
mirror of https://github.com/serai-dex/serai.git synced 2024-12-25 13:09:30 +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.
1877 commits 16 branches 0 tags 36 MiB
Rust 99.9%
Find a file
Luke Parker 8f2a9301cf Don't have the router drop transactions which may have top-level transfers 
The router will now match the top-level transfer so it isn't used as the
justification for the InInstruction it's handling. This allows the theoretical
case where a top-level transfer occurs (to any entity) and an internal call
performs a transfer to Serai.

Also uses a JoinSet for fetching transactions' top-level transfers in the ERC20
crate. This does add a dependency on tokio yet improves performance, and it's
scoped under serai-processor (which is always presumed to be tokio-based).
While we could instead import futures for join_all,
https://github.com/smol-rs/futures-lite/issues/6 summarizes why that wouldn't
be a good idea. While we could prefer async-executor over tokio's JoinSet,
JoinSet doesn't share the same issues as FuturesUnordered. That means our
question is solely if we want the async-executor executor or the tokio
executor, when we've already established the Serai processor is always presumed
to be tokio-based.
2024-09-19 23:36:32 -07:00
.github Smash out the router library 2024-09-19 23:36:32 -07:00
audits Rename the coins folder to networks (#583) 2024-07-18 15:16:45 -04:00
common Misc tidying of serai-db calls 2024-09-19 23:36:32 -07:00
coordinator One Round DKG (#589) 2024-09-19 21:43:26 -04:00
crypto One Round DKG (#589) 2024-09-19 21:43:26 -04:00
docs Remove stray file in docs/ 2024-08-05 06:52:15 -04:00
message-queue serai-processor-bin 2024-09-19 23:36:32 -07:00
mini Add workspace lints 2023-12-17 00:04:47 -05:00
networks Hash the message before the challenge function in the Schnorr contract 2024-09-19 23:36:32 -07:00
orchestration Remove the Sandbox contract 2024-09-19 23:36:32 -07:00
patches cargo update, upgrade alloy 2024-09-05 17:03:23 -04:00
processor Don't have the router drop transactions which may have top-level transfers 2024-09-19 23:36:32 -07:00
spec Correct Multisig Rotation to use WINDOW_LENGTH where proper 2024-09-19 23:36:32 -07:00
substrate Smash out the router library 2024-09-19 23:36:32 -07:00
tests Remove OutInstruction's data field 2024-09-19 23:36:32 -07:00
.gitattributes Correct audit file upload 2023-03-20 17:35:45 -04:00
.gitignore Add validator set rotation test for the node side (#532) 2024-02-24 14:51:06 -05: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 Don't have the router drop transactions which may have top-level transfers 2024-09-19 23:36:32 -07:00
Cargo.toml Smash out the router library 2024-09-19 23:36:32 -07:00
CONTRIBUTING.md Clarify identation policy 2022-10-11 00:40:50 -05:00
deny.toml Smash out the router library 2024-09-19 23:36:32 -07:00
LICENSE Update licenses 2023-01-11 23:05:31 -05:00
README.md Rename the coins folder to networks (#583) 2024-07-18 15:16:45 -04:00
rust-toolchain.toml rust-toolchain 1.81 2024-09-19 23:36:32 -07: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.

  • spec: The specification of the Serai protocol, both internally and as networked.

  • docs: User-facing 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.

  • networks: Various 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