Good evening, viewers. I’m here to report some exciting news today. Doing the right thing takes time, but it’s worth it, and that’s exactly what’s happening with TN11 internal testing. The team behind TN11 has been working tirelessly to ensure that everything is up to standard and ready for the public. They have been conducting rigorous internal testing to make sure that the product is safe, reliable, and efficient. The testing phase is crucial in the development process, and although it may take time, it’s a necessary step to ensure the best possible outcome. Stay tuned for more updates on the progress of TN11 internal testing.

Reported by Shai Deshe Wyborski (大胡子)

The Rusty-Kaspa team has been working hard on the testnet 11, leading to some delays as they implement new performance improvements. These improvements are complex and require careful coding, resulting in the postponement of the public Testnet 11 run. Recently, two significant enhancements have been made:

First, the team has optimized how child blocks are tracked, reducing the number of database writes needed per block. This change alone has improved performance by over 80%.

Second, they’ve improved reachability queries, which are essential for the GHOSTDAG protocol. This optimization has significantly lessened the strain on the system’s disk space.

These updates have more than doubled the header processing rate of the client, especially benefiting machines with lower memory. The team is now focused on merging these changes and beginning internal testing.