-
Notifications
You must be signed in to change notification settings - Fork 68
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
ZIP: on-chain reputation mechanism #488
Comments
we've been thinking about it for ages, the problem is that due to privacy you can't validate if rating-involved contracts was made by the same actor, which devalue the rating since it's quite easy and quite cheap to fake it by creating hundreds of self-contracts. |
Unless someone know the particular way to do so in top of private blockchain |
Perhaps an optional 'postage stamp' type solution, this being it costs both parties, perhaps the postage stamp is burned. Perhaps upon initiating the contract, there is an option to 'contribute to reputation', which would have to be accepted by the receiving party. Upon completion of the contract, the postage stamp is burned, and rep points associated to the aliases involved. This will atleast make it costly for somebody trying to spam contract completions. Just an initial idea. |
i believe there is nothing you can "burn" in term of information or proofs, anything once there can be memorised forever even you you prune it from the blockchain. Anyway, aliases could be involved in rep system, but then we're building Ethereum here, which i don't believe we should. |
An On-chain reputation system will come to be absolutely essential and a necessity for multiple use cases over time.
This could work by using the alias and escrow contracts together, Each time a escrow contract is accepted by both parties, some reputation is assigned to the aliases involved, possibly weighted towards either the initiator or receiver.
When looking at the aliases on the explorer, there would be some transparent 'reputation score' present.
The text was updated successfully, but these errors were encountered: