Guardian Rewards Issue

[letspesl]

My guardian node is syncing well.

But, there are no rewards on staking account after 7 days ago.
0xd9a4866a55f0989d020d3eec4ae0e8cf08f983f5

Could anyone explain it's reason?

Are there some mainnet upgrade? or My mistake in settings?

[causalityloop]

dont listen to that comment. nonsense and just looking to steal your coins. if you go to guardianmonitor dot io you can see your GN is offline. why? no idea...but it is not listed as online

[letspesl]

dont listen to that comment. nonsense and just looking to steal your coins. if you go to guardianmonitor dot io you can see your GN is offline. why? no idea...but it is not listed as online

But, when I called GetStatus, It is syncing. (16888 port is not any open. 21000 opened.)

called theta.GetStatus response

• result.syncing : true / block height is also latest.

[causalityloop]

best place is to reach out on the discord channel. go to the thetatoken dot org site and on the top right is the link to the discord. best place is to ask there. i'm not sure what problem you are having but you can see the guardian node you are staked to is listed as offline from guardianmonitor site. i dont work for theta...just a regular joe like you. good luck.

[letspesl]

@weiribao Could you check this issue?

called theta.GetStatus response

{ ...
"latest_finalized_block_height": "14277530",
"latest_finalized_block_time": "1645765192",
"latest_finalized_block_epoch": "14362783",
"current_epoch": "22177568",
"current_height": "22068751",
"current_time": "1694511083",
"syncing": true,
... }

Syncing is well, but I can't get rewards still now.

And these logs appear intermittently.
Is this a problem?

[2023-09-12 09:31:52] WARN [consensus] Ignoring invalid vote err=Result{code:100000, message:Signature verification failed}

[letspesl]

First, I updated the theta binary from v4.0.0 to v4.0.1, downloaded the snapshot again, and synchronized it.
The problem has since been resolved, but I don't know the cause.
It seems like the current network instability issue still persists.