-
Notifications
You must be signed in to change notification settings - Fork 208
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
reinstantiate PSM with state from chainStorage #6645
Comments
We figured that out Dec 7: How to mint USDC for PSM reboot? |
take care not to re-do the minting! reading from chainStorage conflicts with an architectural goal of not reading from devices, which [somehow?] facilitates parallelism. So more likely: we'll grab all the pre-bulldozer chainStorage state and feed it to the post-bulldozer bootstrap vat in maybe mintHolder for USDC_axl isn't such a good idea... zcfMint? re-adding all the PSM denoms will result in the same IAVL state, modulo board IDs. not double denoms
|
fixes: #6645 - compute total fees - style: keep to jessie-check in startPSM - use vatPowers.chainStorageEntries in restorePSM
fixes: #6645 - compute total fees - style: keep to jessie-check in startPSM - use vatPowers.chainStorageEntries in restorePSM
fixes: #6645 - compute total fees - style: keep to jessie-check in startPSM - use vatPowers.chainStorageEntries in restorePSM
…ished state (#7480) * feat(psm): creatorFacet.makeRestoreMetricsInvitation * feat: restore PSM state from former VM vstorage contents fixes: #6645 - compute total fees - style: keep to jessie-check in startPSM - use vatPowers.chainStorageEntries in restorePSM * chore: never mind mintPSMFees mint the fees within the PSM contract * refactor: move makeHistoryReviver etc. to board-utils.js * chore: findOldPSMState matches published governance shape * fixup! refactor: move makeHistoryReviver etc. to board-utils.js * refactor: factor out common published.psm.IST prefix * refactor: length check before startsWith is superfluous * fixup! refactor: move makeHistoryReviver etc. to board-utils.js * refactor: move ChainStorageVatParams with other swingset types * test: move makeHistoryReviver test; move data to fixture module * refactor: use atomicTransfer * refactor: clean up shapes * refactor: default chainStorageEntries to [] earlier * fixup: prune stray comment * chore: prune redundant CONTRACT_ELECTORATE * docs: explain override of governedParams * refactor: use .name property of startPSM * test: clean up installs.psm --------- Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
What is the Problem Being Solved?
We plan to restart the JS VM from scratch (#6644). The PSM contracts need to be restored, including the anchor assets, fee pool, and governed parameters
Description of the Design
Tasks
Security Considerations
The PSM contract should not have the capability to mint the anchor balance and the fee pool balance after start-up. Perhaps a separate contract or bootstrap function should do the minting and provide the assets to the PSM contract.
Test Plan
Integration with chain will be tested in #7491
cc @turadg @Chris-Hibbert @ivanlei
The text was updated successfully, but these errors were encountered: