It cached signatures per-block. Precommit signatures are bound to each round. This would lead to forming invalid commits when a commit should be formed. Under debug, the machine would catch that and panic. On release, it'd have everyone who wasn't a validator fail to continue syncing. |
||
---|---|---|
.github | ||
coins | ||
common/zalloc | ||
contracts | ||
crypto | ||
deploy | ||
docs | ||
processor | ||
substrate | ||
.gitattributes | ||
.gitignore | ||
.rustfmt.toml | ||
AGPL-3.0 | ||
Cargo.lock | ||
Cargo.toml | ||
CONTRIBUTING.md | ||
LICENSE | ||
README.md |
Serai
Serai is a new DEX, built from the ground up, initially planning on listing Bitcoin, Ethereum, Monero, DAI, and USDC, offering a liquidity pool trading experience. Funds are stored in an economically secured threshold multisig wallet.
Layout
-
docs
: Documentation on the Serai protocol. -
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. -
processor
: A generic chain processor to process data for Serai and process events from Serai, executing transactions as expected and needed. -
contracts
: Smart Contracts implementing Serai's functionality. -
substrate
: Substrate crates used to instantiate the Serai network.