Tunester

home
about
data flow
product demo
discover page
artist page

Inspiration

We enjoy collecting music NFTs and supporting artists on their web3 journey, but we also want to make returns on our collections. It's difficult to get a holistic perspective on who the artist is both in web2 and web3 to better inform our collection strategies.

What it does

A collector can view an artist's profile with various web2 data (Spotify streams, social following) and web3 data (total nft sales, top 10 collectors, discography across multiple platforms).

How we built it

The backend is built on a combination of Web3 and Web2 tech. To obtain the data metrics needed for our dashboard (drops, unique collectors, and artist data) we scraped on-chain data from the Sound.xyz, Audius, Glass.xyz, and OpenSea subgraphs using GraphQL. Then we used their APIs to obtain metadata from their databases to supplement our on-chain information. Lastly, we scraped from Web2 social media sources, Spotify and Twitter, to get more information on the artist’s popularity. We constructed a subgraph to query the information we gathered. The most complete source of information is a traditional web2 database.

The front end is built with React, Next.js, GraphQL, TailwindCSS, and MaterialUI. We use GraphQL to query the data we gathered and compiled on and off-chain, and build it into a user-friendly UI.

Challenges we ran into

Music NFT metadata standards are a mess. It was hard to aggregate numerous platforms due to lack of standardization in artist and edition identifiers, and the fact that metadata is often stored off-chain and is non-trivial to collect. We ran out of time trying to piece multiple chains and subgraphs into our frontend.