-
Notifications
You must be signed in to change notification settings - Fork 219
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
production bootstrap vat includes sim-chain tools such as connectFaucet #6687
Comments
in discussion of reserve module account with @rowgraus , we were reminded that the whole dance between the AMM, reserve, and vaults needs to have the AMM part cut out. |
#6641 includes bootstrap work to make vaults and liquidation work without an AMM. I'm inclined to stand by until we see how that goes before resuming work on this. |
perhaps it belongs in a follow-up to... analagous to... Filed as |
basic-behaviors.js included a function named `mintInitialSupply()`, which (if run) would create the `centralSupply` vat, which can create an initial supply of IST tokens. We obviously don't enable this in the production config, but several unit tests and testnet configs need it, as those environments have no other source of tokens. To assist with auditing, this commit removes `mintInitialSupply` from the basic behaviors entirely, so the code won't even be present in production. The code was moved to `demoIssuers.js`, which is used by `sim-behaviors.js`, which is in turn used by the sim-chain and a few tests. refs #6687
|
What is the Problem Being Solved?
For pismoA, we used boot-psm.js to avoid some complexity from manifest-driven bootstrap actions. In order to support launching the vaults contracts after bootstrap (#4165), we harmonised it with boot-psm.js (#6568). But in doing so, we regressed w.r.t. #4165, by re-introducing
SIM_CHAIN_BOOTSTRAP_MANIFEST
includingconnectFaucet
into the production bootstrap vat. These testing tools should not be in the production bootstrap vat.A noteable exception is mailbox access (#5965), where we plan to control access not by leaving the code out altogether but by not issuing any of the
provisionpass
tokens required to exercise it.Description of the Design
Tasks
Goals:
demoIssuers.js
in favor of some coreProposalssee also
Security Considerations
Auditors shouldn't even have to consider
connectFaucet
when reviewing the production bootstrap.Test Plan
IOU
The text was updated successfully, but these errors were encountered: