BackTabCrypt / Writing
Web3 /

My Journey into Web3 Development

Jan 2026 · 5 min read

I was building React apps, calling REST APIs, the usual stuff. Happy with it. Then someone in a Discord server I was barely active in dropped a link to a Solidity tutorial with no context. I clicked it at like midnight because I had nothing better to do. That was genuinely how it started. No grand plan.

The Part That Messed With My Head

Solidity the language wasn't that hard. What messed with me was the mental model underneath it. In every web app I'd built, there was a server somewhere. A database somewhere. You could change things. Roll back a deployment. Fix a bug with a hotfix. In Web3, once you deploy a contract, it's there. You can't edit it. You can't delete it. The bug you shipped is now a permanent part of the chain.

That scared me a bit at first. Then I started to appreciate it. It forces you to actually think before you deploy instead of deploying and then thinking. I wish more Web2 projects had that pressure honestly.

My First Real Project

First actual Web3 thing I built was a Sui NFT Mint DApp. I was learning Move and JavaScript at the same time, which was chaotic. Move has this strict ownership model where every object has exactly one owner and you can't just pass things around freely. Sounds annoying. Is annoying. Also is exactly what makes trustless systems possible, which I only understood weeks later.

  • Wallet = identity, not just payment — that shift in thinking took a while
  • Every state change needs a signature — there's no silent update
  • Gas is real money — explaining this to users is its own challenge
  • Your frontend still talks to servers — just not your servers

Finding Monad

Sui was great but I kept running into the ecosystem problem — most of the DeFi world runs on EVM. So I started looking at EVM-compatible chains. Monad came up because of one thing: parallel transaction execution. Normal EVM chains process transactions one at a time. Monad runs them in parallel. Same Solidity, same Hardhat toolchain, but the throughput is a different world. For a college student who doesn't want to relearn everything, that compatibility mattered.

I built MonConnect on Monad testnet — escrow payments between event organizers and service providers, with NFT-based identity. That project was where I actually started understanding smart contract architecture rather than just syntax. There's a big difference.

Where I'm At Now

I don't think Web3 replaces Web2. Most apps don't need a blockchain. But for specific things — where strangers need to transact without trusting each other, where you need rules nobody can change — it's the right tool. That's a smaller category than the Web3 hype suggests, but it's a real one.

If you're a Web2 dev curious about it: deploy a simple NFT contract on a testnet. Break it. Read the transaction receipt. Go from there. The community in this space is genuinely some of the most technically engaged people I've met.