After two weeks on the Amoy testnet, the Ahmedabad upgrade will go live on mainnet at block #62278656. At the current rate, that block height is expected to be reached on September 25.
Collectively, this upgrade brings improved developer and user experience:
- Changes token symbol on Polygon PoS from MATIC to POL, as well as WMATIC to WPOL;
- Enables developers to build more complex contract deployments and logics with increased code size, from 24KB to 32KB
- Saves stuck bridge transactions by allowing a replay of failed state syncs, improving observability of the network’s plasma bridge.
The Ahmedabad Hardfork (PIP-37) includes three Polygon Improvement Proposals:
All node operators including infra providers and validators have already upgraded to the latest version of Bor (>= v1.4.0) and Erigon (>= 2.60.8).
What’s in Ahmedabad?
PIP-30 increases the max code size from 24KB to 32KB, allowing dApp devs to deploy more complex contracts without resorting to alternative (and less direct) development patterns.
PIP-36 addresses a gas pricing issue that followed Ethereum’s Berlin hardfork and which caused certain POL (formerly MATIC) transactions to be locked in the plasma bridge. PIP-36 patches the bug and makes it possible to replay failed state syncs, improving overall observability of the network’s plasma bridge.
Finally, PIP-45 follows the recent (and highly anticipated) POL migration to change the token symbol of the native token on PoS from MATIC to POL. and WMATIC to WPOL.
FAQ
Do dApps or users need to take any action?
No, dApp devs and end-users do not need to take any action.
***
Tune into the blog and our social channels to keep up with updates about Polygon.
The future of Web3 is aggregated.
Website | Farcaster | X (Twitter) | Forum | Telegram | Discord | Instagram | LinkedIn | Polygon Knowledge Layer
.png)
.png)
%20(1).webp)
.webp)
