-
Notifications
You must be signed in to change notification settings - Fork 220
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(run-protocol): preview launch support, PSM work-around #5215
Conversation
a1cc82f
to
0c09439
Compare
0c09439
to
907dae1
Compare
along with makeAnchorAsset
- use mintHolder for psm anchor asset to avoid including makeIssuerKit in a core eval script - startPSM: include Electorate in terms - RATIO params
Maintain E(home.scratch).get('installCache') as a CopyMap<Hash, { sha512: string, installation: Installation, path?: string }> Also, save installCache in the board. It turns out that we can't put a copyMap in the board; so we get a boardId for each installation, JSON.stringify the mapping of sha512 to boardId, and put that in the board.
- CHAIN_OPTS for local-chain, agoricstage, ... - shell quoting for description - clean-core-eval no longer needed
- look up PSM installations by hash - eslint-happy output - each install is on the board - merge permits with --permit fixup: declare BASIS_POINTS too fixup: writePsmScript produceIt
generated using: yarn deploy:contracts ... { boardId: 'board04827' } INSTALL_CACHE=board04827 \ ANCHOR_DENOM=ibc/949E954E05CE9E63E072ABD13A7DAAAB338A1E57FFBC148C50D74451AB5067D1 \ yarn build:eval-code:psm yarn build:eval-permit:psm
907dae1
to
3742b1a
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.
LGTM! My only concerns are around what we need to do to reduce technical debt, but that can wait until next devnet.
@@ -74,7 +73,7 @@ export const startEconomicCommittee = async ( | |||
}, | |||
electorateTerms = { | |||
committeeName: 'Initial Economic Committee', | |||
committeeSize: 1, | |||
committeeSize: 3, |
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.
This apparently causes a failure at https://github.com/Agoric/agoric-sdk/runs/6167083776?check_suite_focus=true#step:5:9111
3742b1a
to
6616d86
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.
run-protocol change LGTM
@@ -10,7 +10,10 @@ | |||
"scripts": { | |||
"build": "yarn build:bundles", |
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.
Should this build * like 'lint' does?
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.
perhaps... but some of the build:* things involve blockchain access, so they don't fit the same workflow.
6616d86
to
6f83843
Compare
refs: #5062
closes: #5010
modulo #5218
Description
This is the work necessary to get a clean preview deploy in agoricstage-23.
These are not work-arounds, so they should land:
These are the PSM work-around for version skew with agoricdev-10. Let's land these for the short term; #5218 represents work to clean them up:
This is a generated artifact; I kept it checked in so that I could track how it was changing.
Security Considerations
Documentation Considerations
Testing Considerations