-
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
feat: separate vaults launch from platform #7563
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A first pass. The testing plan LGTM. Might break loadgen? if so you might want to force integration after getting this synced again with master
if (e.code !== 'ENOENT') { | ||
throw e; | ||
} | ||
// FIXME: We could take a hard dependency on `tmp` here, but is it worth it? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably not worth the NPM dependency but we do have Node and could use mkdtemp
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that file isn't actually in this PR; it's an artifact of stacking this on mfig-cli-run-no-solo
@@ -355,7 +355,7 @@ export const startRewardDistributor = async ({ | |||
bankManager, | |||
vaultFactoryKit, | |||
periodicFeeCollectors, | |||
stakeFactoryKit, | |||
// stakeFactoryKit, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
simply delete for now
/** | ||
* Introduce charter to governed creator facets. | ||
* | ||
* XXX make this the responsibility of startVaultFactory, startReserve, etc.? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think so. why not?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just time.
return { permit, script, bundles }; | ||
}; | ||
|
||
test.serial('make vaults launch proposal', async t => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yay bootstrap test!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good so far!
@@ -171,13 +171,13 @@ export const makeBootstrap = ( | |||
const { root } = vat; | |||
const decodedArgs = args.map(decodePassable); | |||
const result = await E(root)[methodName](...decodedArgs); | |||
return encodePassable(result); | |||
return encodePassable(harden(result)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch!
usually among installations
sort of papers over lack of harden() around some start results and lack of good stack traces to figure out which one
redundant with another branch?
In packages/vats, run: yarn test test/bootstrapTests/test-inter-launch.js
other cleanup
Updated the PR with some cleanups around proposal builder, installing the ATOM collateral, measuring per crank computrons. All tests pass, but the PR still needs some rebasing / fixups as I mostly kept the original WIP commits. |
@mhofman thanks for polishing this up, but as noted in #5819 (comment) , this is no longer the plan. If you added anything along the way that should be kept, please put it in another PR. |
closes: #5819 (or at least: refs)
The code still needs some rebasing / fixup, but I works.
@warner do you want to review this? feel free to take yourself out of the list.
Description
remove vaults proposal from devnet bootstrap config
take governance committee, oracles, out of vaults proposal
take stakeFactory out of vaults proposal
add initial collateral type
prune dead code from
packages/inter-protocol/scripts/init-core.js
,packages/inter-protocol/src/proposals/core-proposal.js
review install Inter protocol defi contracts after boostrap using publishBundle #5819 etc. for configuration details to take care of
Security Considerations
nothing new, I don't think
Scaling Considerations
Documentation Considerations
The proposal to launch vaults should come with a community discussion post.
See also
Testing Considerations
TODO: