Hello guys! With whom i can talk about nodes?

Hello! How I can help you?

I supported your node from all my servers for 2 weeks with 100% uptime, and on the payout day, you just reduce the uptime everywhere so that you don’t have to pay the deserved reward? Do you think this is fair? Why are you treating the community like this? I checked 10-12 hours ago, everything was fine, and I don’t believe that uptime could suddenly drop by 50-60% on the payout day!

It is understandable to feel frustrated about sudden drops in uptime on payout days. This issue has been reported by other users as well, and it might be related to how the network checks uptime rather than your nodes' performance. The team is aware and actively working on resolving these monitoring issues. Thank you for your patience and support. [1] Generated using AwesomeQA AI. Please rate this answer.

Just explain me, I'm not a beginner and supporting to many projects. But this kind of injustice seeing first time!

Hey, I understand your frustration, but I want to assure you that there’s no intention to deceive anyone. Could you kindly share your Node ID so we can look into this further? The dashboard reflects cumulative uptime up until the last round checked, so it’s based on real-time data as it stands. It's also worth mentioning that node performance can fluctuate due to various factors like connection stability or meeting specific criteria. We're actively working on improving these aspects, and your feedback is truly valuable. We launched Ocean Node in August, with three development phases planned, and we’re constantly refining things based on community input. Thanks for your understanding!

Стикер

I’m not talking about the epoch. The conditions state that the node’s uptime is calculated weekly, and rewards are distributed based on that uptime, correct? But why did my uptime suddenly drop to 50-60% on the payout day, even though it was 100% for over 10 days? I just can’t understand the logic here. This issue isn’t just affecting me, it’s affecting my entire team and community. I have my own Telegram channel, and everyone is seeing the same results. It would be one thing if it were just 1-2 cases, but over 50 people have already reached out to me about this. the dashboard is not opening right now, here is my wallet address: 0x279106f79ffb745c50a6a3aad78a09dc19b7f2f5

Go ahead and message me regarding your issue for further assistance , I won’t message first

There's nothing unusual here, which means at some point, the monitoring mechanism couldn't connect to your nodes. And your uptime couldn't have been more than 10 days, as one epoch lasts only 7 days.

But my node is connected and working more than 10 days without any issues from my side. I paid for Alchemy api and did everything to keep my uptime 100%. Even in longs no any issues.

I understand your perspective. Allow me to provide an introduction to the potential causes of these issues. Node is a lightweight system, meaning it does not consume significant resources or capacity. The current minimum requirements are minimal. When compared to nodes of other blockchains or projects, you will find that Node’s requirements are significantly lower, often by an order of magnitude. As a result, during periods of high demand, the system may not function optimally. The large number of nodes complicates communication and state synchronization. However, it is important to note that the developers released an update to the monitoring system yesterday. Continuous optimizations and improvements are being implemented. While I cannot provide a specific reason for the sudden ineligibility of nodes, as I am not a developer, my observations indicate that this rebalancing affects various nodes rather than specific ones.

Same thing, sir.

please check my address 0xe2D78eD2097efAF7afD0Be8f92affD395dC47edB in the dashboard, I should have 100% uptime and suddenly the node created a new node id and became two, so I didn't get 100% uptime, and I did a manual restart.😭

Ensure your node has a public IP address, and both API and P2P ports are exposed to maintain uptime [1]. Temporary network fluctuations can cause such issues, so monitoring network conditions can help [2]. Generated using AwesomeQA AI. Please rate this answer.

Hello! You probably created another node and specified the same data Check how many dockers you have One node - one wallet. If you use the same private key on multiple nodes, it is generally not recommended because the node ID is derived from the key, and having multiple nodes with the same key might not be a good idea.

A node cannot spontaneously create a new node ID. A node can take another IP if you transition from one VM to another. However, personally, I haven't observed cases where the node does this as you mentioned.

Стикер