mysticeti
mysticeti copied to clipboard
MystenLabs
Mysticeti: Low-Latency DAG Consensus with Fast Commit Path
IIUC from the code, we currently wait for the causal history of a block to be completely synchronized before aggregating votes for transactions and checking if we have a certificate...
Accept transactions from network (needed for benchmarks). This PR does not change the default behaviour of tests and simulations (in which cases transactions are still locally generated).
When epoch changes, we stop casting our own votes and proposing transactions. But currently, we still process others' votes (these votes will appear in our blocks' causal history) -- namely,...
It would be nice to have small benchmarks for network and storage to ensure they are not the bottleneck.
- [x] Adapt the orchestrator to Mysticeti - [x] Add metrics throughout the codebase - [x] Ensure sample runs work on geo-replicated testbeds (but without clients) - [ ] Add...
Mysticeti persistence - [x] Write blocks to wal - [x] Wal iterator - [x] Read wal in block store on startup - [x] Other wal operations for core, proper recovery...
We seem to issue requests to AWS sequentially, and it actually takes a bit of time even on 10 node cluster, probably going to be unusable on 100 nodes. We...
`Core::signer` and `Committee::authorities` are currently populated with a dummy keypair even for production. We want to generate unique keys and pass it to committee/core
See comments on PR https://github.com/MystenLabs/project-mysticeti/pull/4#issuecomment-1622652332
Metadata
Owner
Metadata
Mysticeti: Low-Latency DAG Consensus with Fast Commit Path