> For the complete documentation index, see [llms.txt](https://whitepaper.avaxtars.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.avaxtars.com/fundamentals/devices/digital-genetic-code-generator-dgcg.md).
# Digital Genetic Code Generator (DGCG)
* Players will be able to buy 1 DGCG per account at the moment.
* The base price for a DGCG is 6 $AVXT.
* DGCGs will be bought as Level 1.
* Locking a scientist into DGCG and paying the upgrade cost with $ENXT will upgrade it to next level.
* The required amount of scientists to upgrade DGCG is 1 and the required $ENXT is 25 for each level.
* Scientists will be locked permanently in DGCG for upgrading the level of DGCG.
* Gen2 Avaxtars will be put into DGCG to farm $DGC Token.
* Gen2 Avaxtars’ rarity **will affect** the outcome of DGCG Process.
* Every 7 days, users should claim produced $DGC Tokens and will start the process again (Just like the process of PAGMs)
DGC Generator Production & Upgrade Table is shown below:
According this table a player may lock 5 Gen2 Avaxtars in to a level 5 DGCC. Let’s assume all of those Avaxtars are Rare then this DGCC will produce 200 $DGC per 7 days.
---
# 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://whitepaper.avaxtars.com/fundamentals/devices/digital-genetic-code-generator-dgcg.md?ask=&goal=
```
`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.