> For the complete documentation index, see [llms.txt](https://whitepaper.frak.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.frak.id/frak-protocol/creator-work-minting/fraktion-supplier.md).

# Fraktion Supplier

{% hint style="info" %}
This function allows to fix automatically every week the new supply of fraktions for a given content and a given profitability
{% endhint %}

### Free Fraktion

Free Fraktion are minted only once when a user is consuming the content for the first time. There is no supply before the minting.

### Initial Supply

The number of Fraktions for the initial drop is the same for every content : `Date 0`

| Profitability | Initial Drop | Initial Price |
| ------------- | ------------ | ------------- |
| Common        | 20           | FRK 90        |
| Premium       | 7            | FRK 500       |
| Gold          | 3            | FRK 1200      |
| Diamond       | 1            | FRK 3000      |

### New Supply

Every week (`Date 0` + `7 days`), we check for every profitability if all the fraktions have been sold.

**Case 1 : If all the fraktions haven’t been sold**

No more fraktion are supplied

The price of the fraktions that haven’t been minted yet is recalculated depending on the algorithm decribed [here](https://www.notion.so/Update-du-27-09-22-85d3073e47554ab5807babf20b947f77).

**Case 2 : All the fraktions have been sold**

New fraktions are supplied.

The number of new fraktions $$n\_w$$ supplied depends on :

* the number of fraktions minted during the former week
* the velocity at which the fraktions were minted

{% hint style="success" %}
$$n\_w$$ is in the range of 80% and 200% of the number of fraktions minted the last week, $$\rho\_{w-1}$$.
{% endhint %}

Let $$t\_k$$ the timestamp when the fraktion $$k$$ is minted

Let $$t\_0$$ the timestamp of the last weekly anniversary (when the new fraktions were supposed to be supplied the last week). $$t\_0=t-168$$.

$$t\_0$$ and $$t\_k$$ are set in hour

$$
n\_w=m\_{w-1}\times\bigg(80%+(200%-80%)\times \mu\_{w-1} \bigg)
$$

where 

$$
\mu\_{w-1}=1-\frac{\sum\_{k=1}^{m\_{w-1}}(t\_k-t\_0)}{m\_{w-1}\times24\times7}=1-\left(\frac{\sum\_{k=1}^{m\_{w-1}}t\_k}{m\_{w-1}}-t\_0\right)\times\frac{1}{168}
$$

Example :

{% embed url="<https://docs.google.com/spreadsheets/d/10VtFagjbk4pvKma1Y2FIpRvbPV9zMQPTZMUBop7zzIs/edit?usp=sharing>" %}


---

# 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.frak.id/frak-protocol/creator-work-minting/fraktion-supplier.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.