Replies: 1 comment
-
In the zkSync Era, while the EIP-1559 transaction format is indeed supported, the specific parameters Here's a breakdown of how this works in zkSync Era:
Regarding your question about sending a transaction with only a legacy gas price value, in zkSync Era, such a transaction would not treat the legacy gas price as a base fee. Instead, the transaction would likely be processed using the standard fee mechanisms that do not utilize the EIP-1559 model. As for future plans to start using For the most accurate and up-to-date information, you might want to follow official zkSync communications or reach out directly to the development team for insights into upcoming features and changes in the fee structure. Your feedback helps us serve you better. If this fully addresses your question, please give it a thumbs up. If it doesn't, please give it a thumbs down. This will inform the community and team so we can improve our support. |
Beta Was this translation helpful? Give feedback.
-
Environment
Testnet
Provide a brief description of the functionality you're trying to implement and the issue you are running into.
In this document, it means that
In ZKsync Era, while the EIP-1559 transaction format is supported, the maxFeePerGas and maxPriorityFeePerGas parameters are not utilized.
Can you explain more about this? Does it literally mean that only the base fee is supported? If so, any plans to start using them?
If a tx is sent with only legacy gas price value, will zksync treat it as a base fee value?
Repo Link (Optional)
No response
Additional Details
No response
Beta Was this translation helpful? Give feedback.
All reactions