[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/css/ - CSS Masters

Advanced styling, animations & modern CSS techniques
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1766843819098.jpg (162.24 KB, 1080x721, img_1766843809442_c2la2a61.jpg)

7e88a No.1005

Just a heads up y'all! I was digging into some Solidity stuff and came across an interesting tidbit about the max bytecode size when deploying ETH smart contacts. It turns out, we got ourselves limited to just 24 KB (that's 24576 bytes for us tech-heads) due to Ethereum Improvement Proposal -170! If your compiled contract exceeds this size during deployment transaction? Well… *insert epic fail GIF here*. The limit applies only to the final deployed bytecode, not temporary code that runs just once like constructor or whatnot. So keep it lightweight and compact when deploying smart contracts on Ethereum! Anybody else tried pushing those limits? I'm curious if there are creative workarounds for handling larger contract sizes without breaking the bank (or blockchain) in terms of gas fees… let me know your thoughts

Source: https://dev.to/mihaihng/ethereum-solidity-quiz-q6-what-is-the-max-bytecode-size-for-smart-contract-deployment-on-4h3o


[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">