-
Notifications
You must be signed in to change notification settings - Fork 225
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
Isolate BLD issuer / mint in its own contract vat #4578
Labels
Milestone
Comments
Huzzah! I like this idea. |
This was referenced Feb 18, 2022
dckc
added a commit
that referenced
this issue
Mar 5, 2022
1 task
dckc
added a commit
that referenced
this issue
Mar 5, 2022
dckc
added a commit
that referenced
this issue
Mar 5, 2022
dckc
added a commit
that referenced
this issue
Mar 6, 2022
dckc
added a commit
that referenced
this issue
Mar 6, 2022
dckc
added a commit
that referenced
this issue
Mar 6, 2022
dckc
added a commit
that referenced
this issue
Mar 6, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the Problem Being Solved?
The BLD issuer kit is created in the bootstrap vat, which means that the mint, issuer, and all the purses are there too. The bootstrap vat gets access to extremely high authority objects; it should only partition access to those object among other components. Running the BLD mint in the same vat is awkward w.r.t. POLA.
Description of the Design
Create a new contract whose only job is to create an IssuerKit. In fact, the
mint
could be thecreatorFacet
and the issuer could be thepublicFacet
.Security Considerations
See problem description above.
Test Plan
It's not clear that this should result in any observable differences, so basic unit tests for the new contract, plus all the existing tests, seem to suffice.
cc @dtribble @Chris-Hibbert
The text was updated successfully, but these errors were encountered: