prepare updates for Upgrade 15

[Chris-Hibbert]

What is the Problem Being Solved?

A plan for the userland updates for Upgrade 15

Steps (in order)

1. Zoe

• Make a branch with refactor ZoeSeat to drop cyclic structure that blocked GC #8682, feat: when zcfSeats exit or fail, delete objects holding cycles #8697, refactor(ertp): reallyPrepareIssuerKit #8497, feat(ertp): upgraded quotes incrementally empty recovery-sets #8498
• write the core eval Write a Zoe coreEval proposal for upgrade-16 #8915
• test refactor ZoeSeat to drop cyclic structure that blocked GC #8682 in A3P. [8672 acyclic zoe seat kit test #9010)
• test fix: When setting a new zcfBundleCap, store it in baggage #8807 in A3P [A3p test zcf bundle cap #8911]

2. Price Feeds. (see Plan for replacing priceFeeds, redirecting oracles #8740)

• Add refactor(ertp): reallyPrepareIssuerKit #8497 to branch
• replace feat(ertp): upgraded quotes incrementally empty recovery-sets #8498 with something that doesn't clean incrementally (Make Recovery sets optional #9013)
• add upgrading price feeds to core eval, see Plan for replacing priceFeeds, redirecting oracles #8740. (see a3p proposal to create new priceFeeds #9044)
• test price feeds in A3P

3. Auction

• add feat: auctioneer detects failing priceAuthority; requests new one #8691, feat: catch all exceptions in auction wakers #8438, fix: Make the auction schedule robust when adding collateral types #8301 to the branch
• add starting a new auction to the core eval. (Write a coreEval to add a new Auction #8918)

4. Vaults

• add Vaults detects failing priceAuthority and requests new one #8696, WIP: in VaultFactory, move auctioneer public facet from terms to private args #8049, Upgrade VaultFactory in A3P, and use new auctions and price feeds #8757 to the branch
• add upgrading Vaults to the core eval
• verify that upgrade succeeds (vaultFactory contract not upgradable #8079)
• test test that walletFactory upgrade continue tracking existing offers #8788, test that smartWallet offer notifications survive Zoe upgrade #8789, smartWallet stops updating purse balance on upgrade #8293 in A3P

We decided (2/12) to upgrade from master rather than a branch, so it's not necessary to make branches. We still need the coreEvals.

[Chris-Hibbert]

@turadg pointed out the seat created in upgrade-10 should still be live, and can be inspected to verify that the seat was fixed by 8682

[dckc]

I don't see #8123 in this plan. Is that on purpose?

@anilhelvaci Anil is doing some work on vault stuff and noticed that vaults do, in fact, lose the state of their governed parameters on upgrade.

[Chris-Hibbert]

I don't see #8123 in this plan. Is that on purpose?

Yes.
It was never included in lists of goals that I saw. AIR, We explicitly decided to deal with the consequences of non-persistent governance.

[dckc]

We decided (2/12) to upgrade from master rather than a branch ...

That's now reified as:

• build SDK releases from master #9252

perhaps that should go in the task list here?

[Chris-Hibbert]

Last I heard, we were not planning to do any of the actually planned upgrades from master, but getting there is somewhere between a goal and a pious hope. I'm pretty sure something called upgrade 15 will go out without being pulled direct from master.

I think the things on this list are closer to upgrade 17 at this point, and so it's possible we'll include @9252, but I wouldn't consider it gating.