oceanprotocol/docs
1
0
Fork 0
mirror of https://github.com/oceanprotocol/docs.git synced 2024-11-26 19:49:26 +01:00
Code Releases Activity

Ocean Nodes update Faq.md

Browse Source 
We  collected questions related to Ocean Nodes over the past couple of weeks and gathered the most common ones. Hence, added them here

Reference spreadsheet - https://docs.google.com/spreadsheets/d/1kDEfSTBPgqpCZTFxYsmBESWcD44AgA3ccLin7bWS8qM/edit?gid=1543467007#gid=1543467007
This commit is contained in:
Wanderclyffex 2024-10-18 03:05:49 +05:30 committed by GitHub
parent d276282eff
commit a699d0d488
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 125 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

125
discover/faq.md
View File

@ -122,6 +122,131 @@ All Ocean modules and components are open-source and freely available to the com
For each consume transaction, the Ocean community gets a small fee. This happens whether OCEAN is used or not. [Here are details](../developers/contracts/fees.md).
</details>
## Ocean Nodes
<details>
<summary>What are Ocean Nodes?</summary>
Ocean Nodes are an integral part of the Ocean Protocol that centralize and simplify the process of accessing, managing, and monetizing data. They replace multiple components (Provider, Aquarius, and Subgraph) and handle tasks like securely retrieving data, verifying permissions and payments, managing metadata, and supporting compute-to-data (C2D) environments for complex data operations. Through modular layers, they ensure secure peer-to-peer communication, efficient data management, and the ability to run various compute tasks, while also providing an API for easy querying and interaction with on-chain and off-chain data. Learn more [here](https://docs.oceanprotocol.com/developers/ocean-node).
</details>
<details>
<summary>What are the minimum requirements to run a node? Can it be run on a phone or other small devices?</summary>
We recommend the following minimum system requirements for running a node, though it may be possible to operate with less depending on your configuration:
-1 vCPU
-2 GB RAM for basic operations
-4 GB storage
-Operating System: We recommend using the latest LTS version of Ubuntu or the latest iOS. However, nodes should also work on other operating systems, including Windows.
While it is technically feasible to run a node on smaller devices, such as phones, the limited processing power and memory of these devices can lead to significant performance issues, making them unreliable for stable node operation.
</details>
<details>
<summary>Can I run a node using Windows or macOS, and are there any recommended guides for those operating systems?</summary>
Yes, you can run an Ocean node on both Windows and macOS.
For Windows, it's recommended to use WSL2 (Windows Subsystem for Linux) to create a Linux environment, as it works better with Docker. Once WSL2 is set up, you can follow the Linux installation guides. Here’s a [helpful link](https://techcommunity.microsoft.com/t5/windows-11/how-to-install-the-linux-windows-subsystem-in-windows-11/m-p/2701207) to get started with WSL2
For macOS, you can install Docker directly and run the Docker image. It’s also recommended to use Homebrew to install necessary dependencies like Node.js.
For a detailed setup guide, refer to the [OceanNode GitHub Repository](https://github.com/oceanprotocol/ocean-node).
</details>
<details>
<summary>Is there a maximum number of nodes allowed, and are there rules against running multiple nodes on the same IP?</summary>
There’s no limit to the number of nodes you can run, but there are a few guidelines to keep in mind. You can run multiple nodes on the same IP address, as long as each node is using a different port.
</details>
<details>
<summary>How long does it take for a new node to appear in the dashboard?</summary>
The time it takes for a new node to appear on the dashboard depends on system load. Typically, nodes become visible within a few hours, though this can vary based on network conditions. You can check the status [here](https://nodes.oceanprotocol.com/).
</details>
<details>
<summary>How can I verify that my node is running successfully?</summary>
To verify your node is running properly, follow these steps:
1) Check the Local Dashboard: Go to http://your_ip:8000/dashboard to view the status of your node, including connected peers and the indexer status.
2) Verify on the Ocean Node Dashboard: After a few hours, visit the [Ocean Node Dashboard](https://nodes.oceanprotocol.com/) and search for your Node ID, Wallet, or IP to confirm your node is correctly configured and visible on the network.
</details>
<details>
<summary>Are there penalties if my node goes offline?</summary>
If your node goes offline, it won't be treated as a new node when you restart it—the timer will pick up from where it left off. However, frequent disconnections can impact your eligibility and uptime metrics, which are important for earning rewards. To qualify for rewards, your node must maintain at least 90% uptime. For example, in a week (10,080 minutes), your node needs to be active for at least 9,072 minutes. If your node is down for more than 16 hours and 48 minutes in a week, it will not be eligible for rewards.
</details>
<details>
<summary>How many nodes a user can run using a single wallet or on a single server?</summary>
Each node needs its own wallet—one node per wallet. You can use an Admin wallet to manage multiple nodes, but it’s not recommended to use the same private key for multiple nodes. Since the node ID is derived from the private key, using the same key for different nodes may cause issues.
You can run as many nodes on a server as its resources allow, depending on the server’s capacity.
</details>
<details>
<summary> Why does my node show “Reward Eligibility: false” and “No peer data” even though it is connected?</summary>
Your node may show "Reward Eligibility: false" and "No peer data" even when connected for a few reasons:
1) Random Round Checks: The node status may change due to random round checks. If your node is unreachable during one of these checks, it could trigger these messages.
2) Configuration Issues: Misconfigurations, like an incorrect P2P_ANNOUNCE_ADDRESS, can impact communication. Ensure your settings are correct.
3) Port Accessibility: Make sure the required ports are open and accessible for your node to operate properly.
</details>
<details>
<summary>How do I backup or migrate my node to a new server without losing uptime?</summary>
To back up or migrate your node without losing uptime, follow these steps:
1) Run a Parallel Node: Start a new node on the new VPS while keeping the old one active. This ensures uninterrupted uptime during migration.
2) Use the Same Private Key: Configure the new node with the same private key as the old one. This will retain the same node ID and ensure continuity in uptime and rewards eligibility.
3) Update Configuration: Update the new node's configuration, including the announce_address in the Docker YAML file, to reflect the new IP address.
4) Verify on the Dashboard: Check the [Ocean Node Dashboard](https://nodes.oceanprotocol.com/) to confirm that the new node is recognized and that the IP address has been correctly updated.
</details>
<details>
<summary>How do I resolve the "No peer data" issue that affects node eligibility?</summary>
It's normal for a node's status to change automatically from time to time due to random round checks conducted on each node. If a node is unreachable during a check, the system will display the reason on the dashboard.
To resolve the "No peer data" issue, consider the following steps:
1) Restart Your Node: This simple action has been helpful for some users facing similar issues.
2) Check Configuration:
a) Ensure that your P2P_ANNOUNCE_ADDRESS is configured correctly.
b) Verify that the necessary ports are open.
3) Local Dashboard Access: Confirm that you can access your node from the local dashboard by visiting http://your_ip:8000/dashboard.
</details>
<details>
<summary>Do I need to open all ports to the outside world (e.g., 9000-9003, 8000)?</summary>
It's not necessary to open all ports; typically, opening port 8000 is sufficient for most operations. However, if you are running services that require additional ports—such as ports 9000-9003 for P2P connections—you may need to open those based on your specific setup and requirements.
</details>
<details>
<summary>How is the node's reward calculated, and will my income depend on the server's capacity?</summary>
The rewards for Ocean nodes are mainly determined by your node's uptime. Nodes that maintain an uptime of 90% or higher qualify for rewards from a substantial reward pool of 250,000 ROSE per epoch. Your income is not affected by the server's capacity; it relies solely on the reliability and uptime of your node.
</details>
<details>
<summary>What are the rewards for running a node, and how is the distribution handled?</summary>
Rewards for running a node are automatically sent to your wallet as long as you meet all the necessary requirements. These rewards are distributed in ROSE tokens within the Oasis Sapphire network.
</details>
<details>
<summary>Does my node's hardware setup (CPU, RAM, storage) impact the rewards I receive?</summary>
Your node's hardware setup—CPU, RAM, and storage—does not directly influence your rewards. The primary factor for receiving rewards is your node's uptime. As long as your node meets the minimum system requirements (90% node uptime) and maintains high availability, you remain eligible for rewards. Rewards are based on uptime rather than hardware specifications.
</details>
## Grants, challenges, and ecosystem