# 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?
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!
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.phi.box/explore-phi/introduction/our-journey.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.