Notary selection and incentives for v5 elections #961
Replies: 18 comments 46 replies
-
My own opinion (not PL) is that the community must not allow the election of active SPs DPs and Clients in the v5 notary cycle. Instead, finding ways to enable anyone to become a notary, as suggested here is the most reasonable path while developing mechanisms to compensate notaries for their time doing due diligence. Some suggestions on compensating notaries include but are not limited to -
Other ideas are welcome |
Beta Was this translation helpful? Give feedback.
-
I would like to suggest notary teams where each team consists of 1 tech person, 1 commercial person and one communication person. Staking and compensation are good motivations to eliminate abuse. F.e. Staking amount shall be payed by the LDN applicant. He/she can get their funds back after the LDN is proper.
To avoid collusion notary compensation should be done by PL/FF. Compensation is released when:
|
Beta Was this translation helpful? Give feedback.
-
@dcasem, clarifying that everyone here has the ability to have an opinion. I'm merely expressing that the community consider NOT electing notaries from a pool of active SPs DPs and Clients in the v5 notary cycle and if you are objecting to my use of the word "must", I'm allowed to campaign for things I believe in just like you. |
Beta Was this translation helpful? Give feedback.
-
Oppose option 3. Filecoin must be Permissionless. filecoin-project/FIPs#774 (reply in thread) Molly, tell Marko Vukolic why he's wrong. |
Beta Was this translation helpful? Give feedback.
-
I hope FIL+ will develop from the next notary selection. Notary
Client.
SP
|
Beta Was this translation helpful? Give feedback.
-
I think this is a good proposal, which shows that each of us is working hard to achieve a better FIL+. Below, we discuss two issues: First, if we do not choose from active SPs DPs and Clients, how should we choose? Can you list more detailed selection criteria. In my opinion, as long as quantifiable standards are listed and accepted by the community, this suggestion can be implemented. Any discussion takes time, and we should give ample time and patience to the development of standards. Second, perhaps this is a dialectical relationship, not all active SPs DPs and Clients are abusing DC, but those who abuse DC are often very active. We can choose a "novice" as a notary, but when he becomes a notary, he may change from an "outsider" to an "insider". People who abuse DC are often powerful people. When you give anyone power, he may abuse it. |
Beta Was this translation helpful? Give feedback.
-
100% agree with this. There is a DP role that helps clients with data process and deal-making, he/she is an important bridge between clients and the Filecoin network. The status quo is that one person plays more than 2-3 roles, which is probably a big reason why FIL+ has gone to nowadays. Regardless of the selection criteria for V5, the above should never happen again. @raghavrmadya |
Beta Was this translation helpful? Give feedback.
-
I don't think there is a need to elect V5 notaries because future notaries would be redundant. Anyone who get the normal reports will automatically get the quota for the next round. |
Beta Was this translation helpful? Give feedback.
-
Let's move on to:
If so, we run into three problems:
|
Beta Was this translation helpful? Give feedback.
-
Agree with @nicelove666, We cannot solve an old problem and bring in a new one at the same time. |
Beta Was this translation helpful? Give feedback.
-
Taking consideration where this is going, I am going to propose the following:
|
Beta Was this translation helpful? Give feedback.
-
True, false, cold and hot are behavioral data created by different SP situations. Storing data is SP's choice and is influenced by policies, regulations and the industry environment. Data retrieval is a requirement of the upper-level data demand scenario, we can create a new project fil++, open source programs reference data CID from IPFS, give the corresponding datacap quota reward. For example, if the small program or portal internal data reference connection comes from the corresponding SP supplier, the corresponding SP supplier will be provided with the corresponding SP credit reward because of its contribution to the development of ecology. |
Beta Was this translation helpful? Give feedback.
-
Is it possible to set up a reward and punishment mechanism to automatically constrain the behavior of notaries? Like set up a reward pool? For example, a certain amount of FIL will be collected from all notaries as pledges at the beginning of a period(like the beginning of a month), and the FIL pledged by inactive notaries will be redistributed in proportion to the most active notaries (can be decided by voting, etc.) at the end. The rest of the pledges can be carried over to the next period. If notaries no longer want to continue to play this role, they may also have a withdrawal option to take back the FIL coins they pledged. |
Beta Was this translation helpful? Give feedback.
-
I'm with @herony-fil on the reward and punishment mechanism, but I think we could make this notary selection and incentive process much easier. Anyone should be able to be a notary. Here are the requirements:
That's it. And there are two rules as a notary:
Resulting behaviors we are looking to create:
The catch with this approach is that clear, objective, measurable requirements need to be implemented first in the areas of:
We need to continue discussions and enhancements in these areas. If we can make quantifiable on-chain data 'indicators' part of the approval process, the notary job can become more of a checks and balances role than as a guardian of DataCap. |
Beta Was this translation helpful? Give feedback.
-
My suggestion is to improve the notary mechanism that combines tools, tasks and incentives related to Trust&Transparency.
Based on the above mechanism, we need to further improve the community rules and complete the tool development as soon as possible. Avoid uneven workload distribution, discrimination, monopoly and other situations.
The rules and order of the community were in chaos for a period of time. If notaries who are willing to continue due diligence, they can form the fifth round of notaries team. At present, the existing notaries have a certain understanding of the community and rules, which reduces the education cost. If there is no completion of the task and notaries removal, the community conduct the phased of new notaries expansion. |
Beta Was this translation helpful? Give feedback.
-
IMO, Why not back the slashed FIL to the reward pool? Should we have clear rules or workflow for judging if an application should be shut down or continue or DataCap removing? |
Beta Was this translation helpful? Give feedback.
-
Applications should be judged by objective codes or reports and not overly rely on supposedly upstanding notaries. I agree to a large extent with the community must not allow the election of active SPs DPs and Clients in the v5 notary cycle. |
Beta Was this translation helpful? Give feedback.
-
I’m still waiting for someone to propose a measure of usefulness other than willingness of the user to pay. |
Beta Was this translation helpful? Give feedback.
-
It has been widely discussed that one of the underlying challenges in addressing DC abuse is notary compensation. Inherently, we have seen a significant overlap in the SP and clients roles notaries play in the current system which makes it extremely challenging to separate the due diligence duties from data onboarding and storage functions in the network.
As such, this discussion invites thoughts and suggestions on compensating notaries for their time and implementing such change as soon as the V5 election
Beta Was this translation helpful? Give feedback.
All reactions