Crypto Analytics: Exploring Uniswap v3 Data
Analyzing User Behavior for Uniswap's v3 Launch
I tweeted out this post over the weekend before sharing over email and it went semi-viral (by my standards). Read on below:
A few weeks ago, I published my first crypto-related blog post: Bring Your Own Wallet: The Future of Consumer Choice and Personalization on the Internet
Since then, I’ve continued to fall down the rabbit hole. So much so, that this post is probably 100 steps more advanced than my first post. So apologies for that, but the place I’ve gotten to now is too exciting to not share.
The Plunge Into Work
As I progressed down the rabbit hole, I joined crypto project’s Discord channels, read through forums and governance posts, and (my favorite) checked out their analytics dashboards. I have some experience from my day job building dashboards, and a ton of strong opinions about dashboard design, so I figured that this could be a spot for me to try. 99.9% of the dashboards I saw were from Dune Analytics, so I signed-up on the day of an ETH all-time high (which I thought was good timing), and off I went.
A Dashboard is Born — Uniswap v3
A very fortunate coincidence was that this happened to also be a few days before Uniswap’s highly anticipated v3 launch (read more here). Within a few hours (minutes?), the Dune team had parsed the Uniswap v3 contracts and made the data available for people like me (SQL is more my speed).
There were a few burning questions I had going into the launch: How does this impact how much Uniswap is used? Does v3 impact what pairs Uniswap is used for? Where is and isn’t v3 being adopted?
A few hours later, I started getting some answers:
Now, enough of my personal journey. Time to answer some of the questions that you all are here for.