Shardnet Uptime Scoreboard Needs Resetting

[joesixpack]

Newer validators have superior uptime because there is significantly less epochs to average the uptime over, especially excluding the three hard-forks.

I suggest resetting the dashboard on every hard-fork for fairness.

[DDeAlmeida]

@htafolla

[htafolla]

We discussed this on the call, and it was decided to leave it as is. The primary reason is that the scoreboard tracks performance across the entire competition. Not to mention the metric is above 70%. So although new validators show at the top, it does not necessarily mean they are the leaders in the competition or for one of the 200 MainNet seats.

[strangeweb3guy]

Hi, what about 9th task. So you will track 70+ uptime by that scoreboard? Or is it enough screenshot? I mean if you have bad uptime you can just recreate staking pool and screenshot 100% or just 70%+ uptime but by the time you will have lower uptime.

Also as I see the problem with low uptime is regarded as a network problem or software problem(I mean validator software). So how we can pass the 9th challenge before it will fix?

[DDeAlmeida]

@gmilescu

[Bela1401]

To be in the list of active validators, I need to have a stake constantly greater than the value of the validator's place. This number is constantly growing, but tekens in the discord do not delegate and it is forbidden to abuse the faucet. What to do with it?

[TandemK]

You calculate the uptime separately by blocks and by chunks. Which, in my opinion, does not correspond to the general calculation formula. So which of the indicators do you accept or summ of both?

[Foo115]

You calculate the uptime separately by blocks and by chunks. Which, in my opinion, does not correspond to the general calculation formula. So which of the indicators do you accept or summ of both

im also confusing.....i produced 45/45 block but my % online just 50 %....lol

[TandemK]

The formula for calculate uptime in near-cli: (produced_blocks+produced_chunks)/(expected_blocks+expected_chunks)*100

[htafolla]

We added a factor of missed epochs as well. For this competition, we are focusing on Chunks as it is for Chunk Only Producers.

(produced chucks / expected chunks) (validated epochs / total epochs) 100

Total epochs = Number of epochs that have passed since the validator was first seen in the validator set.

On Wed, Aug 3, 2022 at 8:03 AM TandemK @.***> wrote:

The formula for calculate uptime in near-cli: (produced_blocks+produced_chunks)/(expected_blocks+expected_chunks)*100

— Reply to this email directly, view it on GitHub https://github.com/near/stakewars-iii/issues/67#issuecomment-1203922145, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACHO5VMTQPF4JTPEL4B32YLVXJUZXANCNFSM55ILWNWQ . You are receiving this because you were mentioned.Message ID: @.***>

-- Thanks, Henry Tafolla Office: 316-202-0755 Cell: 316-841-4238 Email: @.***

[Bela1401]

We added a factor of missed epochs as well. For this competition, we are focusing on Chunks as it is for Chunk Only Producers. (produced chucks / expected chunks) (validated epochs / total epochs) 100 Total epochs = Number of epochs that have passed since the validator was first seen in the validator set. … On Wed, Aug 3, 2022 at 8:03 AM TandemK @.> wrote: The formula for calculate uptime in near-cli: (produced_blocks+produced_chunks)/(expected_blocks+expected_chunks)100 — Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACHO5VMTQPF4JTPEL4B32YLVXJUZXANCNFSM55ILWNWQ . You are receiving this because you were mentioned.Message ID: **@.> -- Thanks, Henry Tafolla Office: 316-202-0755 Cell: 316-841-4238 Email: @.

What are the main parameters that will be taken into account when distributing a delegation in the mainnet?

[strangeweb3guy]

We added a factor of missed epochs as well. For this competition, we are focusing on Chunks as it is for Chunk Only Producers. (produced chucks / expected chunks) (validated epochs / total epochs) 100 Total epochs = Number of epochs that have passed since the validator was first seen in the validator set. … On Wed, Aug 3, 2022 at 8:03 AM TandemK @.> wrote: The formula for calculate uptime in near-cli: (produced_blocks+produced_chunks)/(expected_blocks+expected_chunks)100 — Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACHO5VMTQPF4JTPEL4B32YLVXJUZXANCNFSM55ILWNWQ . You are receiving this because you were mentioned.Message ID: **@.> -- Thanks, Henry Tafolla Office: 316-202-0755 Cell: 316-841-4238 Email: @.

It is strange to calculate epochs when before the new commit that happened on 02.08, we had issues with producing blocks because of location and network synchronization. I mean I've started challenging around the start date and lost many epochs because of node software problems that you have fixed less than a week ago.

[ivanguardia]

May be the formula would be more fairly from the last fork instead from first proposal. So, anybody with 1 epoch will be on the top. (produced chucks / expected chunks) (validated epochs / total epochs) 100 Total epochs = Number of epochs that have passed since the last fork.