There's this new approach pushing boundaries with calldata that deserves attention.
Over a year back, someone called it "Ethereum Reciphered" - basically challenging the old-school ecosystem with alternative micro-architectures.
Think about it: why lock ourselves into just RLP contract calls when there's 96kb of calldata space sitting there? The potential for leveraging that room differently is wild.
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
14 Likes
Reward
14
7
Repost
Share
Comment
0/400
ChainChef
· 12-12 11:45
ngl 96kb of untapped calldata space is like having a fully stocked pantry and just making toast... the recipe potential here is actually insane. ethereum's been way too rigid with its plating standards imo
Reply0
GweiWatcher
· 12-10 21:29
It's really a pity to waste 96kb of bandwidth; someone should have fixed this a long time ago.
View OriginalReply0
BitcoinDaddy
· 12-10 07:57
96kb is wasted like this, it's really a bit incomprehensible
View OriginalReply0
YieldHunter
· 12-10 07:49
honestly, 96kb sounds massive on paper but have you actually calculated the gas cost-benefit here? technically speaking, if you're burning more compute cycles for marginal throughput gains, that's just yield farming with extra steps lol
Reply0
FUDwatcher
· 12-10 07:46
96kb of calldata space is wasted like this? Someone should have tossed this a long time ago
There's this new approach pushing boundaries with calldata that deserves attention.
Over a year back, someone called it "Ethereum Reciphered" - basically challenging the old-school ecosystem with alternative micro-architectures.
Think about it: why lock ourselves into just RLP contract calls when there's 96kb of calldata space sitting there? The potential for leveraging that room differently is wild.