A .NET Dinosaur in Web3. Day 11-12. Two projects, One Stack and What’s Next
The article discusses the author's experiences during Days 11-12 of their Web3 project journey. They developed two distinct projects, WishList Chain and Smart Money Tracker AI, each utilizing similar technology stacks but serving different purposes. The author reflects on the diverse possibilities within the Web3 ecosystem and how their .NET background has been beneficial in this new domain.
- ▪The author created two projects: WishList Chain, focused on on-chain interactions, and Smart Money Tracker AI, which monitors wallet transactions.
- ▪Smart Money Tracker AI provides real-time alerts on wallet activities and uses AI to interpret transaction significance.
- ▪Both projects utilize a similar tech stack, including Next.js and Supabase, but have different architectural designs.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/alenadevsoft/a-net-dinosaur-in-web3-day-11-12-two-projects-one-stack-and-whats-next-35kb |
| Publication time | Mon, 25 May 2026 13:00:00 +0000 |
| Retrieval time | 2026-05-25T13:07:37.303Z |
| Last seen | 2026-05-25T13:07:37.303Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | enWH_4ynZnuN · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3908355) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Alena Posted on May 25 • Originally published at Medium A .NET Dinosaur in Web3. Day 11-12. Two projects, One Stack and What’s Next #ethereum #smartcontract #blockchain #web3 A .NET Dinosaur in Web3 (10 Part Series) 1 A .NET Dinosaur in Web3. Day 1 - First Smart Contract 2 A .NET Dinosaur in Web3. Day 2 - Access Control ... 6 more parts... 3 A .NET Dinosaur in Web3. Day 3 - Voting, Sybil Attacks and Identity 4 A .NET Dinosaur in Web3.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).