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

# Introduction

### Team

A brief overview about us: We are a small team consisting of 2 Devs and one marketing officer. We all work in the IT industry as our full time jobs. 

### Background

We have been around this industry for several years and started looking into yield farming around three years prior analyzing what can we do for a single coin farm not to die in the first few hours. Why did we start with 0 Liquidity and **Genesis** farming? Because we hate bots that ruin every launch of every project that has an initial liquidity. 

### KYC & Audit

Currently, there are no plans for KYC or audits; our code is forked from already existing, working tomb forks and feel no need for an audit. As for KYC, we believe that paying 6 thousand dollars for something that does nothing is pointless. If our community truly wishes for one, we will explore said options. For now, we intend to renounce the ownership of our contracts as soon as possible, ideally before the end of the genesis pools.


---

# 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:

```
GET https://gvbhj-hj.gitbook.io/untitled/introduction.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.