Original - Odaily
Author - Azuma
On the evening of November 12, Starknet announced the v0.13.0 versionUpgrade AnnouncementIt triggered extensive discussions in the community because the upgrade content clearly mentioned the STRK tokens that had been generated but not yet circulated by Starknet (for the time being, they only play a governance role through a few delegates), so the announcement was also interpreted by many community members as Starknet is about to conduct the official distribution of STRK, including a large-scale airdrop to the community.
So, what did last night’s upgrade announcement say? Let’s go back to the original text to learn more about it.
As can be seen from the picture above, the announcement in the Starknet community forum last night mainly involves the specific planning of the v0.12.3 and v0.13.0 versions. Putting aside the v0.12.3 version that is optimized as a minor version, let us put aside Focus on the v0.13.0 major version upgrade.
Simply put, vThe main content of the 0.13.0 upgrade is the new transaction type V3, which is an iteration of the internal structure of Starknet transactions. Its purpose is to enable the Starknet network to support some future functional upgrades, thereby allowing the application layer to carry out more complex construction.
For example, V3 will activate the fee market. You can simply understand this as Starknet will also have a fee bidding mechanism similar to the Ethereum mainnet in the future. When the network is congested, the one with the highest price will go first;
For another example, V3 will activate the payment manager (Paymaster), which you can simply understand as a more flexible fee payment mechanism that allows third parties other than the transaction sender to make fee payments;
There is actually only one sentence to describe STRK, and the original text says this:“v0.13.0 will introduce a new transaction type V3, which is designed to lay the foundation for implementing some of the features on Straknet’s future roadmap, including adding STRK as a new fee token in addition to ETH…”
Although the description is only a few words, from the extension of the announcement, we can learn more details about adding STRK as a fee token.
On October 23, Ohad Barta, product manager of Starkware (Starknet development team), submitted a proposal regarding this motion in the community governance forum.Discussion post。
Ohad appended to the post a document he co-wrote with Evyatar Oster, another Starkware product manager.Github information, which details the protocol and API updates required to add STRK as a new fee token. From this data, we can roughly learn the following information:
Adding STRK as a new fee token needs to be implemented through the new fee type V3, but the old transaction types will also coexist at the same time.Thus maintaining ETH’s continued utility as a fee token。
Use STRK to pay fees,Need to rely on the oracle to provide STRKETH real-time price feed, in the short term Starknet will use the decentralized Pragma oracle as a temporary solution, while the long-term decentralized solution needs to be implemented through future governance.
Due to the introduction of STRK in the fee collection processETH exchange and therefore may invite potential exchange rate attacks, but Starkware assesses that the potential losses faced by the sequencer and users are small, while the cost of the attack is theoretically considerable.
All in all, it can be seen from this information published three weeks ago that Starknet has long been planning to add STRK as a fee token, and has sorted out the specific specifications required for potential changes.
The actual significance of the v0.13.0 upgrade announcement last night is that,The specific timetable for this upgrade was clarified-the mainnet launch vote will be held on January 22, 2024.
However, this does not mean that Starknet will distribute STRK on a large scale before January 22 next year.Because the announcement only mentioned that V3 will be the basis for adding STRK as a fee token, the only conclusion that can be deduced is introduce V3 first, and then activate STRK as a fee token. As for whether STRK should be distributed before or after It was not mentioned, so it is not reasonable to use this as a direct basis for Starknet is about to be airdropped.
However, in a relative sense, the launch of v0.13.0 can indeed be interpreted as Starknet is gradually advancing its roadmap planning, which may also be understood as us getting closer to the large-scale distribution of STRK (including airdrops).
