This is read from the BABE pre-digest when converting from a SubstrateHeader. This causes the genesis block to have time 0 and all blocks produced with BABE to have a time of the slot time. While the slot time is in 6-second intervals (due to our target block time), defining in milliseconds preserves the ABI for long-term goals (sub-second blocks). Usage of the slot time deduplicates this field with BABE, and leaves the only possible manipulation to propose during a slot or to not propose during a slot. The actual reason this was implemented this way is because the Header trait is overly restrictive and doesn't allow definition with new fields. Even if we wanted to express the timestamp within the SubstrateHeader, we can't without replacing Header::new and making a variety of changes to the polkadot-sdk accordingly. Those aren't worth it at this moment compared to the solution implemented.
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. -
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 theff/groupAPIs, 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/testsis 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.