[NOT A BUG] Epoch 1718 earnings for Shard 5 are reduced

There are several reports on Telegram of substantially reduced earnings for pNodes, self-staked pNodes and vNodes.

Appears to be a reduction to ~26.28% of expected earnings.
Appears to be affecting validators in Shard 5 only.

funded pNode
expected 3.822 PRV | received 1.0047

self-staked pNode
expected 10.92 PRV | received 2.8703

6 Likes

Will check with the devs.

3 Likes

@Mike_Wagner here are the raw stats from incscan:

 shard | epoch | generated_blocks
-------+-------+------------------
     0 |  1718 |              353
     1 |  1718 |              353
     2 |  1718 |              353
     3 |  1718 |              353
     4 |  1718 |              353
     5 |  1718 |               94
     6 |  1718 |              333
     7 |  1718 |              219

Less blocks generated for an epoch = less reward. It happens when a shard is stuck during X hours.

2 Likes

Thanks for the explanation. That’s the first time I’ve seen such a radical disparity in block production by a single shard.

2 Likes

It’s not the first time :wink:

If you’re curious about that, here are the stats since epoch 1: https://pastebin.com/wMvBVwrX

1 Like
 shard | epoch | generated_blocks
-------+-------+------------------
     2 |   169 |               74
     2 |   170 |               71
     0 |   181 |               73
     0 |   182 |               71
     5 |   557 |               71
     5 |   558 |               84
     0 |   900 |               71
     7 |   935 |               72
     2 |   936 |               72
     7 |   936 |               71
     2 |   937 |               71
     7 |   937 |               71
     4 |   953 |               71
     4 |   954 |               71
     4 |   955 |               81
     3 |  1116 |               71
     5 |  1418 |               71
     1 |  1543 |               71
     1 |  1544 |               71
     5 |  1718 |               94

(these stats doesn’t show when a shard produced no block for an epoch)

1 Like

Looks like Shards 2 and 5 have a history of being a bit derpy, while Shard 6 always finishes its homework, lol.

Just curious what is the cause for this, is it an issue with the validator nodes in that shard?

1 Like

Yes, the only reason for less block generated in a shard is node issues. These could be network partition / latency or bugs in production code that make these node cannot make consensus on a proposed block. In this epoch, we experienced an unstable network in block producer nodes, and this leads to a bug that these nodes cannot sync enough data to validate block.
We already added a fix for this situation and will deploy today.

5 Likes