# Reputation System The Griffin AI network operates on a permissionless basis, allowing any entity to offer services, operate nodes, or deploy agents. To ensure accountability and build trust, the network assigns unique identities to participants, verifies ownership of these identities through private keys, and records their reliability in a centralized reputation system. Guardian nodes are central to the management of the Griffin AI reputation system. These specialized nodes are responsible for recording and assessing the performance of service providers and AI agents, ensuring that all activities are transparent and accountable. To prevent conflicts of interest and promote impartiality, only Guardian nodes have the authority to write to the reputation system within the Griffin database. Guardian nodes maintain and verify the accuracy of performance metrics, such as service availability and response times. They also aggregate reputation scores provided by network participants. In terms of dispute resolution, Guardian nodes are responsible for addressing and settling conflicts between service providers and users. They have the authority to modify reputation scores, retract negative feedback, or impose bans on Root Identities based on the outcome of their review. While the permissionless nature of the network prevents the physical disconnection of non-compliant operators, these operators can be excluded from the Griffin reputation system. This exclusion acts as a deterrent, making them less visible to new users and signaling potential risks to existing users. That said, Client Providers (CPs) may establish alternative reputation systems with different standards and procedures, tailored to meet the specific needs of their services or community. These systems can vary in their emphasis on security and trust, potentially deviating from the standards set by the Griffin reputation system. This approach to identity verification and the implementation of the Griffin reputation system create a secure and reliable environment for all users and agents on the Griffin AI network. Alongside the network's permissionless principles, this setup allows third parties, such as Client Providers (CPs), to operate their own reputation systems. This flexibility supports a censorship-resistant and open network, accommodating diverse needs and enhancing the overall ecosystem. --- # 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://griffin-ai.gitbook.io/knowledge-base/griffin-identity-management-and-reputation-system/reputation-system.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.