eos-rate
eos-rate copied to clipboard
eoscostarica
How to prevent spam
We need to consider scenarios where people may want exploit the rate system for its own benefit.
Being on chain rating only real EOS accounts will be able to rate BPs.
However, what if these accounts were fake, created with the sole porpuse of rating. How can we prevent that type of scenario while maintaining a frictionless user experience.
The Block.one wallet may have Proof of Life, that could solve the problem https://medium.com/acroeos/ubi-uri-proof-of-life-eng-6678f19ebd33
One person must not be able to rate more than once with different accounts. In order to ensure the ratings are 1:1 to real people need some sort of Identity verification.
We can always start with the promise to remove unverified account ratings from the results afterwards
Maybe Scatter Identities can be used here ? Scatter Identities are containers for personal data, and authentication / permission mechanisms. has https://get-scatter.com/docs/identities
That could be one way, however not all wallets support that. Eg Lynx. Also it work until certain extend, you can have multiple identities.
We could do the following, we allow everyone to rate. But we filter out the results we show, we only display results from rating of account that have at least 5 EOS.
A cron job would be run daily to check for balances.
Additionally I think we should also replicate Voter Decay rules for the the Ratings. this is another thread for that discussion #63
another idea: require rating a minimum of 21BPs in order to get your ratings counted on the aggregate.
I think we can just start without this and later use Voice to prevent it.
@edgar-eoscostarica maybe we can require accounts to vote for at least 30bps as well?
We can include other types of requirements such as having a minum balance of 10 EOS