> For the complete documentation index, see [llms.txt](https://gitbookwhitepaper.gitbook.io/gnc-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbookwhitepaper.gitbook.io/gnc-whitepaper/ico/use-of-funds.md).

# Use of funds

All proceeds from the token sale will fund the product launch, continued platform development, and user acquisition:

**40%** R\&D. Development team with approximately 15-20 engineers. Platform development, new features, data-testing for HFT operations, mobile app development etc.

**25%** – Marketing expenses, PR and Customer Acquisition, presentations and region-specific roadshows. Digital currency trading exhibitions participations etc. There are natural network effects built into the product around the P2P asset trading model, which will lower the average customer acquisition cost (CAC) substantially.

**30%** - Initial Capex. Substantial costs largely associated with b2b API integration from multiple partners-exchanges. Costs of necessary Licensing. Latency optimization. Operational spends, employees (excl. developers), office etc.

**5% -** Legal, compliance fees


---

# 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://gitbookwhitepaper.gitbook.io/gnc-whitepaper/ico/use-of-funds.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.