Scott Yeager

It seems the situation is actually worse. The problem is that farmerbot managed nodes must produce a specific sequence of events in order to avoid penalties at minting time. A...

Checking another example, I am beginning to doubt that it was the node at fault as I wrote above. In this instance there is again a hash logged by Zos,...

Thanks for the additional analysis on this @LeeSmet. I wonder if there was something to this after all: > * What only remains is if the substrate client itself (the...

To summarize, we have two general cases where nodes create a log suggesting successful uptime reporting, but no uptime event is created on tfchain: 1. Extrinsic is rejected with a...

We are seeing a lot more instances of failed uptime reports that appear in Zos logs to be successful (logged with a block hash). Here's an extreme example of a...

Here's another instance from today: ```console 2025-06-05 03:01:42 [+] powerd: 2025-06-05T03:01:42Z info node uptime hash hash=0xa778515aed22253fef4395c5aa696c992c4c292ca29222e190efb53cec4e1aa0 2025-06-05 03:01:38 [+] noded: 2025-06-05T03:01:38Z info utc time from tfchain: 2025-06-05 03:01:36 +0000 UTC...

> is this still happening? Yes, here are some recent examples: ``` -------------------- FAILED UPTIME EXTRINSIC FOUND in block 19404835 (0x028cd368b497479878450572e1ef7c84abbbfde94bb15c0336a82cdd44933db2) Timestamp: 2025-09-08T16:40:48 (1757374848) Extrinsic Index: 1 Failed Count: 1...

We need some more discussion around this, and probably a GEP, before implementing. The summary though is that RAM generation serves as a simple and effective proxy for overall hardware...

Yes, looks indeed like a failed disk. The question is why doesn't the error appear on the console screen.