# Full and Light Nodes Griffin AI's network is structured into multiple tiers to cater to varying use cases as well as computational and storage needs: * Full Nodes (Lion Client): Operated by active network participants, these nodes are integral to the network’s operation. Full nodes are operated by either SP (mandatory to operate a full-node), CP (optional to operate a full-node, can also run a light-node or SDK) or Gurdians (mandatory to operate a full-node). These nodes connect the operator to the Griffin Network. * Light Nodes (Eagle Client): These nodes provide wider accessibility and are designed for participants with limited resources such as client CP, individual developers and AI agents. Optimized for lower system requirements, these nodes primarily focus on service execution. While limited in functionality, they can access the full Griffin Network through connected full-nodes. \ The network maintains operational integrity through differentiated staking requirements for these two client types. Node operators are mandated to stake tokens, a mechanism that aligns their operational objectives with the overarching goals of the network and underscores their commitment. Moreover, the network is implementing incentive mechanisms that provide rewards to operators for hosting AI services and actively participating in the governance and maintenance of the network. This approach not only encourages sustained engagement but also fosters a collaborative and stable network. --- # 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/decentralized-ai-network/griffin-nodes/full-and-light-nodes.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.