# Reputations in Web3 EtherScore badges can help to curate blockchains users according to their past actions. In fact, a lot of existing systems are already using such approaches as in social networks (Twitter), forums (Reddit), or collaboration platforms (Github) where trust between users can be acquired from their previous actions. While the transparency, when there is, of such systems allows anyone to dig into the user profiles to check their history, it is unfeasible on a large scale, and most known websites instead use various badges, ranks, or status to directly identify users. All these methods tend to curate communities and bring trust between users by aggregating and synthesizing user’s past experiences (which can highlight fake accounts or bad behavior). Once profiles are curated, this creates a list of reliable users which can also be used to distribute gifts, discounts or privileges. Such lists of users were nonexistent directly on-chain, which was clearly limiting their usages in current blockchains and Dapps. Community curation using EtherScore badges could be a solution to several existing issues related to a lack of user identification tools on Ethereum. Indeed airdrops, token sales, and DAOs governance could become more distributed among curated users by using badges as access conditions (a lot of new services can also emerge such as in DeFi with under collateralized loans but also in decentralized social networks or anything that requires mutual trust). Such techniques could lead to virtuous cycles where those ’Web3 user profiles’ help to reduce the number of scams and bring value to user’s involvement in platforms. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.etherscore.network/more-readings/reputations-in-web3.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.