Thread by @zksync

73 days to zkSync 2.0 on mainnet. The next roadmap milestone is Dynamic Fees and today we’re releasing a definition of what it’ll include. Next week we’ll release the exact date. Heads up to developers on testnet, this release will be a regenesis event. #marchtomainnet

🧵 (1/7)

Dynamic Fees

Today, all transactions on zkSync 2.0 testnet cost a fee that's independent of transaction logic & respective L1 cost. Our new fee model is similar to Ethereum's with L2-specific modifications. Each transaction will be priced based on the resources consumed.

(2/7)

Dynamic Fees (cont’d)

To differentiate from the standard “gas,” our measurement unit is called “ergs.”

Ergs pay for:

1. Transaction execution & proof generation
2. L1 storage use
3. Proof verification on L1
4. Additional L1 interactions

(3/7)

Removing Variant Token Payments

This milestone will remove support to pay fees in variant tokens. This should only affect developers. The change should not be noticed by users because…

(4/7)

Account Abstraction Support for Paymasters

Users will be able to pay in different tokens directly to a ‘paymaster’ – who would then convert it into ETH for system compatibility.

Background: medium.com/infinitism/erc…

(5/7)

EIP-1559 Support

The same burn mechanism used by Ethereum L1 will be used in zkSync 2.0. This will be switched off initially (think of transaction tip as a system constant), as we don’t prioritize transactions with higher fees.

More on EIP-1559: eips.ethereum.org/EIPS/eip-1559

(6/7)

If you’re interested in porting to or launching on zkSync 2.0, get started by joining our testnet: v2.zksync.io

(7/7)