You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lucy only assigns positive reputation. Failure to execute on a contract or solve a dispute simply translates into no reputation tokens, not negative ones.
As for the ability to down vote contracts, that's still a subject for debate. Imagine for instance if people started downvoting all contracts protecting assets of homeless people, as a coordinated attack, or something similar - it could be used as a weapon to target certain group. Rather it would be better with a function to upvote contracts if they fullfill their stated objective, and the ability to flaw contracts if there are technical issues with them.
The text was updated successfully, but these errors were encountered:
You are correct. That's an oversight on my part. I'd sampled reputation code from git and it included a negative reputation value, which I intended to remove from the final release, but kept within the code so I could study how it functioned it its entirety. I will remove it soon.
Got it. I'll keep the issue open though, because of the second point mentioned regarding negative reputation as an attack vector against groups when it comes to up voting and down voting smart contracts.
Lucy-draft/Lucy_DRAFT
Line 271 in 62799d0
Lucy only assigns positive reputation. Failure to execute on a contract or solve a dispute simply translates into no reputation tokens, not negative ones.
As for the ability to down vote contracts, that's still a subject for debate. Imagine for instance if people started downvoting all contracts protecting assets of homeless people, as a coordinated attack, or something similar - it could be used as a weapon to target certain group. Rather it would be better with a function to upvote contracts if they fullfill their stated objective, and the ability to flaw contracts if there are technical issues with them.
The text was updated successfully, but these errors were encountered: