> For the complete documentation index, see [llms.txt](https://lucas-documentation.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lucas-documentation.gitbook.io/docs/why-a-registration-fee.md).

# Why a Registration Fee?

{% hint style="info" %}
The fee is currently set to 0.00005 FIL/TiB on Mainnet but might change in future rounds.
{% endhint %}

Registration fees do **not** count toward a participant’s eligible FIL burn for DataCap allocation.

Their purpose is purely structural. The registration fee exists to:

* Prevent spam or costless registrations
* Ensure a minimal economic commitment from participants
* Maintain a clean separation between **access control** and **contribution measurement**
* Cover the transaction costs associated with issuing DataCap allocations at the end of the round

By excluding the registration fee from contribution accounting, AutoCap ensures that allocation outcomes are driven exclusively by **measured on-chain economic activity**, rather than by participation overhead or gating mechanisms.

This separation preserves the integrity of the allocation process: registration controls *who* can participate in a round, while FIL burns determine *how much* DataCap is allocated.


---

# 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://lucas-documentation.gitbook.io/docs/why-a-registration-fee.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.