PANews reported on May 9th that Ethereum founder Vitalik Buterin published an article titled "Multi-Dimensional Gas Pricing," discussing the importance and feasible path of introducing a multi-dimensional gas pricing mechanism in Ethereum. Vitalik pointed out that currently Ethereum simplifies the pricing and limits of all resources into a single dimension of Gas, which, while simplifying market design, also leads to significant efficiency losses. If the network needs to manage n different resources, a single-dimensional Gas could result in a throughput loss of up to n times. EIP-4844 introduced multi-dimensional pricing for the first time in Ethereum, adding a dedicated Blob data area with its own price and limit. This improvement reduced the cost of Rollup by 100 times, increased transaction volume by over 3 times, while only slightly increasing the theoretical maximum block size.

The article also discusses the necessity of using multi-dimensional Gas when introducing storage proofs for stateless clients. Due to quantum security risks in the Verkle tree scheme, the community is considering switching to Binary Merkle trees and STARK, but their proof generation speed is much slower. By independently pricing and limiting storage access, stability can be ensured while avoiding cost issues caused by increasing Gas prices.

In addition, Vitalik proposed two approaches to implement multi-dimensional Gas pricing: 1. The simpler approach is to set a resource cap for each transaction, valuing Gas for each transaction based on the larger of the consumed data and computational resources, as suggested by EIP-7623. 2. The more ideal but complex approach is to establish a dynamic adjustment mechanism for each resource similar to EIP-1559. Vitalik emphasized that introducing multi-dimensional execution Gas will bring some complexity at the EVM level, but for safely enhancing the scalability of Ethereum L1, this trade-off is worthwhile. The community still needs to further explore more elegant designs in terms of economic feasibility and developer friendliness.