We already said we would reduce scope so this seems like a moot discussion. We will all find out definitively in the future if its a problem or not, based on if someone decides to run various problematic cross contract calls or not, and based on various other things.
So a new proposal needs to pass to get data about how the cluster would perform with less nodes? Doesnt seem like a data driven decision making process.
You were told in telegram that the data that is available is here on stats.secret.express, you were also told that members of the team may provide data or otherwise be willing to help with testing.
Over time this tool has changed how it works, including where and how the data is stored.
If you have any other questions feel free to ask them. This specific question has been answered though.
From analysis
Future Testing Recommendations for Secret Network (not specific to API team)
The team suggests a more thorough analysis of archive node information as a viable test to understand network bottlenecks better and potentially resolve them by finding patterns in what contracts are executed when many network validators miss many blocks.
This was our recommendation to find network bottlenecks which are more generally useful anyways, I have helped with this in the past, and various members of our team have said they’d be willing to assist with further testing where available. This information is what we believe is more useful. If anyone wants to dig into this or help us do so, feel free to reach out.
The actual priority concern communicated to us via network participants was costs not tests / data. We are prioritizing the actual larger concern.
Linking to revised API Proposal IV for continuity. These reductions go into effect immediately.