> For the complete documentation index, see [llms.txt](https://aikaverse.gitbook.io/aikaverse/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aikaverse.gitbook.io/aikaverse/information/contributors.md). # Contributors Our team is a tight-knit group of 6, led by [**@cryptoraz1**](https://x.com/cryptoraz1), with [**@luxetheluxe**](https://x.com/luxetheluxe) as one of the core contributors at AIME. Raz handles most of the operations and tech side of things, while I focus on marketing and growth. About 6 months ago, we launched Fanko.tech on the Sanko chain, and it’s now become the go-to token launchpad on the chain. You might not have heard of it, but it’s actually one of the key reasons why [Arbitrum Foundation](https://x.com/arbitrum)/ [Offchain Labs](https://x.com/offchainlabs) awarded us a top grant in their recent trAIlblazer program. On top of that, Camelot also backed us with an operational grant during our early months. Before all this, we’d already been building in crypto since 2020. Our track record spans everything from DeFi index products to social platforms, so launching Fanko wasn’t our first rodeo. #### Here’s a quick breakdown of the core team’s experience * **Lead Dev** – Former Senior Data Scientist at the largest edutech company in the country. * **Full Stack Dev** – Over 10 years of experience building banking and finance infrastructure. * **AI Dev** – Built a music-to-blockchain platform and is a certified prodigy (graduated in 2.5 years with a specialization in AI). * **UI/UX Dev** – Former Senior Designer at Top 3 most used stock app in the country. --- # 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://aikaverse.gitbook.io/aikaverse/information/contributors.md?ask=&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.