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

Concerns about the Fisherman incentivization model #6

Open
DragonDmoney opened this issue Jun 11, 2022 · 2 comments
Open

Concerns about the Fisherman incentivization model #6

DragonDmoney opened this issue Jun 11, 2022 · 2 comments
Assignees
Labels
bug Something isn't working enhancement New feature or request

Comments

@DragonDmoney
Copy link

DragonDmoney commented Jun 11, 2022

Describe the bug
I'm not sure that the current Fisherman incentive model is suitable for trustless Fisherman (castnet)

Concerns

Contrary to ServiceNodes, Fishermen rewards are not affected by the content of the samples and TestScoreMsgs as long as they are not null.
The current fisherman model rewards all Fishermen the same amount regardless of the quality of sampling. Once we reach Cast-net and there are trustless Fishermen, what incentive is there for Fishermen to give accurate test scores? What is stopping a fisherman from giving terrible test-scores to nodes run by another actor, and giving perfect test scores to their own nodes? Typically in economic environments like this, if there is no incentive model to do a task well, then the task will not be done well. Imagine if Chainlink rewarded all nodes the same regardless of their accuracy, and its core, fisherman, and chainlink perform very similar tasks: reporting off-chain data on the chain.

Solution

These reasons lead me to propose another economic model, similar to the Chainlink model, where fishermen would be rewarded based on how similar their results are to the rest of the fishermen. Over time, these Fishermen would be given a ReputationScore, based on how accurate their data is, and their reward system and impact on ServiceNode's report cards would depend on their ReputationScore. I haven't fully thought out the exact specifications of this, but this is a significant change, and I'd like to hear your thoughts before I draft up a new specification.

Origin Document
https://docs.pokt.network/v1/utility

Creator: DragonDmoney (Pierre)

@DragonDmoney DragonDmoney added the bug Something isn't working label Jun 11, 2022
@Olshansk Olshansk added the enhancement New feature or request label Jul 1, 2022
@Olshansk
Copy link
Member

Olshansk commented Jul 1, 2022

Just wanted to link to the V1 Contributor hour presentation from 06/23/2022 discussing this topic.

I think this proposal has the foundation of potentially very meaningful changes but requires more research & discussion so tagging it as an enhancement for now.

@DragonDmoney
Copy link
Author

Note: this issue is continued by

#7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

2 participants