# FAQ

<details>

<summary>Is the codebase forked or built from scratch?</summary>

At Extrafi XLend, our guiding principle is 'safety and user experience first'. To achieve this, we use a battle-tested codebase instead of building from scratch, allowing us to focus on accessibility and composability.&#x20;

1. The core liquidity protocol is a fork of Aave V3.0, with essential fixes and enhancements applied for added robustness.
2. Our multi-account functionality is powered by the leading Account Abstraction (AA) solution - Coinbase Smart Wallet.&#x20;

We’ve also developed peripheral contracts and overall UX enhancements to ensure a smooth, seamless experience across the product.

</details>

<details>

<summary>is the product audited?</summary>

Yes, while the original codebase has undergone multiple audits and verifications, we conduct a new audit before its launch. Check the report [here](https://docs.extrafi.io/extrafi-xlend/security/audits-and-security).

</details>

<details>

<summary>What is the difference between XLend and Extrafi LYF (Leveraged Yield Farming)</summary>

XLend is a liquidity protocol enabling users to borrow and lend.&#x20;

Also, smart account integration paves the way for XLend to evolve into an open, composable liquidity protocol designed to enhance on-chain capital efficiency with intuitive inputs. Even in this early version, users can benefit from features like liquidation-free borrowing and one-click leverage within the protocol.\
\
Extrafi LYF focuses on its current use case, with a vision to enable flexible liquidity provision.

</details>


---

# 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.extrafi.io/extrafi-xlend/borrow-lend/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.