A Radical Market Approach towards FIP Consensus #1040
Fatman13
started this conversation in
Enhancements - Technical
Replies: 2 comments
-
Soft Consensus = Juan supports this FIP |
Beta Was this translation helpful? Give feedback.
0 replies
-
Greate FIP, the cornerstone for moving forward. Support this. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Introduction
Filecoin has been using the soft consensus process for accepting or rejecting FIP proposal since its mainnet, which has its merits and flaws. This thread intends to solicit discussion on using a radical market approach to improve current FIP consensus process, which is inspired by Radical Markets authored by Eric Posner and Glen Weyl.
Background
Why Market Approach?
For lacking other competent alternatives, markets have been the most efficient way to capture participants' preferences since emergence of land and labor markets during industrial revolution. Like in real world there is no political market to reflect constituency's preferences in different policies, there is no market in Filecoin consensus process to reflect network stakeholder's preferences in the direction of where the network should be heading. It is thus crucial to establish such market so that the community could collectively steer the network to its betterment.
An Example Market
An example describing how a consensus market that could proximate individual's preferences given a range of choices could be found here. It is recommended that readers of this FIP discussion to go through the example in the aforementioned link from page 2 to 3.
Key Takeaway
There are key elements for a consensus market to work, on which the proposed market approach relies heavily.
Proposed Market Approach
Each aspect of the market approach below is subject to better alternative solution and further fine tuning per discussion.
Acquiring Voting Credits
A staking mechanism to allow network stakeholder, ie token holders, to accumulate voting credits (vfil) over time. The amount of voting credits one is awarded over a time interval could be a function of amount of token staked and the time it is committed in staking. And once the time commitment is fulfilled, the amount of fil token would then be released back to the staker. For example...
The staking time could be [180, 1080] days in conformity with sector lifetime defined in core protocol so that token staker and miner could both use the same vfil vesting function.
Additionally, vfil vesting function could take into consideration that the longer tokens are to be staked the more vfil it could reward the staker to incentivize long term alignment which helps alleviating potential problems of voting out of short term interests.
Voting Scope
All FIPs are to be voted for acceptance or rejection to capture community's preferences on where the network will be heading. The larger the scope of the voting is, the better it would reflect preferences.
QV
Quadratic voting has been used by Filecoin in projects like network public goods and regtroPGF. QV concept works as the following...
QV outperforms traditional 1 person 1 vote (1p1v) system in...
A fundamental issue that QV tries to address is that...
More on "why quadratic voting" can be found under "Quadratic Voting" section on page 19 of this link.
KYC
A key component for this voting scheme to work is KYC which is not mentioned in the book as it is always assumed that KYC just works in real world, but in Web3 it would be much more challenging to properly KYC on a global scale. It could be either a combination of Web2 accounts (Github, Twitter, Slack), or maybe a minimum staking threshold say the amount of pledge required for median node QAP among all mining nodes. Any suggestion on KYC or alternatives is welcomed.
Voting & Acceptance Criteria
TBD
Limitations
QV
QV is not without its limitations. For example...
vfil tokens could be soul bound to reduce the risk of bribing. For example, stakers transfers its vfil to others to vote for a price.
KYC
A flawed KYC or alternative may result in DDOS attacks wrt voting. For example, token holder distribute its staking so that it takes advantage of using 1 vfil to buy one vote and never go up to higher cost of acquiring multiple number of votes.
Enforcement
Quick reactions and strong stance on frauds maybe challenging to achieve on large scale. For example, it would be very damaging to voting's credibility if no action were to be carried out investigating and mitigating fraud.
A proposal by Ancients Research
Beta Was this translation helpful? Give feedback.
All reactions