ai-on-chain
AI agents have an multi-chain identity crisis. A crisis where the same agent exists as three different entities on three different chains and no on-chain mechanism can prove they are the same. ERC-8004 gave AI agents on-chain identity. Over 200,000 agents are now registered across 23+ chains, up from
ERC-8004 agents are fragmented. Not in theory. In production. There are ~200K agents registered across 23+ chains right now. Each one has an identity token, a reputation score, and a validation surface — all locked to a single chain's registry. An agent on Base has no on-chain relationship with
solidity-smart-contracts
Note: Read the previous part before starting: 1. Part-0, 2 Part-1 ( must-read ) With Part 1 of this article series, you've already internalized the fundamentals of ABI encoding. We’re now ready to move deeper into complex structures that Solidity developers use every day: structs, arrays, and deeply nested
solidity-smart-contracts
For Solidity developers, ABI Encoding/Decoding is THE topic to master. It's one of those topics that separates you from the rest - makes you a 10x solidity dev. On the other hand, it's a topic that could be very difficult to grasp. It's
![Why Learn Hard Solidity Things [ ABI Encoding Series: Part 0 ]](https://storage.ghost.io/c/46/35/4635d1f6-d86a-4e97-a594-818a3a258861/content/images/size/w600/2025/06/ChatGPT-Image-Jun-8--2025--07_07_45-PM.png)
solidity-smart-contracts
Solidity is EASY. It's a simple and beautiful language. With the rise of excellent educational resources, courses, dev-tools, and LLMs, learning and writing Solidity has never been easier. But here's the hard truth — if it's easy for everyone to get started, it's
move-smart-contracts
move-smart-contracts
I recently tried a new smart contract language, MOVE. The language is inspired by Rust, so it's not intuitive for Solidity devs. However, it's super fun to build with. In this article series, I aim to provide an introduction to the Move language and its features.
Simplifying Web3 and Tech for all
Special Thanks to Matt, Peter, Jasper and Mario from SEDA team, & Nam, Paul from Hyperlane team for a detailed review & feedback on the articles. The cross-chain world is evolving faster than you think. We have now officially entered the era of Interop 3.0. An era of modular
Special Thanks to Matt, Peter, Jasper and Mario from SEDA team for a detailed review & feedback on the articles. In the first part of this article, I made some strong arguments on: * the shift toward modular stacks, * how modularization creates specialists, * the rise of Verification marketplaces and verification specialists,
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.
A major shift in Web3 interoperability is around the corner. We are witnessing a massive change in how value is transferred between chains. The shift has already begun, but this is only the beginning. I have used and studied both interop models as a user and a researcher/developer—adequately
Chain abstraction is not what you think. It isn't your fault. It's easy to form wrong mental models in web3. Every new narrative brings along waves of new tweets, podcasts, articles, and typical CT debates that shape your understanding. The current hot narrative is Chain Abstraction.
There are probably a plethora of articles out there on "How to GET a web3 job" but not enough that explains How to Survive one. While it might seem just like any other remote job, there are some significant differences in a Web3 Job. Web3 is one of
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
Why this article? 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. Why not ERC165? As suggested by the name "registry contract" any
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.
WHAT? On May 13th, tornado cash governance was hacked. Let’s understand how it was possible and what the vulnerability was. 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