-
Notifications
You must be signed in to change notification settings - Fork 217
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): collect runStake fees #5197
Conversation
4d425ad
to
c9f8eef
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
Co-authored-by: Chris Hibbert <[email protected]>
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 defer to @Chris-Hibbert ; I'm fuzzy on makeGovernorFacet(creatorFacet)
return { publicFacet, creatorFacet }; | ||
return { publicFacet, creatorFacet: makeGovernorFacet(creatorFacet) }; |
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.
Does this mean runStake governance was previously busted? Did we not have any tests for it?
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 just moved the makeGovernorFacet
down here to make more obvious that there are two slightly different things named creatorFacet
.
Darn; I think the permit for that needs tweaking: modified packages/run-protocol/src/core-proposal.js
@@ -137,6 +137,7 @@ const REWARD_MANIFEST = harden({
loadVat: true,
vaultFactoryCreator: true,
ammCreatorFacet: true,
+ // TODO: runStake
zoe: true,
},
produce: {
|
Description
makeCollectFeesInvitation
to RunStake's creatorstartRewardDistributor
Security Considerations
RunStake creator facet exposes a way to collect its fees
fixes: #5004
Documentation Considerations
--
Testing Considerations
Relying on types. Open to requests for additional coverage.