Right now, when I joined a community like @FWBtweets one of the main screens I see is this:
it tells me nothing about the token really, or the community around it. To really think deeply about this and what we should show, we need to examine web2 vs web3 communities again.
In web2, the management of a community is fairly top-down and discovery is fairly shallow. The area of discovery is likely highly customized and moderated by the community leaders!
In web3, community leaders have full control of their stack. But they have less power on the largest surfaces of discovery, given the inherent composability of the ecosystem.
Given this uncontrollable surface area and much deeper discovery stack - we have our work cut out for us!
I propose trying to find the "pulse" of a token at each layer of context, to really convey information about a community much more concisely. Some starter questions:
But this matters for more than just presenting a better interface - it brings together token health with community health!
Having this data impacts three key groups:
Web3 communities can't really bankrupt like a typical company, but they can definitely still become zombies - no pulse at all. And if your token is trading actively but has no pulse/context - well thatβs a clear warning sign too.
tldr; we need to identify the right data points on tokens/communities and standardize them into an open API.
I've listed some goals for this research below. If you're interested in being a core contributor, please fill out this form by Nov 26! docs.google.com/forms/d/e/1FAIβ¦
β’ β’ β’
Missing some Tweet in this thread? You can try to
force a refresh
Many data analysts start out by querying on Dune right away. Instead, they should first learn to break down transactions, traces, and logs on any block explorer.
I've put together a new comprehensive guide for that!
Let's start by understanding the transaction tab:
You'll first need to learn to distinguish contract addresses from EOA addresses, which is normally obvious based on if there is a long hex string in the input data or not.
Thankfully, we have ABIs that define exactly how variables are encoded into functions (and logs). That means we get to read this instead!
The transaction input kicks off all of the following contract calls and logs, think of it is as the root of the action.
The memecoin craze is back, led in part by the Farcaster with coins like DEGEN, ENJOY, and HIGHER.
I created a dashboard that gives coins financial and social scores, so communities can understand how they stack up against one other and investors can better understand risks.
Generally, memecoins go through five or so life stages as they fight to be at the top.
I first created weekly score for each coin based on caster and engagement activity on Farcaster, taking into account the number of casters that have held a given token
Farcaster is taking crypto by storm, recently crossing 10k in DAUs. But how does it all work, and how can you work with the data?
I'll walk through the whole protocol and all data structures, and teach you how to query it using Dune and Neynar
πLink to guide at the end
First, you need to understand what's onchain and what's offchain.
The onchain part is split into three contracts to purely handle user registration. When a user registers, they are given an fid and custody address, as well as some storage units.
Here's an example transaction, and I've broken down this transaction in a query so you can see the Dune tables that you should use to access this data.
Our first weekly quest is live! Submit your best data work on @jokerace_xyz. This will open each week at noon on Wednesdays and close at midnight on Sundays.
You'll get to earn tokens, and get direct feedback from me and the community.
Having a Bytepass is required to participate - a snapshot is taken right before each quest.
Don't know what that is? Check out this thread explaining the Bytexplorers and how to join us.
You can submit any kind of data work. The goal here is to continuously curate the best work in the data ecosystem, while letting you build your reputation onchain.
Get those queries, dashboards, reports, scripts, tools, and models in here!
I'm launching the Bytexplorers, an onchain community for crypto data people to learn and earn together.
Anyone can join by minting a bytepass, and then participating in weekly quests.
π link to learn more and join is in my bio π
The first quest will be a set of weekly questions on
jokerace, where you can submit anything you've created. I want to see the work you are most proud of - it can be queries, charts, reports, etc.
Quests start each Thursday. You must mint a bytepass beforehand to participate.
By participating in quests like the one above, you can earn "guild tokens" and move up in "tiers". More quests on more platforms will be released over time.
The "guild token" count is the number in the bottom left of the Bytepass, and the "tier" is the symbol in the middle.
Ready to become part of the top 1% of data wizards in the Ethereum space? π§π
I've put together my most comprehensive guide on getting the most out of @DuneAnalytics , covering advanced topics and many of my own little tips and tricks.
(link to guide at the end)
If you don't already know basic SQL and how to navigate Dune tables - start with the beginners guide.
If you understand one protocol like @Uniswap v2, but cannot easily break down other protocols by yourself - you are at the right level for this guide.