Etherep - A simple reputation dapp

I have been working on a project that could use some kind of reputation system behind it so users could have some level of confidence with whom they were about to make transactions with. Looked around, and didn't really like the other solutions available. Tokens seemed a little too volume-based and trading of reputation tokens seemed like a bad idea creating a pay to play system.

Instead, I thought something a lot simpler would work for my needs so I put together Etherep. It's a dapp with a set of contracts that can be integrated into other dapps. Ideally it won't just be a standalone dapp.

I've been developing in isolation, so I'd appreciate any feedback, especially critical, on the contracts, dapp, or the Web site.

Site: https://etherep.com
Ropsten Test Dapp: https://test.etherep.com
Dapp Source: https://github.com/gointollc/etherep
Contracts: https://github.com/gointollc/etherep-contracts

Comments

  • crackthecodecrackthecode Member Posts: 8
    Wow, thats really cool! It still maintains the anonymous aspect of alt coins while still getting an idea of who the person is. Brilliant! Just a question, how did you learn solidity and creating dapps in general? I really want to learn and have my own ideas.
  • mikeshultzmikeshultz Member Posts: 5
    The solidity documentation and trial and error. And for learning, I recommend you get setup with Truffle and testrpc to make fast change-test-change easier.
  • crackthecodecrackthecode Member Posts: 8

    The solidity documentation and trial and error. And for learning, I recommend you get setup with Truffle and testrpc to make fast change-test-change easier.

    Thank you!
  • TheWolfTheWolf Member Posts: 6
    Very cool contract. I like the fact that the code is simple and easy to understand. It is a good idea too, easy to include in any project.
    However the limit of 5 min is the weak point.
    You should store the votes and check if an address has already voted for another address, it would fix the spamming problem.

    :p
  • mikeshultzmikeshultz Member Posts: 5
    Thanks for the feedback. I made that design decision because of the efficiency of the EVM. Arrays are very expensive. Also, a mapping in this case would prevent any multiple ratings of an address. I was thinking maybe one user may want to rate another multiple times, for new transactions, or in case a relationship turned sour.

    But, I generally agree that those limitations could be cumbersome to the user at times. Perhaps making the time limit per address pair would be a reasonable compromise. I'll look into it more and do some testing.
Sign In or Register to comment.