I wrote an X post that gained amazing traction and great insights. So much so, that I felt compelled to write this article. The post has a high signal-to-noise ratio; it was a discussion fueled by honest opinions & insights from some of the best minds in the web3 interoperability
Intent-solver systems are the silent engine behind Chain Abstraction. This is an extensive guide to understanding how intent solver system works.
OpenZeppelin recently announced changes in the upcoming version 5.1. Here are few imperative changes around Governance and ERC20. Governance Related Changes GovernorCountingSimple- The _countVotes function now returns uint256 . Previously the _countVotes function looked something like this: function _countVote( uint256 proposalId, address account, uint8 support, uint256 weight, bytes memory // params
It’s 2025... The US elections are over, and Trump is back in office... Crypto is on a bull run..the screens are glowing green...the best minds are creating amazing web3 products...web3 is on its journey to onboard the next billion users. You’ve just launched your new
As I was writing a post about ERC777, I had to explain ERC1820 as well, and in that process, I realized that ERC1820 needs a separate article. So let’s delve deeper into ERC-1820. You might be wondering why is it called a registry contract. Well, any contract or EOA
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
An effective guide to understanding User-Defined Operators in Solidity and how they work
A technical deep dive of ERC777 token standard and understanding why it failed.
On May 13th, tornado cash governance was hacked. Let’s understand how it was possible and what was the vulnerability. This post won’t be about the statistics but more about the technical route of the attack. TL;DR — The attacker mainly used CREATE, CREATE2, and selfdestruct to exploit the
smart-contracts
Solidity just released its newest version of Solidity, 0.8.20. And, as always, along with it comes quite a few new changes, improvements, bug fixes, etc. However, there is one imperative update in this version that you as a smart contract developer must be aware of. That is -
evm
If you are a Solidity developer struggling to wrap your head around the Ethereum Virtual Machine (EVM), this one is for YOU. EVM can be a tricky topic to tackle, but it's also an imperative one if you want to excel in the web3 world as a developer.
solidity-smart-contracts
evm
Featured in Week In Ethereum News [ Start Playing ] 🤾🏻♂️ * Go to Decipher EVM Puzzles github repo * Check the Installation and set-up steps * Start Playing It has been quite evident in the web3 developer space that solving puzzles, CTF challenges, games, etc are one of the most effective ways to grasp any
evm
evm
solidity-smart-contracts
Do you know EVM rewards users with a gas refund for clearing the on-chain storage occupied by the contract data? There have been some changes after the London fork. But to understand it better we will look at the scenario before the London Upgrade and then we will see the
evm
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
smart-contracts
Table of Contents Why do we witness Well-known attacks in Web3? Reason no-1 Smart Contract Security - Significance & Tools Reason no-2 Mistakes & Learnings every Smart Contract devs should experience It's been 6 years, 3months, and 25 days since the infamous DAO hack that shook the entire
solidity-smart-contracts
solidity-smart-contracts
solidity-smart-contracts
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.