# 1. Registration

When a round opens, participants can register through the [AutoCap Dashboard](https://filautocap.xyz/) by:

* **Connecting** a Filecoin-compatible wallet in the ***Burn Address*** \
   *This wallet is tracked for on-chain activity;*
* **Paying** the **registration fee** from that wallet\
  \&#xNAN;*The fee is currently set to 0.00005 FIL/TiB on Mainnet but might change in future rounds;*
* **Providing** a **DataCap Recipient Address** (`f0xxx`)\
  \&#xNAN;*This is the address that will receive DC at the end of the round.*\
  *Participant can either provide the Actor ID of the wallet directly, or the wallet address (0x, f1, f2, ...). The registration form will automatically convert the address in the corresponding Actor ID.*

Registration establishes a binding between measured on-chain activity of the ***Burn Address*** and the ***DataCap Recipient Address***, meaning the DC recipient, for the duration of the round.

<figure><img src="/files/Y4yzwNUBbReLlsRVIR34" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The **DataCap Recipient Address** is in the form of **Filecoin's Actor ID** (`f0xxx`). \
However, during the registration for the round, it can be provided as a standard wallet address `f1, f2, f3, f4, 0x` since AutoCap automatically derives the correct address. \
You can check your Actor ID at <https://filecoin.blockscout.com/>.
{% endhint %}

{% hint style="warning" %}
The **DataCap Recipient Address** must **already be active on-chain**. In practice, this means it should have sent or received at least one transaction (holding a small amount of FIL is sufficient).
{% endhint %}

#### Address Roles

Registration defines two distinct address roles:

* **Participant Burn Address**\
  This is the address from which on-chain economic activity is measured.\
  Only FIL burns originating from this address are counted toward the round.
* **Participant DataCap Recipient Address**\
  This is the address that receives the DataCap allocation at the end of the round.\
  It is not used for activity measurement.

These roles are independent: activity is always attributed to the Burn Address, while DataCap is always issued to the specified DataCap Recipient Address.

#### Constraints

* Each Participant Burn Address may register **at most once per round**.
* Registration applies only to the active round and does not carry over to future rounds.


---

# 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://lucas-documentation.gitbook.io/docs/phase-1-registration.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.