-
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(vats): facilitate launching additional PSMs #6142
Conversation
How to introduce additional PSMs to the psmCharter?@dtribble @Chris-Hibbert bootstrap wires up "the" PSM to |
00b568b
to
cc6b031
Compare
cc6b031
to
ced7bff
Compare
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 have some questions in the comments.
"economicCommittee": true | ||
}, | ||
"produce": { | ||
"$ISSUE": "These names assume there can be only one psm", |
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.
Are these intended to remain?
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.
no. hence #6142 (comment) and #6146 and such.
ced7bff
to
0492f10
Compare
* refactor: make PSM bootstrap support multiple brands This helps with #6142, but might be merged into that or #6139. * chore(inter-protocol): register PSM under anchor keyword * chore: clean-ups and comments suggested in review. * build(ERTP): increase test timeout to mitigate CI failure Co-authored-by: Dan Connolly <[email protected]> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
876d46a
to
7d903d1
Compare
I think #6146 addressed
|
7d903d1
to
da1785d
Compare
connection to the
|
@Chris-Hibbert and co, PTAL.
There was some wiring up the |
re docs: I can imagine the chainStorage and agoricNames stuff should be documented. for now:
|
da1785d
to
ab6beb8
Compare
@@ -46,7 +49,9 @@ export const start = async (zcf, privateArgs) => { | |||
); | |||
}; | |||
|
|||
const makeOfferFilterInvitation = () => { | |||
/** @param {Instance} instance */ |
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.
@turadg I'm interested to get some training on using Instance
types parameterized by the contract start
function and such.
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.
ab6beb8
to
18f5de1
Compare
oops! I force-pushed after requesting review. I hope I didn't make too much of a mess. |
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.
LGTM
import * as startPSMmod from '@agoric/inter-protocol/src/proposals/startPSM.js'; | ||
import * as ERTPmod from '@agoric/ertp'; |
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.
Capitalization nit: shouldn't these be startPSMMod
and ERTPMod
?
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.
could be. if this version doesn't pass CI, I'll tweak it.
- provide startPSM module to core-eval - support proposedName, decimalPlaces in anchorOptions - check shape of anchorOptions
... in order to avoid importing sim-behaviors.js into boot-psm.js
rather than starting psmCharter with "the" PSM
... which moved to startPSM.js in inter-protocol
1f27602
to
d66e91c
Compare
goal:
closes: #6021
Description
This exposes the
startPSM
andmakeAnchorAsset
functions to the core-eval scope; as a result, a proposal to start a PSM for DAI is just a few lines.TODO:
Security Considerations
TODO:
Documentation Considerations
@rowgraus should we put something about this process in some Inter Protocol docs? Or just wait until it's time to discuss an actual proposal with the community?
Testing Considerations
I did
local-chain
end-to-end integration testing, as noted below