# Introduction xHashtag is a Web3 protocol providing on-chain credentials. Using reputation credentials, brands can dynamically assemble skilled liquid teams while users are able to build their Web3 reputation and earn in exchange for creating value*.* xHashtag offers 4 key features aimed at boosting every partner Web3 project: **1) Soultag Credentials**\ **2) Automated Loyalty Program**\ **3) SoulDrops**\ **4) .SOUL Web3 domain names** xHashtag builds on the strengths of #Web3 projects through the Automated Loyalty Program by helping them build and grow a reliable community, that believe in the project and are willing to back it. In addition to activating the partner project's existing community, xHashtag is also able to mobilize its large user base towards the project, by rewarding them with non-transferable achievement credentials called Soultags for their contribution to the project in terms of task and campaign completion. The SoulTag SBTs are used as a method of identification which helps in conducting targeted Sybil-resistant airdrops called Souldrops. This would ensure that genuine workers are rewarded aptly for the tasks completed by them, and projects would also benefit from access to unique and targeted participants for their tasks, sans fears of bots, impersonation or duplicity. Additionally, the launch of .Soul names helps users showcase their SBTs in a single place. The SBTs collected by the user, regardless of the issuer, would be shown directly to the user via the domain link made accessible via our DNS gateway. The domain names ending with “.soul” are minted on Ethereum & Polygon blockchain and are tradeable on Opensea and other marketplaces. --- # 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.xhashtag.io/what-is-xhashtag/introduction.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.