-
Notifications
You must be signed in to change notification settings - Fork 405
Add governance proposal #4
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
Conversation
HIP001.md
Outdated
# Motivation | ||
[motivation]: #motivation | ||
|
||
We must decide on a mechanism for the on-going governance of the blockchain network. For clarities sake, _governance_ refers to changes to consensnus breaking rules. These could be changes to the minting schedule, mining reward distribution, or the number of consensus members required. |
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.
typos: For clarities sake
, consensnus
|
||
### Voting | ||
|
||
Voting should take place on-chain, not through an out of band mechanism. Any _stakeholder_ should be able to create and sign a _voting transaction_ at any time which proposes which chain variable to change and to what new value. |
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.
could a single voting transaction propose changing multiple variables at once? there are some variables currently that would only make sense to be changed together (percent distribution variables for example). Though maybe we should change that to be a single variable whose value is a map/tuple of sorts
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 don't see why not, although I am not that familiar with how the chain variables work at a technical level. Ideally variables that require grouping like this could be consolidated into a single variable to reduce any risk of error.
|
||
Voting should take place on-chain, not through an out of band mechanism. Any _stakeholder_ should be able to create and sign a _voting transaction_ at any time which proposes which chain variable to change and to what new value. | ||
|
||
Each voting transaction requires a minimum affirmative threshold of stakeholders in order to pass, and by default fails to pass after a certain number of blocks. These values are also defined as chain variables. |
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.
how is the minimum affirmative threshold determined?
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'd suggest that it itself is a chain variable that is initiated with a default value by Helium Inc. Maybe a week long?
|
||
- Hotspot hosts (1:1) | ||
|
||
- OUI owners (Based on DC usage) |
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.
some handwaving here... is there a way to determine legitimate OUIs? DC usage could maybe be faked to some extent
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 agree. Don't have a great suggestion about how to combat this, other than to remove OUI's as a voting member.
# Summary | ||
[summary]: #summary | ||
|
||
This RFC attempts to describe an on-chain governance mechanism that relies on a voting mechanism in conjuction with _chain variables_ to effect changes to the blockchain network. |
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.
This RFC attempts to describe an on-chain governance mechanism that relies on a voting mechanism in conjuction with _chain variables_ to effect changes to the blockchain network. | |
This RFC attempts to describe an on-chain governance mechanism that relies on a voting mechanism in conjunction with _chain variables_ to effect changes to the blockchain network. |
|
||
## Governance Mechanism | ||
|
||
I propose that the correct mechanism for deploying a _blockchain_txn_vars_ is by on-chain vote of network stakeholders. |
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 propose that the correct mechanism for deploying a _blockchain_txn_vars_ is by on-chain vote of network stakeholders. | |
I propose that the correct mechanism for deploying a _blockchain_txn_vars_ is an on-chain vote of network stakeholders. |
|
||
- OUI owners (Based on DC usage) | ||
|
||
Hotspot hosts will have to have a _score_ above a minimum threshold before they can be considered for a given vote. |
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.
Hotspot hosts will have to have a _score_ above a minimum threshold before they can be considered for a given vote. | |
Hotspot hosts will have to have a _score_ above a minimum threshold before they can vote. |
HIP001.md
Outdated
|
||
- What should we measure to prove a reduction in complexity? | ||
|
||
- What should we measure to prove an acceptance of this by it's users? |
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.
- What should we measure to prove an acceptance of this by it's users? | |
- What should we measure to prove an acceptance of this by its users? |
|
||
- How will existing documentation/knowlegebase need to be supported? | ||
|
||
- Is this backwards compatible? |
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.
- Is this backwards compatible? | |
- Is this backward compatible? |
# Deployment Impact | ||
[deployment-impact]: #deployment-impact | ||
|
||
Describe how this design will be deployed and any potential imapact it may have on |
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.
Describe how this design will be deployed and any potential imapact it may have on | |
Describe how this design will be deployed and any potential impact it may have on |
I need to add a PR template, but I propose we crib other RFC process and put actual RFCs in a subdirectory and include a description in the filename: |
c046b44
to
3dfe920
Compare
Co-Authored-By: Jay Kickliter <jay@kickliter.com>
A proposal for on-chain governance in the Helium network.
Rendered view: https://github.com/helium/HIP/blob/4cae1fad8f262dbb443b2a5006597bd026d2a4f9/HIP001.md