No,. There’s some newer versions out there but all for test net. An announcement will come from IOG for main net in due course
2 Likes
Does anyone know what happened to 1.35.0? A couple of weeks ago this was the latest release, but now the latest release is 1.34.1 again! Was 1.35.0 pulled back?
7.4d4
27 July 2022 12:28
5
1.35.0 seems to have been pulled as a recommended release because of this issue:
opened 01:24PM - 24 Jul 22 UTC
bug
### Strange Issue
So, i will post a bunch of pics here, screenshots taken fro… m pooltool.io. Blockflow is from botton->top. These are only a few examples, there are many more!
**This is happening on mainnet right now** running 1.35.* nodes. There are many occasions with double & tripple height battles where **newer v7 1.35.\* nodes** are **picking up the wrong parent-block** and try to build on another v7 block. So v6 1.34.* nodes are winning those all the time.
I personally had the issue loosing 10 height-battles within a 1-2 day window against v6 nodes. That was 100% of all my height-battles i had.
Its always the same pattern: There is a height battle that a v7 node looses against a v6 node. If there are also two nodes scheduled for the next block and one of them is a v7 node, it picks up the wrong lost block hash from the previous v7 node and builds on it. Of course it looses against the other v6 node which is building on the correct block. But as you can see in the example below, this can span multiple slotheights/blocks ⚠️
This is a Vasil-HF blocker IMO, because it would lead to the situation that SPOs are only upgrading to 1.35.* at the last possible moment before the HF, giving the ones staying on 1.34.1 an advantage. Not a good idea, it must be sorted out before. Q&A team please start an investigation on that asap, thx! 🙏
![image](https://user-images.githubusercontent.com/47434720/180648823-942ce127-18d8-4aa7-b5c5-b2506852482f.png)
-----
![image](https://user-images.githubusercontent.com/47434720/180648826-f0317024-d6d1-48f7-8d28-03a7cce45c14.png)
-----
Here is a nightmare one, v7 built ontop of other v7 node (green path):
![image](https://user-images.githubusercontent.com/47434720/180649301-95f087c4-c882-4909-bb56-6ecc33447a15.png)
-----
![image](https://user-images.githubusercontent.com/47434720/180648837-4063c8c9-3746-4e49-9cb9-9b0796d21722.png)
-----
![image](https://user-images.githubusercontent.com/47434720/180648850-e9892b2d-1538-45c4-a1cd-fbcd18bb764f.png)
-----
![image](https://user-images.githubusercontent.com/47434720/180649488-3c6cdc63-4e9e-4dcc-a846-461d6af7d581.png)
-----
![image](https://user-images.githubusercontent.com/47434720/180648859-8a0b757e-d5b5-4b8a-8e46-ea7623b2b714.png)
-----
![image](https://user-images.githubusercontent.com/47434720/180648865-5589296a-9ba8-47fa-9635-603ad5264a01.png)
So are we running 1.35.3 on mainnet? I would they would make that very easy and clear.
Wow, another call to upgrade in a same day.
…, because the first one was deleted … due to blowback?
HeptaSean:
due to blowback?
Blow back in just 1 hour and 39 minutes
Most efficient ghost-chain community ever.
1 Like