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

economic governance parameters: ranges, risks #653

Closed
dckc opened this issue Mar 29, 2022 · 3 comments
Closed

economic governance parameters: ranges, risks #653

dckc opened this issue Mar 29, 2022 · 3 comments

Comments

@dckc
Copy link
Member

dckc commented Mar 29, 2022

for governance parameters such as MintingRatio, document plausible range of values and risks associated with a setting that is too high or too low.

ref: Agoric/agoric-sdk#4741
see also: Agoric/agoric-sdk#4828

cc @turadg @rowgraus @btulloh @Chris-Hibbert

@Tyrosine22
Copy link
Contributor

I'll tackle this when I tackle Governance in general (#749)

@dckc
Copy link
Member Author

dckc commented Jan 14, 2023

I suppose that's one way to go about it, but note that this is more about risks associated with operation of the Inter Protocol contracts in particular than the governance framework in general.

One option is to close this for the same reason I closed Agoric/agoric-sdk#5046 : the parameters are documented for the community in product docs (by @otoole-brendan and co):

We don't go much into risks of getting the parameters too high or too low there, but those parameters are managed by the Economic Committee; I think they keep some internal documentation of these matters.

If someone else wanted to deploy the Inter Protocol docs, they might appreciate documentation on the risks around setting the minting limit etc. too high or too low. But that's pretty low priority compared to a lot of other documentation.

I wonder if this report says much about economic risks associated with the governance parameters in the Inter Protocol contracts...

no, I don't see much about it.

@dckc
Copy link
Member Author

dckc commented Dec 22, 2023

no longer seems cost-effective to document this here

@dckc dckc closed this as not planned Won't fix, can't repro, duplicate, stale Dec 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants