# Our journey

Our founder, Shugo, embarked on his journey with his co-founder in January 2021, driven by a question: How can users uniquely express their onchain identity?

<figure><img src="https://2819029275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN3SP59WsdH4ATy0OAWIv%2Fuploads%2FERM2deZmqC07vjkUktpx%2Fimage.png?alt=media&#x26;token=ee36d318-75e2-4409-aa62-e21df3681e99" alt=""><figcaption></figcaption></figure>

This led to the creation of [Phi Land](https://philand.xyz/), a casual metaverse that visualizes onchain activities on ENS in a visually captivating format designed by [eBoy](https://www.eboy.com/), a world-class pixel artist and also co-founder of [Nouns DAO](https://nouns.wtf/). As you know, Phi Land allows users to claim adorable NFTs based on their onchain transactions, and build their [#philand🏝](https://twitter.com/search?q=%23philand\&src=hashtag_click) to showcase their identity.

Over the last year, Phi Land has gained significant traction:

* Over 4.1 million Phi NFTs were minted.
* Engaged more than 296k+ unique users (including over 163k+ unique wallets).
* Collaborated with 65+ protocols

Our team is pleased to see many people sharing their [#philand🏝](https://twitter.com/search?q=%23philand\&src=hashtag_click) on the timeline. The goal was to visualize onchain transaction data uniquely. In this vision, users would utilize PhiLand as their onchain profile, creating a seamless connection between their digital identity and blockchain interactions.

This approach not only personalizes the blockchain experience but also integrates it into a broader social context, bridging the gap between transactional data and personal expression.

While PhiLand has successfully achieved its initial goals, we're eager to expand and enhance your experience even further!

<figure><img src="https://2819029275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN3SP59WsdH4ATy0OAWIv%2Fuploads%2F3gu4IEy8PDbxIjZXRXg6%2Fnapkin-selection%20(2).png?alt=media&#x26;token=0c3c5643-5be1-4522-ab13-3fd17237dfdb" alt=""><figcaption></figcaption></figure>
