The problem WalletScore solves

Over the past year, NFT's have witnessed a cambrian moment — generating US$18.5 billion in 2021 and US$24.3 billion in 2022. NFTs have witnessed a significant uptick in adoption with traditional web2 enterprises such as Adidas and Puma, to Coca-Cola and Burger King to Reddit and Meta experimenting with the asset class across their product offerings. Further, over the coming month, Porsche, Game of Thrones and ToysRUs will foray into the web3 space with the launch of their respective NFTs.

Whilst the current NFT value stack is comprehensive with several innovations and unique value propositions, it is highly primitive and disaggregated. Chief amongst the available whitespace is in distribution. In simple terms, creators and enterprises are unable to identify, evaluate and communicate with their potential primary minters. This is further exacerbated by way of the anonymity behind the respective wallets; leading to the creation of WalletScore.

WalletScore is a compact solution providing enterprises with a range of wallets curated to fit specific themes. Looking for proven long term diamond hands? We got'chu. Need flippers to help drive short-term volume? We got'chu. Seeking wallet heavy whales? We got'chu. On the hunt for the most loyal otakus? That's right, we got'chu.

Simply put, WalletScore scours the chain — categorising wallets based on available on-chain data whilst simultaneously providing a list of hierarchically ordered wallets based on specific pre-requisite criteria. Further, by integrating Push Protocol, we are not only able to ascertain said wallets but additionally communicate with them.

Gone are the fears of never minting out.
Why?
Cause WalletScore has got'chu.

Challenges we ran into

1. We initially sought out to have 50+ thematic categorizations on the basis of 200+ metrics. However the paucity of non-tokengated marketplace APIs was a significant hurdle that we were unable to overcome due to financial constraints (>USD $1,000.
2. In addition, the collation of the requisite data sets was extremely arduous due to API rate limits.
3. Lastly, whilst Push Protocol serves as a viable communication solution, it requires both — the enterprise AND the primary minter/consumer to have installed and have a functioning Push account; functioning as a significant barrier towards frictionless mass adoption.