Jumbo EthereumTransactions

[Nana-EC]

Description:
Hedera enforces a 6kb transaction limit which requires additional network complexity to support large callData
scenarios. This often means only about ~5kb is left for the transaction callData (1kb is used by signatures)
However, EVM type transactions on other EVM networks support callData sizes of up to 128kb.
This is partly because the cost of work is fully captured by gas * gasPrice on the network.

This HIP proposes to support EthereumTransaction submissions with ~5kb > callData > 128kb for increased EVM
equivalence.

Related issue(s):

Fixes #

Notes for reviewer:

Checklist

• Documented (Code comments, README, etc.)
• Tested (unit, integration, etc.)

[netlify]

✅ Deploy Preview for hedera-hips ready!

Name	Link
🔨 Latest commit	ba08caa
🔍 Latest deploy log	https://app.netlify.com/sites/hedera-hips/deploys/674500f8d28848000886e975
😎 Deploy Preview	https://deploy-preview-1086--hedera-hips.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[Neurone]

Should we consider increasing the fees for malformed EthereumTransaction accordingly with their size, i.e., from $0.0001 for 5kb up to $0.0025 for 128kb?

[rbair23]

@Neurone, I agree the EthereumTransaction fee will go up based on the number of bytes in a non-linear way. That is, 12KB should cost more than 2x the price of 6KB.

[Nana-EC]

Should we consider increasing the fees for malformed EthereumTransaction accordingly with their size, i.e., from $0.0001 for 5kb up to $0.0025 for 128kb?

Yep, my next update will include a suggestion for a tiered progressive pricing. Great minds ....

[rbair23]

@Nana-EC I think we should not include a suggestion for tiered progressive pricing. We should leave this to CoinCom. I avoided trying to get too specific because Coincom has to make that call.