> For the complete documentation index, see [llms.txt](https://docs.zkshine.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zkshine.xyz/node-operations/node-types-and-responsibilities.md). # Node Types & Responsibilities #### **Compute Node** **Purpose:**\ Performs private computation, zk proof generation, and AI inference tasks for zkShine’s network. **Responsibilities:** * Generate zk-SNARK/zk-STARK proofs for user computations * Validate proofs submitted from other nodes * Maintain proof integrity and task history **Reward Source:**\ Compute verification fees + network rewards. #### **Relayer Node** **Purpose:**\ Ensures **transaction anonymity** by rebroadcasting Solana transactions through encrypted relay paths. **Responsibilities:** * Receive transactions from zkGateway * Strip metadata and rebroadcast to Solana validators * Maintain randomized routing for unlinkability **Reward Source:**\ Relay fees proportional to traffic volume and uptime. #### **VPN Node** **Purpose:**\ Provides **decentralized RPC routing** and privacy tunnels for dApps and wallets. **Responsibilities:** * Route encrypted RPC traffic * Rotate session identifiers * Ensure no logs or IP traces are kept **Reward Source:**\ Bandwidth fees + zkVPN usage payments. #### **Vault Node** **Purpose:**\ Handles zkVault encrypted storage and zk access control proofs. **Responsibilities:** * Store encrypted user data in decentralized shards * Respond to zk-proof-based access requests * Maintain 99.9% data availability **Reward Source:**\ Storage allocation + proof validation rewards. --- # 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.zkshine.xyz/node-operations/node-types-and-responsibilities.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.