> For the complete documentation index, see [llms.txt](https://docs.etherscore.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.etherscore.network/documentation/factory.md). # EtherScore Badge Factory The EtherScore Badge Factory is at the core of the EtherScore protocol. It is the set of smart contracts that enable EtherScore NFT Badges to be deployed and tailored to a user’s precise specifications. The EtherScore Badge Factory is designed to focus on these characteristics: * **Decentralization:** Using The Graph subgraphs and a Chainlink oracle, our data are indexed and queried in a decentralized manner. * **Verifiability**: EtherScore Badges are stored on-chain as NFTs, and are completely auditable since they contain the query and result to check their validity. Alternative badge providers don’t provide the same level of data integrity. Communities using their badges are forced to trust a centralized badge issuer concerning badge validity. * **Customizability**: Badge issuers can fully customize their badges to meet their requirements. Users can define minting conditions, transferability, burnability, supply, evolutive badges and many other qualities. Soon: * **Openness**: Anyone will be able to create and deploy a badge model without having to ask permission or give information to an intermediary. * **Ease of Use**: A no-code interface will be provided to facilitate badge issuance. Of course, users may also interact with the smart contract directly. While the EtherScore team is already using the badge factory to issue its own collection of badges, the factory is not yet available to the public. To create or build on top of badges, please follow [the section 'For Builders'](/faq-for-builders/top.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.etherscore.network/documentation/factory.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.