EtherScore
WebsiteAppTwitterDiscordLensSnapshot
  • Overview
  • Documentation
    • ❓What's EtherScore?
    • đŸŽ–ī¸EtherScore Badges
    • đŸĒĒEtherScore Profiles
    • đŸĨ‡Reputation Tiers
    • đŸ›ī¸EtherScore DAO
      • 🌱Alpha Version
      • đŸŒŗBeta version
      • ➕Benefits of Reputation-Based Governance
      • ➖Limits of Reputation-Based Governance
    • 🏆Badge benefits
    • 🏭EtherScore Badge Factory
    • đŸ›¤ī¸Roadmap
  • FAQ (FOR USERS)
    • đŸŽ–ī¸How to claim badges?
    • 🏆How to claim Discord roles?
    • 📜How to vote in EtherScore DAO?
    • âœī¸How to propose badges to the DAO?
  • FAQ (FOR BUILDERS)
    • đŸ› ī¸How to create badges?
    • đŸ—ī¸How to build on top?
      • 🔒Token-gate your community (Discord/Collab.land)
    • 🧑‍🎨How to integrate EtherScore Profiles?
  • Others
    • 🔗Useful links
    • â„šī¸Contract addresses
    • 🎨Brand kit
  • More readings
    • Introduction
    • 🔍Problem statement
      • Data analytics access
      • Absence of reputation system
    • 💡Reputations in Web3
Powered by GitBook
On this page
  1. More readings

Problem statement

PreviousIntroductionNextData analytics access

Last updated 10 months ago

Blockchains need reputation systems. The ecosystem lacks the ability to access historic, granular, or processed data. Therefore, true reputation models do not exist. Applications have difficulty identifying and rewarding users. While some applications have started to exploit refined data, usage remains limited to informative front-end or market data purposes. Blockchains need access to data directly on-chain to enable a new generation of reputation-based services. Indeed, while more than 90% of traditional companies use a system to track user fidelity/engagement , Dapps still have difficulty integrating the concept.

🔍
(source)