# FAQ

### Why use a fractional stablecoin? <a href="#id-17h" id="id-17h"></a>

{% embed url="<https://twitter.com/samkazemian/status/1380022644280414212>" %}

**TLDR**: capital efficiency, as well as decentralization.

### How many chains is FRAX on?

FRAX the stablecoin is on over 20 different [chains](/frax-v1-original/frax.md). Ethereum, Fraxtal, and Arbitrum are the largest. FXS, FPI, frxETH, sfrxETH, and sFRAX are also on many of these chains.

### When was FRAX launched?

The FRAX token was launched December 20th, 2020 by [Sam Kazemian](https://iq.wiki/wiki/sam-kazemian/), [Travis Moore](https://iq.wiki/wiki/travis-moore/), and [Jason Huan](https://www.linkedin.com/in/jason-huan/).

### What is the relationship between FRAX and Everipedia / IQ.wiki?

Frax founders Sam Kazemian and Travis Moore (along with [Theodor "Ted" Forselius](https://iq.wiki/wiki/theodor-forselius/) and [Mahbod Moghadam](https://en.wikipedia.org/wiki/Mahbod_Moghadam)) created [Everipedia](https://iq.wiki/wiki/iqwiki/) (now IQ.wiki) in December 2014. Sam and Travis remain as advisors, but the company is now primarily led by Ted Forselius, [Navin Vethanayagam](https://iq.wiki/wiki/navin-vethanayagam/), and [Cesar Rodriguez](https://iq.wiki/wiki/navin-vethanayagam/).

### How big is the Frax Team?

As of 11/8/2024, 13 team members.

### Why does the Frax ecosystem have so many tokens and sub-projects?

The purpose of sub-projects like Fraxlend and Fraxswap is to ultimately generate utility for FRAX ecosystem tokens (like FXS, sFRAX, frxETH/sfrxETH) and stabilize / collateralize the FRAX peg. The goal was never to compete with larger competitors (e.g. Aave for Fraxlend, Uniswap for Fraxswap).&#x20;


---

# 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.frax.finance/guides-faq/faq.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.