A .NET Dinosaur in Web3 — Days 11–12: Two Projects, One Stack, and What's Next
While building WishList Chain, I decided to dive deeper into transaction flows within decentralised trading systems and build something completely different. Initially, I wasn't sure about making this second project public, as building a commercial product wasn't my goal. However, I eventually decided to share it because it turned out to be a very good example of how vastly different development paths can be hidden behind the magical umbrella term "Web3."
Another Direction
While WishList Chain is a fun, game-like project focused heavily on on-chain interactions — contracts, goals, and donations — the second project approaches the space from a completely different angle. It is far more practical, real-time, and closely tied to trading and finance. The "serious stuff."
The core idea is straightforward: you follow a specific wallet, and the moment it makes a move, you get notified. Right now it can track any wallet, but the long-term vision is to track "smart money" wallets and understand patterns behind their moves, get real-time alerts on potential issues, or gain insights into why someone made a specific move.
Smart Money Tracker AI
The MVP is intentionally simple. Since this is uncharted territory for me, I focused purely on the foundational flow.
A Telegram bot monitors Ethereum wallets and fires alerts on new transactions. Instead of serving raw, cryptic data, every transaction passes through an AI layer that interprets what actually happened and why it matters.
🐋 Smart wallet activity
Wallet: 0xd8da...6045 (Ethereum)
Type: Swap · Value: ~$45,200
🤖 AI Insight: This wallet rotated a large ETH position into stablecoins.
Combined with three similar moves this week, this looks like a risk-off
signal — possibly bracing for macro uncertainty.
⚠️ Risk: Medium
💡 Actionable info: If you're holding a sizable long ETH position,
this is worth watching closely.
The bot is live and completely free.
Web: smart-money-tracker-ai-web.vercel.app
Sign up → Connect Telegram → /follow [wallet_address] → Done.
Same Stack — Different System
Both projects leverage almost identical tech stacks: Next.js, Supabase, Alchemy, Telegram, and the Claude API. However, their architectural blueprints are very different.
| Feature | WishList Chain | Smart Money Tracker |
|---|---|---|
| Core Mechanic | Users create goals and receive donations | System monitors wallets and fires alerts |
| Blockchain Role | Backend — reads and writes state | Data source — listens to events only |
| AI Role | Generates commentary on donations | Analyses transactions with risk context |
| Queue System | None needed | BullMQ on Upstash Redis |
| Trigger | User-initiated actions | On-chain events |
| Status | Testnet MVP | Live on Ethereum Mainnet |
Shifting Perspectives
My biggest takeaway was realising that Web3 is far from a single, standardised tech stack. It's an expansive, often chaotic ecosystem where you can design fully on-chain systems, launch hybrid architectures, or treat the blockchain merely as an immutable data feed. Navigating these fluid standards felt like entering uncharted territory.
Yet, to my surprise, my .NET background proved highly transferable. The same engineering principles still apply — event-driven design, separation of concerns, modularity. The syntax required an evolution. The core architectural patterns did not.
Current State
Both projects are functional MVPs, but still quite raw.
WishList Chain — on-chain goals, donations, DreamPower mechanics. What's next: donation history, analytical dashboards, refined DreamPower logic.
Smart Money Tracker — real-time wallet tracking, AI commentary, Telegram alerts. What's next: multi-chain support (Base + Arbitrum + Solana), smart wallet discovery, weekly digest summaries.
I won't stop working on either — both deserve to grow. The plan is to ship new features for each project roughly twice a week.
Next Step — Back to Contracts
After building infrastructure around contracts, I want to go deeper into the smart contracts themselves. The next chapter: 7 days — 7 contracts — 7 articles.
Day 1 — Access Control (Ownable, Modifiers)
Day 2 — Escrow & Pull-over-Push Pattern
Day 3 — DAO Voting Systems
Day 4 — ERC-20 Token Implementation
Day 5 — Staking Mechanisms
Day 6 — ERC-721 NFT Basics
Day 7 — Reentrancy Protection & Security
All repositories are open source: github.com/alena-dev-soft
Follow the journey on Telegram: t.me/dotnetToWeb3
Stage: Dinosaur 🦕 — two systems live. Now going deeper into the bedrock.
Top comments (0)