# FilDA Platform Documentation

## Introduction <a href="#introduction" id="introduction"></a>

FilDA is a lending and borrowing project basing on smart contracts to realise a cross-chain money market . It launched on HECO (Huobi ECO Chain) and is deployed on other public chains (IoTeX, Elastos Smart Chain, BNB Smart Chain, Polygon and Arbitrum One).

Unlike other lending and borrowing projects deployed on the Ethereum chain, we chose HECO as the base chain. We introduced the ecological resources and assets on Huobi and can make our service more user-friendly because of the accessibility of HECO and the extremely low gas fees. The same is true for the subsequent chain launches since our genesis on HECO.

**Note**

FILDA is the governance token of FilDA Protocol rather than a token with pure investment value.

The project team has 5 percent of the token share which will be released in blocks over 4 years. The team didn't receive any tokens in the first week after FilDA was launched. The token for the team was generated from the second week after FilDA went live.

### Business Model <a href="#business-model" id="business-model"></a>

![](https://gblobscdn.gitbook.com/assets%2Ffilda-english-preview%2F-MZyeAg1-dQfFhTorPvq%2F-MZye_rO34V3kI7PDdPa%2F0.png?alt=media)

#### Basic Features <a href="#basic-features" id="basic-features"></a>

* Liquidity pool
* Interest rates are determined algorithmically by supply and demand
* Floating interest rates that are non-negotiable
* Absolutely transparent token balance information, complete records of all transactions and historical interest rates

#### Deposit <a href="#deposit" id="deposit"></a>

* Aggregate the tokens of each user
* Withdraw the assets at any time
* Collect the accrued interest at any time

#### Primary Use Cases <a href="#primary-use-cases" id="primary-use-cases"></a>

* Uses can supply their asset and earn interest at low risk
* dApps, institutions and exchanges can gain incremental returns

#### Borrowing Tokens <a href="#borrowing-tokens" id="borrowing-tokens"></a>

* Requires over-collateralisation
* No time limit for borrowing

#### Risk <a href="#risk" id="risk"></a>

* When the value of the borrowing assets is above the collateral ratio, the users' collateral should be liquidated at a price that is below the market price, which motivates the arbitrageurs to step in to eliminate the risk.

#### Primary User Cases <a href="#primary-user-cases" id="primary-user-cases"></a>

* Quickly borrow utility tokens at any time without having to wait (time required to fill an token buy order on exchanges)
* Users can conduct ICO investments by borrowing ETH using their existing portfolio (multiple tokens or assets) as collateral.
* Short selling

#### Ledger System <a href="#ledger-system" id="ledger-system"></a>

Cash + Borrows = Supply + Equity

Follow international accounting standards:

| Event                    | Debit               | Credit              |
| ------------------------ | ------------------- | ------------------- |
| Supply Token             | Cash                | Supply              |
| Withdraw Token           | Supply              | Cash                |
| Borrow Token             | Borrows             | Cash                |
| Repay borrows            | Cash                | Borrows             |
| Liquidate (Borrower)     | Supply (Collateral) | Borrows(Asset)      |
| Liquidate ( Caller)      | Cash(Asset)         | Supply (Collateral) |
| Accrue Interest (Supply) | Equity              | Supply              |
| Accrue Interest (Loan)   | Borrows             | Equity              |

​[<br>](https://gregfilda.gitbook.io/filda-english-preview/v/chinese/)


---

# 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/english-version/filda-platform-documentation.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.