solidity-smart-contracts

Points to note in Openzeppelin Contracts 5.0

Openzeppelin recently released version 5 of the solidity libraries. In this article, you, as a developer will get to know the imperative changes and updates. The minimum solidity version for using OZ libraries is also now bumped up to 0.8.20. You might face problems working with this version

solidity-smart-contracts

Deciphering User-Defined Operators in Solidity

An effective guide to understanding User-Defined Operators in Solidity and how they work

solidity-smart-contracts

Attention Solidity Developers, You might have missed this update

evm

EVM Part II: The Journey of Smart Contracts from Solidity Code to Bytecode - 2nd Section

evm

EVM Part II: The Journey of Smart Contracts from Solidity code to Bytecode - 1st Section

solidity-smart-contracts

How to clear storage and get incentivized by Ethereum Blockchain ?

Do you know EVM has the functionality of rewarding users with a gas refund for clearing the on-chain storage occupied by the contract data? Let’s learn more about this. There have been some changes after the London fork. But to understand it better we will look at the scenario

evm

EVM Part I: The ABCs of Ethereum Virtual Machine

Table of Contents 1. EVM in 100 words 2. EVM as a Virtual Machine 3. EVM as a State Machine 4. EVM as a Quasi-Turing Complete Machine 5. Ethereum's crucial components 6. EVM's crucial components 7. EVM Working Mechanisms 8. Summary EVM in 100 words The

solidity-smart-contracts

Part III: Custom Errors in solidity are more useful than you think

solidity-smart-contracts

Part II: Replace modifiers with private functions and reduce your contract's size

solidity-smart-contracts

Part IV: Using libraries to optimize contract size

The topic of discussion in this article series has been the ways a smart contract developer can optimize the contract’s bytecode size & never hit the threshold of 24.576 kb. So here is another crucial development pattern you can use to lower the bytecode size of your contract.

solidity-smart-contracts

Part I: Beware Solidity Devs, you might just hit your contract size limit

It's quite imperative for you as a Smart Contract Developer to always be within the pre-defined Smart Contract Bytecode size limit. Wait, What is Bytecode? 🤔 In very simpler terms, Humans understand Solidity, but EVM understands Bytecode. Bytecode is the low-level language that our solidity smart contracts (a high-level

evm

Does Etherscan display the Creation Code or Runtime Code of a Contract?

This is gonna be a quick short post on some findings regarding how etherscan displays the bytecode of a deployed and verified smart contract. After we deploy a contract on the ethereum blockchain, we know for a fact that the creation code(init code) is executed and it returns the

See all