Dear Starknet Governance Committee and fellow DAO Members,
I appreciate the dedication and continuous effort to improve and upgrade our Starknet protocol. However, I would like to express my concerns regarding the absence of adequate documentation for breaking changes to the RPC API. These concerns have led me to cast a ‘AGAINST’ vote for this upgrade and I’d like to explain why.
I see there is a lot of non technical people here so let me explain,
In the world of software development, documentation is not just an optional extra but a critical component that ensures reliability and usability of the system for its users. When API changes occur, especially those that are breaking in nature, they need to be properly documented to ensure developers are able to adjust their software accordingly. Without such documentation, systems may break and services can be disrupted, leading to user dissatisfaction and potential loss of reputation.
This happened to our team, for example getSimulateTransaction changed it’s input data. Before it was only a transaction, now it is a array of transaction with a new type field inside the transaction. The data returned also changed, which had me update all my tests and mock data all within a week before update is applied to mainnet.
Unfortunately, the provided documentation and blog posts related to the Starknet Alpha v0.12.0 upgrade do not seem to address these breaking changes.
This is not the first time we have faced this issue. It is crucial that we as a DAO address these issues proactively to prevent recurring lapses. We should insist on complete and thorough documentation for all upgrades, including details about API changes, to ensure all teams can continue building on Starknet without unforeseen disruptions.
It is my hope that we will use this opportunity to improve our process and insist on better API documentation moving forward. If these concerns are addressed in a satisfactory manner, I am more than willing to reconsider my stance and support this upgrade. But for now, for the reasons stated above, I cannot vote in favor of Starknet Alpha v0.12.0.
Thank you for considering my viewpoint. I look forward to our continued collaboration as we strive to make Starknet the best it can be.