> For the complete documentation index, see [llms.txt](https://bridge-docs.orbitchain.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bridge-docs.orbitchain.io/validator-guide/notes-for-validator-nodes.md). # Notes for Validator Nodes ### Advantages from Orbit Bridge Validator Participation \- Transmission of decentralized operation method in blockchain ecosystem \- DAO formation experience for governance consensus for Web3.0 transition (differences from updates through centralized servers in Web2.0) \- Gain experience in various mainnets through operation of validator nodes and accumulate know-how for node management \- Understanding and sharing of technology in the blockchain industry that Ozys has researched and developed so far ### Ozys Validator Node Operation Features \- Sharing the module connecting Web2.0 to Web3.0 and experiencing Orbit Bridge operation through module construction \- Experience off-chain consensus among various cross-chain operations \- Korean communication channel while most of the solutions communicate in English \- Strategic combination between projects and Ozys DeFi products which enables entry into multi-chain ### Costs for operating a validator node \- Server(EC2) costs: minimum requirement is consist of two t3.medium that costs ($0.052000 \* 2) / hourly → approximately $80 a month \- Monitoring system: checking node’s instance status through AWS cloudwatch, newrelic, datadog → about 10 to 30 minutes total a day \- Human resources: dedicated manager needed for following up updates on governance, disk usage, logs, bug fixes, and so on --- # 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://bridge-docs.orbitchain.io/validator-guide/notes-for-validator-nodes.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.