Replies: 4 comments 2 replies
-
|
btw. here is some side-proof that issue with V1 occurred on June 14 |
Beta Was this translation helpful? Give feedback.
-
|
@adspx5 the v1 database is no longer supported and the v2 should be used. Rewards are tied to your plots and not your database so that would not have any effect on payouts. Another consideration is that reward halving occurred in March which cut rewards in half, more information about this is contained in this blog: As a heads up we can generally provide more timely and thorough support in our discord server (https://discord.gg/chia). We would want to look at your log file located at |
Beta Was this translation helpful? Give feedback.
-
|
I understand about splitting rewards since March. Running local full timelord (or not running) not helping to solve the problem {{deleted}} |
Beta Was this translation helpful? Give feedback.
-
|
In that article I linked did you also read about the filter halving that occurred? If I am missing something please feel free to jump into our discord server for more timely and thorough support (https://discord.gg/chia) or provide your log file here for us to review but with the information provided I am not seeing any issues:
|
Beta Was this translation helpful? Give feedback.
-
|
Not sure if I got idea of plot filtering right, but I assume it just consumes more energy(on harvesters) since June 2024. My farm has separate harvesters. All connected. VDF Client: Running proving for iter: 7104614 ......... 2024-06-26T17:07:01.171 full_node chia.full_node.full_node: INFO ⏲️ Finished signage point 46/64: CC: f419c64cc6fa09070xxxxxxxxxxxxxxxxxxxxxx harvestrers(no gaps): |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the info! You are correct that the filter halving leads to more work being performed by the machines but with your logs it does not seem like that is an issue (proof checks all appear to be conducted in a timely manner). Please feel free to jump into our discord server for more timely and thorough support (https://discord.gg/chia) I am not seeing any issues in the above logs or reports. Do keep in mind that running more processes on the same machine will at least in part hinder the other services running (we generally recommend that timelords have their own dedicated machines). If you do want to take a deep dive then feel free to jump into our discord server and we can better troubleshoot there but I am really not seeing anything that would be cause for concern. |
Beta Was this translation helpful? Give feedback.
-
After 12pm on blockchain I was constantly getting error. BLOCK_COST_EXCEEDS_MAX
Resynching 2 month old backup didn't help. I was trying resync for few times.... Was getting the same error around the same timestamp.
2024-06-13T12:06:36.186 full_node chia.full_node.full_node: ERROR Invalid block from peer: PeerInfo(_ip=IPv4Address('98.183.103.242'), _port=8444) Err.BLOCK_COST_EXCEEDS_MAX
2024-06-13T12:06:36.187 full_node full_node_server : WARNING Banning 98.183.103.242 for 600 seconds
2024-06-13T12:06:36.189 full_node chia.full_node.full_node: ERROR sync from fork point failed err: Failed to validate block batch 5496001 to 5496033
2024-06-13T12:07:26.947 full_node chia.full_node.full_node: ERROR Invalid block from peer: PeerInfo(_ip=IPv4Address('8.23.109.77'), _port=8444) Err.BLOCK_COST_EXCEEDS_MAX
Anyone on V1 noticed same error?
Anyone still alive on V1?
Beta Was this translation helpful? Give feedback.
All reactions