zkSync, a leading Ethereum Layer 2 scaling solution, has achieved another critical milestone on its journey toward mainnet launch—just weeks after unveiling its public roadmap. The latest update, known as the Dynamic Fees Milestone, introduces a refined fee model, enhanced support for account abstraction through paymaster functionality, and compatibility with EIP-1559. These upgrades mark significant progress in fulfilling zkSync’s mission: extending Ethereum’s security and decentralization while enabling scalable, low-cost transactions.
This release brings zkSync closer to delivering a seamless, developer-friendly environment where users enjoy predictable costs and greater control over transaction fees—all powered by zero-knowledge technology.
👉 Discover how next-gen blockchain scaling is redefining user experience
Understanding Dynamic Fee Modeling
Every blockchain transaction incurs costs, and Layer 2 solutions like zkSync must balance affordability with sustainability. The new dynamic fee system ensures that operational expenses—especially those tied to publishing data on Ethereum Layer 1—are accurately reflected in pricing, without overburdening users.
Unlike traditional gas-based models, zkSync uses the term “erg”—a nod to physics, where an erg measures work done. This conceptual shift reflects zkSync’s focus on resource consumption: each transaction consumes computational resources (ergs) and generates data posted to L1, which carries its own cost.
Transaction fees are now calculated based on two key components:
- Computational cost: The amount of processing power required to validate and prove the transaction.
- Data availability cost: The L1 gas expense associated with publishing transaction data on Ethereum.
To give users granular control, three parameters define every transaction:
ergsLimit: Maximum ergs the transaction can consume.ergPrice: Price per erg the sender is willing to pay.ergsPerPubdataByte: Caps the erg cost per byte of data sent to L1.
This model enables users to set caps on how much they’re willing to spend during periods of high L1 congestion. For example, a user can specify that their transaction should not execute if Ethereum gas prices exceed a certain threshold.
While this is an initial implementation, ongoing monitoring and community feedback will guide future optimizations. The goal remains clear: keep fees as low as possible while maintaining network integrity and performance.
Paymaster Support: Advancing Account Abstraction
One of the most exciting additions in this update is paymaster support, a powerful feature inspired by EIP-4337 (account abstraction). While zkSync 1.0 allowed native ERC-20 fee payments, zkSync 2.0 takes it further by decoupling payment logic from wallet ownership.
A paymaster is a smart contract that can sponsor or subsidize transaction fees on behalf of users. This opens up transformative possibilities:
- dApps can cover gas fees for their users, offering frictionless onboarding.
- Projects can reward activity by making specific transactions free.
- Enterprises can implement customized billing models, such as batch payments or subscription-based access.
Developers can now build custom paymasters using zkSync’s SDKs and integrate them directly into their applications. Over time, this reduces reliance on ETH for gas, allowing users to transact using their preferred ERC-20 tokens—even if they hold no ETH.
👉 Explore tools that empower developers to build feeless dApps
Importantly, zkSync will not deploy a default paymaster at mainnet launch. This decision promotes decentralization by ensuring no single entity holds privileged status, encouraging a diverse ecosystem of infrastructure providers.
EIP-1559 Compatibility Now Live
zkSync 2.0 testnet now supports EIP-1559, the Ethereum improvement proposal that standardized transaction pricing with base fees and optional tips. However, due to zkSync’s unique architecture, some aspects differ from Ethereum:
- All transactions are processed first-come, first-served—no priority fees or miner tips are needed.
- Base fee mechanics exist primarily as a transaction format, not yet influencing protocol-level prioritization.
Despite these differences, this compatibility lays the groundwork for future enhancements. Upcoming updates will leverage EIP-1559 semantics to introduce features like fee forecasting, improved UX in wallets, and better integration with existing Ethereum tooling.
Additional Developer-Focused Improvements
Beyond core protocol upgrades, this release includes several enhancements aimed at improving developer experience and ecosystem inclusivity:
✅ Vyper Language Support
Developers can now write smart contracts in Vyper, a Python-inspired language valued for its simplicity and security. Sample projects are available in the official GitHub repository to help teams get started quickly.
✅ Hardhat Compiler Plugin Upgrade
The Hardhat-zksync plugin now downloads compiler binaries directly instead of relying on Docker images. This simplifies setup, speeds up compilation, and improves cross-platform compatibility.
✅ Enhanced zkEVM Behavior Alignment
Feedback from early testers has led to refinements in how zkEVM handles smart contract execution. The virtual machine now behaves more consistently with Ethereum’s execution layer, reducing unexpected behavior during migration.
✅ Wallet Troubleshooting Guidance
Users experiencing stuck transactions after network restarts are advised to reset their MetaMask wallets. Persistent issues can be reported via zkSync’s Discord or support email for prompt assistance.
What’s Next: Mainnet Countdown
With mainnet launch scheduled within 59 days, the zkSync team remains on track to deliver a secure, scalable, and user-centric Layer 2 solution. Each milestone brings the ecosystem closer to mass adoption, empowering developers to build innovative applications without compromising on cost or speed.
Developers are encouraged to begin testing on the zkSync 2.0 testnet today at v2.zksync.io. Whether porting existing dApps or launching new projects, early engagement ensures smoother integration at mainnet release.
👉 Start building on one of the fastest-evolving L2 platforms
Frequently Asked Questions (FAQ)
Q: What are “ergs” in zkSync 2.0?
A: Ergs are units measuring computational and data resources used in zkSync transactions. They replace traditional “gas” terminology to reflect zkSync’s unique resource-based pricing model.
Q: Can I use ERC-20 tokens to pay fees instead of ETH?
A: Yes—via paymaster contracts. While initial interactions may require ETH, developers can deploy paymasters that allow users to pay fees in any supported ERC-20 token.
Q: Is EIP-1559 fully implemented in zkSync 2.0?
A: Currently, EIP-1559 is supported as a transaction format. It does not yet influence transaction prioritization but sets the stage for future protocol improvements.
Q: Why isn’t there a default paymaster on mainnet?
A: To promote decentralization and fairness, zkSync avoids centralized privileges. Instead, it encourages a competitive ecosystem of independent paymaster providers.
Q: How do dynamic fees protect me during Ethereum congestion?
A: By setting ergsPerPubdataByte, you cap how much you’ll pay per byte of L1 data. If Ethereum gas spikes beyond your limit, your transaction won’t execute—protecting you from unexpected costs.
Q: Where can I find documentation for building with paymasters?
A: Full guides and code examples are available in the zkSync v2 docs.
Core Keywords: zkSync 2.0, Ethereum Layer 2, dynamic fees, account abstraction, paymaster, EIP-1559, zero-knowledge scaling, blockchain scalability