Skip to content
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

Merged
merged 13 commits into from
Apr 26, 2022

Conversation

dckc
Copy link
Member

@dckc dckc commented Apr 25, 2022

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:

  • cfa36cd feat(vats): export AssetTerms type from mintHolder.js
  • 423f67c refactor(run-protocol): move startPSM() to src/psm/startPSM.js
  • 0bce9e3 fix(run-protocol): PSM governance, anchor mintHolder
  • 9e7e729 chore(run-protocol): write 2 proposals: econ-committee, main
  • 16546a9 docs(run-protocol): preview docs, WIP
  • 7dc988f build(run-protocol): deploy-contracts script
  • bc7cd25 build(run-protocol): build:eval:main, deploy:contracts npm scripts
  • 07685b6 build(run-protocol): Makefile for agd tx gov submit-proposal etc.

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:

  • 24f4c78 chore(run-protocol): exclude PSM_MANIFEST from MAIN for now (WIP)
  • 10fe1a7 build(run-protocol): writePsmScript for bootstrap version skew
  • 8ce23d0 build(run-protocol): PSM work-around npm scripts

This is a generated artifact; I kept it checked in so that I could track how it was changing.

  • a1cc82f build(run-protocol): generated gov-startPSM.js script

Security Considerations

Documentation Considerations

Testing Considerations

dckc added 12 commits April 25, 2022 18:19
  - 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
@dckc dckc marked this pull request as ready for review April 25, 2022 23:20
@dckc dckc requested a review from turadg as a code owner April 25, 2022 23:20
Copy link
Member

@michaelfig michaelfig left a 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,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

@turadg turadg left a 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",
Copy link
Member

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?

Copy link
Member Author

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.

@dckc dckc added the automerge:no-update (expert!) Automatically merge without updates label Apr 26, 2022
@mergify mergify bot merged commit 50c130d into master Apr 26, 2022
@mergify mergify bot deleted the dc-psm-gov-workaround branch April 26, 2022 00:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge:no-update (expert!) Automatically merge without updates
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Integrate PSM with bootstrap
3 participants