8b26a85faa
The rational is detailed in the root Cargo.toml. While I don't personally mind MPL dependencies, even if I don't prefer them (they're allowed in the deny.toml for a reason), I do mind the pointless scope creep and wish to highlight how little it actually used from the crate by re-defining it as the single function. We could also fork directories-next, or directories, and remove the usage of option-ext per https://github.com/dirs-dev/dirs-sys-rs/issues/24, yet that'd be a much larger task than what was done here. In the future, it may be beneficial to submit a PR to wasmtime replacing directories-next with home, a cargo-team maintained library to get the home directory and associated folders. An example migration can be found at https://github.com/harryfei/which-rs/pull/80. |
||
---|---|---|
.github | ||
audits | ||
coins | ||
common | ||
coordinator | ||
crypto | ||
docs | ||
message-queue | ||
mini | ||
orchestration | ||
patches | ||
processor | ||
substrate | ||
tests | ||
.gitattributes | ||
.gitignore | ||
.rustfmt.toml | ||
AGPL-3.0 | ||
Cargo.lock | ||
Cargo.toml | ||
CONTRIBUTING.md | ||
deny.toml | ||
LICENSE | ||
README.md | ||
rust-toolchain.toml |
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.
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 theff
/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, orcrate/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
- Website: https://serai.exchange/
- Immunefi: https://immunefi.com/bounty/serai/
- Twitter: https://twitter.com/SeraiDEX
- Mastodon: https://cryptodon.lol/@serai
- Discord: https://discord.gg/mpEUtJR3vz
- Matrix: https://matrix.to/#/#serai:matrix.org
- Reddit: https://www.reddit.com/r/SeraiDEX/
- Telegram: https://t.me/SeraiDEX