New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Research / related and prior works. #1

Open

liamzebedee opened this issue May 16, 2022 · 1 comment

Owner

liamzebedee commented May 16, 2022 •

edited

https://signalsandthreads.com/state-machine-replication-and-why-you-should-care/

Jane St runs a distributed state machine.

Messages come in from all sorts of different data sources.
Sequencer produces a canonical order.
After which message is disseminated to node for execution/processing.
Programs have rudimentary ABI interface that Jane St calls message types (lol).
State sharing is interesting.
Their sequencer doesn't multicast all messages. Execution nodes subscribe to particular topics - reduce network bandwidth. Publish-subscribe model

liamzebedee changed the title ~~Notes.~~ Research / related and prior works.

Owner Author

liamzebedee commented May 30, 2022

Flow: Separating Consensus and Compute – Execution Verification – https://arxiv.org/pdf/1909.05832.pdf
Subspace (interesting but not really relevant)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment