# Understand Filecoin (FIL) Wallet Address

#### **Understanding Filecoin (FIL) Wallet Addresses**

Filecoin (FIL) wallets come in **five different address types**: **f0, f1, f2, f3**, and **f410 (or 0x)**.

***

#### **How to Identify Your Wallet Address Type**

You can tell what type of address you have by looking at the **first few characters** of your Filecoin address, called the **“protocol indicator.”**

**Example:**\
If your address looks like this:\
**f1s5hbfgxihcbdj5jc35kv2eyoqpqdbahyo67ord**\
The number **right after the “f”** is **1**, so this is an **f1 address**.

***

#### **Why Are There Different Address Types?**

Filecoin is more than just a blockchain—it’s a network for **decentralized data services** like **storage, retrieval, and computation**. Each address type serves a **specific purpose** within this ecosystem, helping different parts of the network work together smoothly.

***

#### **What is an f410 or 0x Address?**

An **f410** (or **0x**) address is needed if you want to use **Filecoin Virtual Machine (FVM)** applications, like DeFi protocols (including **FILLIQUID**).

* An **f410** address starts with “**f410**”.
* A **0x** address looks like an **Ethereum-style** address, starting with “**0x**”.

The **f410** and **0x** addresses are **linked**—they both control the **same FIL balance**. You can easily **convert** between them.

**Example:**

* **f410fxk7kt4wlqoduvsv52sflzrkrp7iwuqjqphtis5y**\
  ↔
* **0xBabea9F2Cb83874aCaBdD48ABCc5517fd16A4130**

Both of these addresses give access to the **same FIL**. That’s why we call them **0x/f410 wallets**.


---

# 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://docs.filliquid.io/staking-user-guide/more-instructions/understand-filecoin-fil-wallet-address.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.