-
Notifications
You must be signed in to change notification settings - Fork 207
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.
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
build basic transcript-based persistence mechanism #155
Comments
Not yet complete, but good enough to merge. refs #16
Commit ba89426 gets us a Once I write up some of the other options (and their pros/cons/dependencies), I'll close this ticket. This is far from the last word in persistence strategies, but it should be enough for us to experiment with over the next month. |
ok, I think that's good enough for now. |
in the old repo. this was SwingSet issue 16 |
* fix typos in doc and comments * clarify Device architecture` * extraneous whitespace * remove "attenuator", and reduce dupe headers * corrections in review * minor cleanups as part of the review
…ic#155) * feat(zoe): allow specifying additional endowments for contracts This is also added to the contractHost, so that SwingSet users can endow a `require` function for bundled contract code in the `getExport` module format. * doc(zoe): declare that additionalEndowments should be pure-ish Same for contractHost.
I've started with some docs in docs/persistence.md . We don't have engine-level support for checkpointing, but we can plan for it, and in the meantime we "persist" the Vat state by recording a transcript of everything we ask the Vat to do. Since Vats are supposed to be deterministic, replaying the transcript ought to construct an identical state.
The text was updated successfully, but these errors were encountered: