-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should we support EIP-4844? #5810
Comments
@3for The previous discussion, which you can continue here: |
As discussed in Meeting 16, TRON currently does not have a prosperous rollup ecosystem. Secondly, EIP-4844 is a relatively ambitious project and may take up more development resources and time. I think we should first evaluate the ecological status, the priority of this function, and the difficulty of implementation. Then make a conclusion based on the overall status quo. Is there any new progress so far? Can the discussion be continued at the next meeting? @3for |
We should prepare for the future. No new progress so far. |
@3for I guess due to the current low fee of tron transaction and current TPS meeting the needs of most situations, Tron maybe don't have enough motivation to implement the eip. The complexity of the eip maybe another important reason, as everyone knows, Tron's technological strength is much inferior to Ethereum's. |
Background
EIP-4844 , also known as proto-danksharding, so end-users are expected to benefit from lower gas fees on layer two (L2) transactions following proto-danksharding.
EIP-4844 introduces:
EIP-4844 will influence the tx fees of L2 rollups ecosystem on TRON. EIP-4844 is expected to reduce tx fees by 2X - 5X according to Polygon team evaluation.
Rationale
Rollups are in the short and medium term, and possibly in the long term, the only trustless scaling solution for Tron. We have already deployed TRON zkEVM testnet based on Polygon zkEVM technology. So we should consider to support EIP-4844 to decrease the tx fees for Tron zkEVM and future L2 rollups ecosystem.
The text was updated successfully, but these errors were encountered: