> For the complete documentation index, see [llms.txt](https://whitepaper.memetheftauto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.memetheftauto.com/the-founder/sb-on-them-nfts.md).

# SB On Them NFTs

Many in the Web3 space know me as SB On Them NFTs. I began my crypto journey in late 2020, drawn to the explosive growth of the NFT market. Eager to learn and succeed, I immersed myself in the space, quickly recognizing a critical gap: effective marketing strategies were essential for projects to thrive.

With a Bachelor of Science in Entertainment Business, with an emphasis in Marketing from Full Sail  University, I leveraged my expertise to fill that need. I initially served as a partnership manager for multiple projects, then expanded my role to include advisory, creative strategy, and conceptual development.

Over the past four years, I’ve contributed to the growth of dozens of Web3 projects, including notable names such as Asset Dash, Stoned Ape Crew, WIDI, and Gainz by GOTM. Collectively, these efforts have generated upwards of eight figures in revenue through minting and secondary sales, attracted hundreds of thousands of investors, and established a robust network of influential players in the Web3 ecosystem.<br>

I developed Meme Theft Auto from the recognition of yet another critical grab and a belief of the need to usher in the Web4 era… Now Not Later. I’ve seen the commitment that traders have to their “bag” and loyalty to their selected communities, as I have with GTA players dedicating over a decade with the same, if not more, intensity and relentlessness. Our passion to what we deem valuable unites both worlds in a deep yet unrealized accord. I’m a firm believer that those efforts and hours should not go unrewarded.

&#x20;

MTA is the beginning.

<figure><img src="https://386784223-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnnRUUlcWNZHniEsvyhAM%2Fuploads%2Fsaz11XLEAtoQ8xoUm92f%2F9E8A5255-10D2-4132-9E62-2C383C829F4F%202.JPG?alt=media&amp;token=84e58317-5f3e-44db-8ba7-0cf35ae1b6d4" alt=""><figcaption></figcaption></figure>

<figure><img src="https://386784223-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnnRUUlcWNZHniEsvyhAM%2Fuploads%2FmlBdvcSx06FOKR60jRou%2FE8D58C8D-12AF-417B-B5D2-B8391C8F84C0.PNG?alt=media&amp;token=e876135e-fc38-406d-bd9d-c6cb295af1c0" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://whitepaper.memetheftauto.com/the-founder/sb-on-them-nfts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
