Ethereum Wrapped
Your on-chain year in review, decoded with data.
Created on 24th January 2026
•
Ethereum Wrapped
Your on-chain year in review, decoded with data.
The problem Ethereum Wrapped solves
Ethereum is transparent, but it’s not friendly.
All your transactions, tokens, and contracts are public, yet understanding what they actually say about you is hard. Most users only see endless tables on block explorers and have no simple way to answer questions like:
How active was I on Ethereum this year?
Where did I spend most of my gas?
Am I more of a builder, trader, or explorer?
Because of this, people often know what they did on-chain, but not what it means.
Ethereum Wrapped fixes this gap.
Instead of raw data, it gives users a clear, personalized summary of their on-chain journey inspired by Spotify Wrapped. By analyzing transactions, ERC-20 transfers, and contract interactions, it turns complex blockchain activity into simple insights and stories.
Users can instantly see:
Their activity trends over time
Gas fees and efficiency
Most-used tokens and contracts
Active streaks and milestones
A Web3 persona that reflects their behavior
The goal is simple:
To make Ethereum data understandable, relatable, and fun, without requiring any technical knowledge while still being powerful enough for developers and analysts.
Challenges we ran into
One of the main challenges was connecting the backend and frontend smoothly.
The analytics pipeline was built using Flask, which meant designing a clean API that could return complex, nested blockchain insights as JSON. Since each wallet summary involves multiple analytics results, structuring the response in a way that was both flexible and easy for the frontend to consume required several iterations.
On the frontend side, parsing and handling this JSON data was not trivial. Mapping raw backend responses into meaningful UI components, handling loading states, and ensuring the data remained consistent across different sections of the “Wrapped” experience took careful coordination between both sides.
Another challenge was debugging issues related to HTTP methods, API routes, and CORS configuration. Small mismatches between frontend requests and Flask endpoints initially caused errors that were not obvious at first glance. These were resolved by carefully aligning request formats, enabling proper cross-origin access, and testing the API independently before integrating it into the UI.
Overall, this process helped me gain a much deeper understanding of API design, JSON data flow, and full-stack integration, which played a key role in shaping the final project.
Tracks Applied (1)