Skip to content
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

4383 durable zoe #5879

Merged
merged 5 commits into from
Aug 9, 2022
Merged

4383 durable zoe #5879

merged 5 commits into from
Aug 9, 2022

Conversation

Chris-Hibbert
Copy link
Contributor

@Chris-Hibbert Chris-Hibbert commented Aug 2, 2022

refs: #4383

Description

First step of making Zoe reachably durable. This covers all of Zoe's global state. Remaining tasks are

  • instance state and instanceAdmin
  • FeeMint
  • zoeMint

I recommend reviewing this by commits. The commits separately update InvitationIssuer, escrow storage, installationStorage, and proposalSchema storage.

Security Considerations

Maintain Zoe invariants

Documentation Considerations

None.

Testing Considerations

Ensure existing tests continue to pass.

@Chris-Hibbert Chris-Hibbert added Zoe package: Zoe force:integration Force integration tests to run on PR MUST-HAVE labels Aug 2, 2022
@Chris-Hibbert Chris-Hibbert added this to the Mainnet 1 milestone Aug 2, 2022
@Chris-Hibbert Chris-Hibbert self-assigned this Aug 2, 2022
Copy link
Member

@erights erights left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

* @param {ShutdownWithFailure | undefined} shutdownZoeVat
*/
export const createInvitationKit = (shutdownZoeVat = undefined) => {
const invitationKit = makeIssuerKit(
export const createInvitationKit = (baggage, shutdownZoeVat = undefined) => {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you think of a naming convention where functions that

  • take a baggage first argument,
  • call a vivifySomething
  • therefore need to be called during the first crank, if they might be revivifying

should themselves be called vivifySomething?

Suggested change
export const createInvitationKit = (baggage, shutdownZoeVat = undefined) => {
export const vivifyInvitationKit = (baggage, shutdownZoeVat = undefined) => {

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sounds like a good rule.

@Chris-Hibbert Chris-Hibbert added the automerge:no-update (expert!) Automatically merge without updates label Aug 9, 2022
@mergify mergify bot merged commit c3daab6 into master Aug 9, 2022
@mergify mergify bot deleted the 4383-durableZoe branch August 9, 2022 01:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge:no-update (expert!) Automatically merge without updates force:integration Force integration tests to run on PR Zoe package: Zoe
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants