# PAGM

![PAGM v2](/files/LYKrCnJI0Ix7QBwzp6Ly)

**Personal Avaxtar Generation Machine (PAGM)** is available to buy with $AVXT Tokens on [**Marketplace**](https://avaxtars.com/browse?t=items\&f\[data.type]=PAGMs\&s=data.price:asc)

PAGM can analyze the digital genetic codes of the Avaxtars, process them and create new Avaxtars. We called this **Avaxtar Farming (AF)**. For the **AF** process, two Avaxtars should be locked in PAGM for a certain time.&#x20;

Only Gen1 Avaxtars can be used for the **AF** process.&#x20;

Unfortunately, the AF process requires some time and cannot be completed successfully on every try. The basic success rate multiplier is 50%. But this can be increased by the rarity levels of the Avaxtars used for the AF process. In addition to this, the required time for the AF process decreases by the rarity of Avaxtars used for the **AF** process. Here are the tables for Success Rates and Waiting Times.

![Success Matrix of AF](/files/OE0inO9x1T2eInXulqg2)

![Process Time for AF (Days)](/files/i5EQ4bOZTE36lamsCrMm)

Let’s dive deep into these tables.

If an Agent locks two **Common Avaxtars** in the **PAGM** then the waiting time will be **7 days** and at the end of this process, the success rate is **50%**. In this example, if **PAGM** fails to generate a new Avaxtar, the locked ones return to their Agents.

If an Agent locks two **Legend Avaxtars** in the **PAGM**, the waiting time for a new Avaxtar will be **3,85 days**, and the success rate of **0,95** means that at the end of 3,85 days a new Avaxtar will be generated **95%**.

Farmed new unique Avaxtars will have the same distribution percentages as now to become in different rarities.

Every new Avaxtar brings some **$AVXT** tokens with it. The amount of **$AVXT** token brought by the new character depends on the rarity of that Avaxtar. When Avaxtars started the amount of $AVXT can be earned was with the creation of Gen2 Avaxtars are as follow;

* Common: 10 $AVXT,
* Uncommon: 12 $AVXT,
* Rare: 14 $AVXT,
* Epic: 17 $AVXT,
* Legend: 20 $AVXT.

With the ongoing process **after every 2.500 new Gen 2 Avaxtars creation**, the **$AVXT** rewards given to Avaxtar Farmers have been reduced by 25%. We have now halted this process after 11 successful bounty reduction periods. From now on, there will be no decrease in $AVXT rewards. The rewards for successful AF processes are shown below in the period following each reward reduction. We will reconsider the awards and make changes in the future.

![](/files/dVPnFPhHNF85vvTrOfg3)

Agents have a possibility to decrease the required time for **AF** spending some **$AVXT** Tokens. You should have enough $AVXT Token balance in your game wallet. For different PAGM Accelerations players should spend different amount of $AVXT Tokens. Those tokens have been also reduced after every 2.500 new Gen 2 Avaxtars creation. From now on, there will be no decrease in $AVXT costs for process accelerations and we will reconsider to make changes for those costs in the future.

![](/files/nIQPi7sn2fCTZUDSEG66)

**Failed PAGM processes will reward** [**$DGC**](/fundamentals/tokenomics/usddgc.md)

**The Avaxtar Farming (AF)** process, which is carried out using the **PAGM** device and **two Gen1 Avaxtars**, has varying success rates depending on the rarity level of the Gen1s used, and all PAGM owners, without exception, can occasionally get **unsuccessful results**. On the other hand, PAGM devices spend considerable time analyzing the digital genetic codes of the two Gen1s to generate a new one. We can see that **some of the analyzed code can be recovered**, even if it fails to generate a new Gen2. This amount will be determined by the rarity of the Gen1s used. The table below shows how much **$DGC** can be recovered.

![](/files/60VG4T4gXuNrhCFGBPZg)

Unfortunately, the records of Gen1s placed in PAGM devices during the early period when PAGM processes began in Avaxtars were corrupted due to the first wave of the Quantnet frequency wars. For all these records, PAGM holders will be awarded 50 $DGC for related transactions. Yes, starting with the first failed PAGM and retroactively, all PAGM holders will receive their rewards :) From now on, new failed PAGM transactions will also generate $DGC in the specified amounts.

***Using PAGM for $DGC generation***

During their research, our scientists discovered that Gen2 Avaxtars were insufficient to create new Gen2 characters. Further investigation, however, revealed that **Gen2s could be used to generate $DGC**.

By locking **two Gen2 characters into a PAGM device** and **waiting a certain amount of time**, any player will be able to generate $DGC. Unfortunately, this process will **not award $AVXT** as it did for Gen2 production, but thanks to the tremendous efforts of our scientists, there is **no risk of failure in the production of $DGC with PAGM devices**. The **rarity level of the Gen2 characters** used in the PAGM device determines the amount of $DGC that can be produced.

The table below shows the amount of $DGC that can be produced using two Gen2 and PAGM as a result of extensive research.

![](/files/9rpPn8Y5dWdUZYq4GAgP)

The production times are the same as those required for Gen1 production as shown in the table below.

![](/files/uyqUwojTRQxkuyxUsv5C)

Our scientists have discovered that this process can be accelerated by 20%, 40%, or 60% by paying $AVXT as in the Gen2 production process and at the same cost.<br>


---

# Agent Instructions: 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://whitepaper.avaxtars.com/fundamentals/pagm.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.
