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.
Find a file
Luke Parker c182b804bc
Move in instructions from inherent transactions to unsigned transactions
The original intent was to use inherent transactions to prevent needing to vote
on-chain, which would spam the chain with worthless votes. Inherent
transactions, and our Tendermint library, would use the BFT's processs voting
to also vote on all included transactions. This perfectly collapses integrity
voting creating *no additional on-chain costs*.

Unfortunately, this led to issues such as #6, along with questions of validator
scalability when all validators are expencted to participate in consensus (in
order to vote on if the included instructions are valid). This has been
summarized in #241.

With this change, we can remove Tendermint from Substrate. This greatly
decreases our complexity. While I'm unhappy with the amount of time spent on
it, just to reach this conclusion, thankfully tendermint-machine itself is
still usable for #163. This also has reached a tipping point recently as the
polkadot-v0.9.40 branch of substrate changed how syncing works, requiring
further changes to sc-tendermint. These have no value if we're just going to
get rid of it later, due to fundamental design issues, yet I would like to
keep Substrate updated.

This should be followed by moving back to GRANDPA, enabling closing most open
Tendermint issues.

Please note the current in-instructions-pallet does not actually verify the
included signature yet. It's marked TODO, despite this bing critical.
2023-03-26 02:58:04 -04:00
.github Remove the code for the CI to spawn a Serai node 2023-03-20 01:07:43 -04:00
audits/Cypher Stack crypto March 2023 Correct audit file upload 2023-03-20 17:35:45 -04:00
coins Update procesor/correct prior commit 2023-03-25 04:06:25 -04:00
common/zalloc Merge branch 'develop' into crypto-tweaks 2023-03-16 16:43:04 -04:00
crypto cargo fmt 2023-03-20 20:43:52 -04:00
deploy Processor (#259) 2023-03-16 22:59:40 -04:00
docs Move in instructions from inherent transactions to unsigned transactions 2023-03-26 02:58:04 -04:00
processor Update procesor/correct prior commit 2023-03-25 04:06:25 -04:00
substrate Move in instructions from inherent transactions to unsigned transactions 2023-03-26 02:58:04 -04:00
.gitattributes Correct audit file upload 2023-03-20 17:35:45 -04:00
.gitignore fix for #166 & cleanup (#184) 2022-12-07 10:08:04 -05:00
.rustfmt.toml Apply an initial set of rustfmt rules 2022-07-16 15:16:30 -05:00
AGPL-3.0 Add an initial Substrate instantiation 2022-07-15 00:05:00 -04:00
Cargo.lock Move in instructions from inherent transactions to unsigned transactions 2023-03-26 02:58:04 -04:00
Cargo.toml Move in instructions from inherent transactions to unsigned transactions 2023-03-26 02:58:04 -04:00
CONTRIBUTING.md Clarify identation policy 2022-10-11 00:40:50 -05:00
deny.toml Move in instructions from inherent transactions to unsigned transactions 2023-03-26 02:58:04 -04:00
LICENSE Update licenses 2023-01-11 23:05:31 -05:00
README.md Document crypto crates with audit notices 2023-03-16 19:25:01 -04:00

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.

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

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

  • deploy: Scripts to deploy a Serai node/test environment.