DEV Community

Cover image for A .NET Dinosaur in Web3. Day 6 - Wishlist or… “Dream Coins True”?
Alena
Alena

Posted on • Originally published at Medium

A .NET Dinosaur in Web3. Day 6 - Wishlist or… “Dream Coins True”?

#web3 #dotnet #beginners #ethereum

There's something that happened between Day 5 and Day 6 during brainstorming about project ideas. Day 6 wasn't just a deploy session — it was the first day of building something real.

Intro

Brainstorming started as a strategy question — I needed a practice project. Something to learn the full modern Web3 stack and something I could build in public.

I already have another idea that I've started building, but until the MVP is ready — I decided to keep it under wraps.

The idea was simple: pick something "common", but complex enough to cover real technical ground.

Well… I'm a dreamer. So the wishlist idea just felt right.

I started thinking — is it possible to build something interesting around it? Maybe the idea isn't new. It doesn't really matter… I just like it.

Take a wishlist, let people make each other's dreams come true and… maybe build something on-chain around it.

The base Wishlist contract was already written. It was already there — a working smart contract with a React frontend deployed on Sepolia.

So why not just build something on top of it?

Multi-user goals, ETH donations for specific goals, a Telegram bot for notifications. A proper monorepo with contract, Supabase, Drizzle, Next.js, and more.

And then the idea shifted.

What if every donation increases the "strength" of something?

A global counter. An on-chain kind of energy. A number that grows every time someone believes in someone else's dream enough to send ETH.

The working name became WishList Chain (WSHL) — not a token, at least not yet. An on-chain power score. totalDreamPower in the contract. Every donation adds to it. Every goal has its own dream power.

(DreamCoin, the name I originally wanted, is apparently already taken — so I had to rethink pretty quickly.)

Is it a real product? Possibly. Is it a learning project? Definitely. Is the idea somewhat ridiculous? Yes, and that's exactly why it might work in crypto.

The project is at github.com/alena-dev-soft/wish-list-chain — open source.

Day 6 was about laying the foundation for all of it.

The Goal

Write the core contract for WishList Chain — version 3 of the original Wishlist.sol.

Multi-user goals, ETH donations, dreamPower accumulation per goal, totalDreamPower globally, and a DreamPowerIncreased event for future Alchemy webhooks. Deploy with Hardhat. Verify on Etherscan.

The Contract

WishlistV3 is a different architecture from V2. V2 was one owner, one wishlist. V3 is a shared contract where every wallet has its own goals.

The .NET analogy:

// V2
List<WishItem> wishes;

// V3
Dictionary<address, List<Goal>> goals;
Enter fullscreen mode Exit fullscreen mode

In Solidity: mapping(address => Goal[]) public goals

struct Goal gained financial fields:

struct Goal {
    string name;
    uint256 targetAmount;
    uint256 currentAmount;
    uint256 dreamPower;
    bool isFulfilled;
    uint256 createdAt;
}
Enter fullscreen mode Exit fullscreen mode

donate() is the core function. Two things worth noting:

It must be payable — without that modifier, Solidity won't accept ETH. The keyword is required, not optional.

Goal storage goal = goals[_owner][_goalIndex] — storage means you're working with the actual on-chain data, not a copy. Change it, and the state changes. Use memory instead, and you're editing a local copy that disappears after the function returns. This distinction doesn't exist in .NET — it's specific to the EVM execution model.

The event:

event DreamPowerIncreased(
    address indexed owner,
    uint256 indexed goalIndex,
    uint256 addedPower,
    uint256 newTotalPower
);
Enter fullscreen mode Exit fullscreen mode

indexed parameters are searchable in logs. They become filter keys — Alchemy webhooks can listen for specific owners or goal indices without scanning every event. The non-indexed parameters are just data payload.

Hardhat

Moving from Remix to Hardhat is the next step in my Web3 journey. Remix is a great tool for exploration. Hardhat provides everything needed out of the box, including a proper build pipeline.

The setup that actually works with Hardhat 3 + viem:

npm install --save-dev hardhat@latest @nomicfoundation/hardhat-toolbox-viem@latest
Enter fullscreen mode Exit fullscreen mode

I really like this part — deploy and verify in one command:

npx hardhat ignition deploy ignition/modules/WishlistV3.ts --network sepolia --verify
Enter fullscreen mode Exit fullscreen mode

Fair warning: getting there involved the usual package dependency hell — wrong versions, renamed config keys, cached artifacts. Nothing mysterious, just the standard tax you pay any time you touch a stack that lives and dies by npm. Read the error codes, fix one thing at a time.

The Project

WishlistV3 is not just a learning exercise. It's the core contract for something that's being built. The donate() function, the DreamPowerIncreased event, the multi-user architecture — all of it is designed for a real use case that will be revealed when the MVP is ready.

Two-week sprint. This was the foundation.

Contract address: 0x90de4a1934d0B062423adAEeDEe37Bb6fD12D0Ca

Verified: sepolia.etherscan.io/address/0x90de4a1934d0B062423adAEeDEe37Bb6fD12D0Ca

Stage: Dinosaur 🦕 — dependency hell survived. Foundation is live.

Top comments (0)