# Founder's Notes

GM!

I'm Chewbacc◎ and I would like to firstly thank you for taking the time to read through what we have written here. As fate would have it, Gab and I met nearly 7 months ago in the search for a higher calling in the space. It has been an exhausting yet rewarding 7 months, putting together our combined knowledge of what we know as "Solana NFTs" to create what we have today. We are also extremely grateful to all the friends we have made in the community as well as the help we've gotten thus far.

This project, as new as it might seem, has been through several ups and downs, 3 major changes to our art (scrapping and redoing), 5 iterations of our roadmap, a couple of bulls and bears, days worth of calls, even a few “Are we ever gonna make it?” questions but here we are, ready and raring to go. A quick insight into certain things related to the project:

What type of project are we?

In the current NFT market, there are two main choices for any project founder, a Utility Driven or Community Project. A utility driven project such as a revenue share platform, a whitelisting tool, or even a casino does have its merits. But a utility driven project would also mean intense competition of speed and value against competitors (both directly and indirectly), possibly being outdated/out-cycled by the time you mint, as well as the need for strong technical experience from the project leads.

The second option, a Community Project. More specifically, an Art-Focused and Community-Centric Project was the more obvious choice for us as it gave us the following:

1. A community grows over time, whereas utilities/tools are continually being made redundant and replaced as the ecosystem grows. A community driven project provides longevity and sustainability.
2. Original art forms the core identity of our project. It has been proven that good art gives the project team a greater foundation to build upon. For example, in the form of branding, storylines or a persona that the community resonates strongly with.
3. Despite what was said earlier about utility, an Art & Community project gives us the flexibility to create various utilities that are relatable to both the project and the market. We deem utility as more of a feature of the project than a niche. Ultimately, we aim to be seen as a project with captivating art and a strong community.

With that being said, we decided it was best for us as founders of the project to apply a more hands-on approach with our community ; to actually connect with the community rather than leaving it in the hands of hired moderators or community managers. Of course, this took up a substantial amount of time out of our schedule but on balance we feel the efforts will go a long way in creating the foundations of success for our project.

Our Vision,

> We aspire to establish a "*forever space*" for communities to partake and thrive in together.

was written with a certain level of personal emotions involved. Irregardless of the changes made to our roadmap, art or even the ever-changing market, this Vision has always stood tall and strong. To us, creating a home for our community to experience and grow together will be an achievement no other project can top.

And so, there we have it. Our motivation for Stellar Drifters. It has been a lengthy piece thus far, thank you once again if you have read it up till this point. We will now allow the rest of the Stellar Papers and our actions speak for ourselves.

CHEERS,

Chewbacc◎ :heart:&#x20;


---

# 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://stellar-drifters.gitbook.io/stellar-papers/about/founders-notes.md?ask=<question>
```

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.
