# FilDA Finance Update - May 2022

1\. Optimize functions such as wallet connection and network switching.

2\. Deploy FilDA on the REI Network network.

3\. Support opening FilDA in ioPAY wallet.

4\. Added support for Korean language in FilDA.

### FilDA Supply On The page Product Data:

Total deposits and loans: $34,109,875.52

Number of current addresses: 145,302  

Current FilDA circulation: 180,836，673 FilDA

DAO pool pledge amount: 65,490,501.36  FilDA

 （ $ 434,902.91)

CMC market cap rank:3335

Coingecko Market Cap Ran:1932

In February, the loan agreement interest income for users (USDT):

HECO: 44,006.53

IoTeX: 112,665.84

ESC: 6,541.86

### Operational Dynamics:

1\. On May 02 (UTC), FilDA - ESC restarted and opened deposits and borrowing. Users can obtain FilDA rewards by staking ELA, BTC, ETH, HUSD and other assets to provide liquidity.

<https://www.filda.io>

2.Recently, FilDA teamed up with ONTO to hold an online AMA. The best questions asked on Twitter and the AMA site can be shared with $𝟓𝟎𝟎 Filda.

<https://twitter.com/FilDAFinance>

3.Recently, $Filda (HECO) was launched on the Bit.Store app.

<Https://bit.store/index.html>

4.Recently, FilDA teamed up with REI Network to hold an online AMA. Follow and retweet the content on Twitter to participate in the share of $1000 Filda, and join the Telegram group to participate in the AMA to have a chance to win $𝟓𝟎𝟎 Filda share reward.

<https://twitter.com/FilDAFinance>


---

# 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.filda.io/english/filda-report/filda-finance-update-may-2022.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.