Reputation Systems
on the Blockchain
Andrés Junge
andres.junge@consensys.net
Why do we want a reputation system?
Take a decision fast
"is it worth it?"
"how it is going to behave?"
"which one should I choose?"
Does my dApp need a RepSys?
Reputation Statement
- Source
- Claim
- Target
"Joe says Tim is a good developer"
"Jamie thinks Blockchain technology is revolutionary"
"Daniel told me that James Bond's movies are the best action movies, ever!"
"Banco de Chile has evidence that I'm a good payer"
Context!
Never ever mix contexts!
A bad payer is not a bad worker!
A good priest is not necessarily a good person!
Can't pay
Bad payment reputation
Can't find job
Lose job
Collect & store reputation statements for a context
Aggregate claims for a target
Make a decision base on the reputation "score"
In a contract!
Collect & store reputation statements for a context
please consider:
-
Claims coding
-
Privacy
-
Aging
-
Ownership
-
Cost
Aggregate claims for a target
In a contract!
problems arrise:
-
Which Aggregate function?
-
Function is personal
-
Weighted by source
-
General function makes sense?
Contract can make a decision!
Make a decision base on the reputation "score"
Well......
Recap
-
Does my dApp need a RepSys?
-
Don't ever mix context.
-
Aggregate function makes sense?
-
Leave decision to the humans
¡Gracias totales!
http://slides.com/ajunge/devcon1-repsys
DevCon1 Reputation Systems
By Andres Junge
DevCon1 Reputation Systems
- 922