-
Notifications
You must be signed in to change notification settings - Fork 206
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
Add hash bundle support to Zoe install
#4974
Labels
enhancement
New feature or request
Comments
kriskowal
added a commit
that referenced
this issue
Mar 31, 2022
kriskowal
added a commit
that referenced
this issue
Apr 21, 2022
kriskowal
added a commit
that referenced
this issue
Apr 22, 2022
kriskowal
added a commit
that referenced
this issue
Apr 28, 2022
kriskowal
added a commit
that referenced
this issue
Apr 28, 2022
kriskowal
added a commit
that referenced
this issue
Apr 28, 2022
kriskowal
added a commit
that referenced
this issue
May 2, 2022
kriskowal
added a commit
that referenced
this issue
May 2, 2022
kriskowal
added a commit
that referenced
this issue
May 3, 2022
kriskowal
added a commit
that referenced
this issue
May 3, 2022
kriskowal
added a commit
that referenced
this issue
May 25, 2022
kriskowal
added a commit
that referenced
this issue
May 25, 2022
kriskowal
added a commit
that referenced
this issue
May 25, 2022
kriskowal
added a commit
that referenced
this issue
May 25, 2022
kriskowal
added a commit
that referenced
this issue
May 26, 2022
kriskowal
added a commit
that referenced
this issue
May 27, 2022
Solved in #4975 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the Problem Being Solved?
Zoe currently accepts bundles that contain all of their source, resulting in very large transactions to the chain. Per #4563, we added a new installation method to Zoe,
installBundleID
that allows a bundle to be published to the SwingSet controller without a chain transaction and then install it in Zoe using its “identifier” (tagged consistent hash).@michaelfig observes that
install
is already sufficiently generic to support an evolving bundle payload type. @dckc observes that this change also avalanches through our documentation #4565 (comment).Description of the Design
So, instead, the plan is to consolidate the behavior of
installBundleID
intoinstall
and instead introduce a new “hash bundle” type that would be accepted byinstall
in addition to “source bundles”, and eventually instead of source bundles #4565.Security Considerations
Test Plan
The text was updated successfully, but these errors were encountered: