> For the complete documentation index, see [llms.txt](https://kami-1.gitbook.io/kami/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kami-1.gitbook.io/kami/utility/project-eclipse.md).

# Project Eclipse

## Enter Eclipse

Eclipse is a software solution designed to enhance the experience of NFT collectors and holders across all blockchains. 

With Eclipse being the first of our products, it will not be gatekept to just holders or blockchain (although Kami holders will have exclusive benefits for Eclipse). Its purpose is to be accessible and utilized by all Web3.

We aim to transform the way we interact with our NFT collections, by offering new possibilities to showcase and connect with the Web3 community. 

{% hint style="info" %}
Our conviction is, Eclipse will have a positive impact on the entire NFT ecosystem, providing a unique and innovative approach to collecting, showcasing, and networking.
{% endhint %}

## Goal of Eclipse

Our goal is to provide a comprehensive and visually appealing platform for your NFTs, social media, and links, while seamlessly integrating the capabilities of Web3 technology. 

## A Lean Startup Approach

Our plan is to launch the MVP version of Eclipse shortly after mint. Our holders will be the first to use Eclipse and we will start to generate the *Build-Measure-Learn* feedback loop. 

{% hint style="info" %}
MVP - Minimum Viable Product, a product with basic features to attract early-adopter customers and validate a product idea.
{% endhint %}

We are adopting this model because arguably, the majority of people that are invested in the Crypto/NFTs space are considered [*'early adopters'*](#user-content-fn-1)[^1]*.* Early adopters are the best at testing new products and providing feedback. We want to capitalize on this and build Eclipse quickly whilst constantly testing new features and adjusting them accordingly to demand.

The Goal of the lean starting approach is to create a product that has the perfect amount of features to entice early adopters and validate a product concept during the early stages of product development. 

<figure><img src="/files/DG4eE428HciBqTpdg7XH" alt=""><figcaption></figcaption></figure>

## Example:

<figure><img src="/files/gmPAvDF6YxUvg7tWiPkE" alt=""><figcaption></figcaption></figure>

## 6 Steps for Eclipse

1. **Define our user base:** Identify who our target users are, what their needs are, and how our platform can address those needs.
2. **Identify the core features:** Determine what the essential features of our platform are that will provide the most value to our users.
3. **Build the Minimum Viable Product (MVP):** a basic version of our platform with the core features from step 2. Make it look good, easy to use, fully functional, and capable of solving our users' most pressing issues.
4. **Test and gather feedback:** Launch Eclipse to a small group of users and gather feedback on their experience with the platform. This feedback will help us identify areas for improvement, refine our product roadmap, and prioritize new features to add.
5. **Refine and enhance:** Take the feedback we receive and make iterative enhancements to our platform. This might involve adding new features, improving current ones, or streamlining the user interface to make it more user-friendly.
6. **Launch and scale:** Once we have a solid product that meets the needs of our users, we can launch it to a wider audience and scale up our marketing efforts to attract more users.

{% hint style="info" %}
Our production process is crucial because we don't create individual product components and wait until the end to make users happy. Instead, we focus on developing a self-sufficient and fully functional product that can evolve over time with ideas, feedback, and enhancements. This iterative approach ensures that users are continually satisfied with each product improvement.
{% endhint %}

[^1]: Early adopters are those individuals that use new products before the majority of people. They are risk-takers, trendsetters and willing to test things before it is prefected.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://kami-1.gitbook.io/kami/utility/project-eclipse.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.