For the past 45 days I have been learning Web3 concepts one per day, writing about them in public, and building a mental map of how everything fits together. I have covered blockchains, DeFi, stablecoins, zero knowledge proofs, identity, storage, DePIN, regenerative finance, and more. Around Day 46, I am starting to feel like I have enough pieces in my head to stop just learning and start actually building something. Not a full production app, not a token launch, just a small v0 project that ties together a few of the ideas I have been circling.
This is Day 46 of my 60 Days of Web3 experiment. If you are new here, you can read the full journey on Medium, checkout Ribhav on Future, and hang out with us in the Web3ForHumans Telegram at Web3ForHumans. Today's post is less "here is what I learned" and more "here is what I am going to build, and I will document it for the rest of this series."
The three big threads I keep seeing
Before I explain what I want to build, let me do a quick recap of the three main themes that have shown up over and over in this journey so far.
Money and stablecoins evolving. We started with basic stablecoins in Day 17, moved to regenerative and impact backed stablecoins in Day 42, and yesterday in Day 44 we looked at how DeFi is starting to fund real world infrastructure. The story here is that money in Web3 is not just about holding value, it is about where that value flows and what it funds while it sits idle.
Infrastructure and data becoming modular. Early on we covered things like nodes, RPCs, indexers like The Graph, and storage layers like IPFS and Arweave. Then in Day 43 we looked at DePIN, where physical infrastructure gets coordinated by tokens. The story here is that Web3 is not just one blockchain, it is a stack of composable services that you can plug together to build apps without owning all the infrastructure yourself.
Trust and identity sitting between everything. In yesterday's Day 45 piece, I argued that identity is the glue layer. It is what lets DeFi do credit and reputation, what lets DePIN filter spam, what lets regenerative projects verify impact, and what lets protocols stay open but still comply with regulations. We also covered zero knowledge proofs earlier, which let you prove things about your identity or credentials without revealing the raw data.
Those three threads keep intersecting. Money flows into infrastructure. Infrastructure produces data. Identity and reputation shape who gets access and trust. And all of it lives on blockchains that are increasingly modular, composable, and programmable.
What I want to build: a Web3 journey and impact dashboard
Here is the idea I keep coming back to. Right now, if you are active in Web3, your identity and activity are scattered everywhere. You have tokens in a wallet, you have contributed to a DAO, you have written articles or code, you have interacted with DeFi protocols, maybe you have run a DePIN node or bought impact backed assets. But there is no clean way to see all of that in one place, and there is no way to surface the story behind it.
I want to build a Web3 journey and impact dashboard that does a few simple things. You connect your wallet or ENS name, and it pulls in:
Your on chain activity. What protocols have you used, what tokens do you hold, what NFTs or credentials do you own, what DAOs or communities are you part of. This is basically a more readable, narrative version of what Etherscan or block explorers already show, but with context and storytelling instead of raw transaction logs.
Your impact footprint. If you hold regenerative stablecoins like AZUSD, if you have staked in DePIN networks, if you have contributed to carbon credit projects or other ReFi initiatives, the dashboard surfaces that and shows what your holdings are quietly funding in the real world. It answers the question from Day 42 and Day 44: "what is my balance actually funding while I sleep?"
Your builder and learning journey. If you have published articles, contributed to open source repos, earned credentials or attestations, or participated in hackathons or grants, the dashboard pulls that in too. This is the "Web3 resume" angle we talked about in Day 45. It is proof of work and proof of learning, not just proof of holdings.
The goal is not to build another portfolio tracker or another wallet UI. The goal is to build something that tells the story of your Web3 presence. Who are you, what are you building or learning, what impact are you having, and how is all of that connected?
Why this project fits the 60 day arc
There are a few reasons this project makes sense for me right now, beyond just "it sounds cool."
It forces me to integrate everything I have learned so far. To build this, I need to interact with on chain data via indexers like The Graph or RPC calls. I need to handle wallet connections, ENS resolution, and identity. I need to pull metadata from NFTs, credentials, and attestations. I need to surface DeFi positions, DePIN activity, and regenerative assets. And I need to think about privacy, since not everyone wants their full activity public. That covers most of the technical concepts from the first 45 days.
It also aligns with my own goals. I am building this 60 day journey in public partly to learn, partly to build a portfolio, and partly to show what I can do as a technical writer and builder. A dashboard that visualizes my own journey is both a useful tool for me and a proof of concept that I can ship something real, not just write about theory.
And it solves a real problem, even if the audience is small at first. A lot of people in Web3 are builders, contributors, or learners who want to show their work but do not have a clean way to do it. GitHub profiles work for code, Medium works for writing, but neither captures on chain activity, impact, or credentials in a coherent way. This dashboard could be the start of something that bridges those gaps.
What v0 will actually do (narrow scope, real timeline)
I am not trying to build a unicorn startup or a VC funded product. I am trying to ship a working v0 by the end of this 60 day series, which means I have about two weeks of focused build time after today. So the scope needs to be tight and realistic.
Here is what v0 will do. You land on a simple web page, connect your wallet via MetaMask or WalletConnect, and the app pulls in a few key data points. It shows your ENS name if you have one, or your wallet address if you do not. It lists a few protocols you have interacted with, based on transaction history from an indexer or block explorer API. It shows any NFTs or soulbound tokens you hold that represent credentials, memberships, or proof of participation. And if you hold certain tokens like AZUSD or staked DePIN tokens, it shows a small explainer of what those assets represent in terms of real world impact or infrastructure.
The output is a single page dashboard, clean and readable, with a few sections. Activity summary. Impact footprint. Credentials and contributions. And maybe a small narrative blurb at the top that you can customize, something like "I am learning Web3 in public, here is my journey so far."
That is it. No wallet for sending transactions, no live portfolio tracking with price charts, no social features or feeds. Just a static or lightly dynamic snapshot of your Web3 presence, with the option to refresh the data or update the wallet address. Simple, focused, shippable.
The tech stack I am leaning toward
I have not locked everything down yet, but here is the rough stack I am thinking about for v0. I will use a simple React or Next.js front end, since I already know enough JavaScript to get by and there are good Web3 libraries for wallet connection and on chain queries. For wallet connection, I will use something like RainbowKit or wagmi, which are clean, well documented, and handle MetaMask, WalletConnect, and other options out of the box.
For on chain data, I will start with a mix of RPC calls via ethers.js or viem for simple queries, and The Graph for more structured indexing if I need it. We covered The Graph earlier in the series, and I know it is overkill for a v0, but if I want to query things like "all DAOs this wallet has voted in" or "all protocols this wallet has interacted with," a subgraph could save me a lot of manual parsing.
For ENS resolution, I will use the ENS JavaScript library to turn wallet addresses into human readable names, and maybe pull the avatar and other metadata if it is set. For NFTs and soulbound tokens, I will query metadata via standard ERC721 or ERC1155 calls, and filter for specific contract addresses if I want to highlight certain credentials.
For the impact and DePIN layer, I will hardcode a small list of known tokens like AZUSD, Helium, Hivemapper, and a few others, and display custom descriptions or links when those tokens show up in a wallet. This is not scalable long term, but for v0 it is fine. The point is to show the pattern, not to index every single impact token in the ecosystem.
I will deploy the front end on Vercel or a similar static host, keep everything client side for now to avoid needing a backend or database, and maybe add a simple cache layer later if API rate limits become a problem. The whole thing should be lightweight, fast, and easy to iterate on.
What comes after v0 (but not in scope yet)
I already have ideas for v1 and v2 features, but I am intentionally not building them yet. Scope creep kills side projects, and I want to ship something working before I start adding bells and whistles. That said, here are a few things I would love to add later if v0 works and people actually use it.
Multi chain support. Right now I am focused on Ethereum mainnet and maybe one or two L2s like Arbitrum or Base. But a lot of people are active on Solana, Polygon, or other chains, and their activity is just as valid. Adding multi chain indexing would make the dashboard more useful, but it is also a lot more complexity.
Privacy controls and selective reveal. Some people might want to show only their credentials and contributions, not their full wallet holdings or transaction history. Zero knowledge proofs could let you prove "I have interacted with these protocols" or "I hold impact tokens worth at least X" without revealing exact amounts or addresses. That is a stretch goal, but it ties back to the ZK concepts we covered earlier.
Social and DAO integrations. If the dashboard could pull in your GitHub contributions, Medium articles, Farcaster or Lens posts, or DAO participation from platforms like Snapshot, it would give a much fuller picture of your Web3 presence. But that means dealing with multiple APIs, authentication flows, and data formats, so I am saving it for later.
Customizable narratives and templates. Right now I am thinking of one default layout, but people might want different layouts depending on whether they are applying for a grant, a job, or just showing off to friends. Templates or themes could make the dashboard more flexible, but again, that is v2 or v3 thinking.
The rest of the 60 day series will include build logs
Starting tomorrow, I am going to split my daily posts between continuing to explore new Web3 concepts and documenting progress on this project. Some days will be "here is what I learned about X," and other days will be "here is what I built, what worked, what broke, and what I am trying next."
I am treating this as a real build in public experiment, not just a thought exercise. That means I will share code snippets, design decisions, mistakes, and honest reflections on what is hard and what is easier than expected. If you are learning Web3 and want to see what building something real actually looks like, the next two weeks should be useful.
And if you want to follow along, contribute ideas, or even fork the project and build your own version, I will drop links to the repo and live demo as soon as I have something worth sharing. For now, consider this Day 46 post the kick off. The project has a name, a scope, a rough tech stack, and a timeline. Now it is time to actually build it.
If you are on a similar Web3 learning path
This note is part of my public 60 Days of Web3 journey, one concept per day, explained in human terms, with all the confusion and course corrections left in. You can read the full journey on Medium, follow Ribhav on Future, and join the community on Telegram at Web3ForHumans.
If something here feels off, incomplete, or sparks an idea, reply, quote it, or write your own version. And if you are building something similar or have ideas for what this dashboard should do, I would genuinely love to hear from you. I am learning and building in public so you do not have to do it alone.
Top comments (0)