> For the complete documentation index, see [llms.txt](https://constant-finance.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://constant-finance.gitbook.io/docs/faq/audits-networks-and-points.md).

# Audits, Networks, and Points

[All FAQ topics](/docs/faq.md)

Select a question to reveal its answer.

<details>

<summary>Is Constant Finance audited? Is it safe to use?</summary>

Constant Finance is preparing for external smart-contract audits covering the core lending and Staking contracts. These audits have not yet started or been completed. Audit completion is required before mainnet launch.

No audit can guarantee safety. Smart-contract defects, oracle errors, collateral price changes, and limited liquidation liquidity can cause losses. The deployment covered by this documentation is a Sepolia public beta using test assets. See [Deployment](/docs/introduction/deployment.md) for its limitations.

</details>

<details>

<summary>Which network is covered by this documentation?</summary>

This documentation covers Ethereum Sepolia testnet. It does not describe an Ethereum Mainnet deployment. Sepolia faucet assets have no mainnet economic value.

Use the [Deployment](/docs/introduction/deployment.md) pages for network and contract information, and follow the official channels for future launch announcements.

</details>

<details>

<summary>Is there a token? What is the Points program?</summary>

Constant Finance does not currently have a protocol token. A token is planned for the future, but no launch date or allocation terms are specified here.

The **Points program is live** at [points.constant.finance](https://points.constant.finance/). Points measure participation and are intended to serve as one reference for future community distributions and other rewards. This FAQ does not promise a fixed conversion ratio or a guaranteed reward allocation.

Visit the Points portal for available participation activities and their requirements.

</details>

<details>

<summary>Where can I find official information and technical details?</summary>

Use these official resources:

* [Constant Finance website](https://constant.finance/) for project information.
* [Overview](/docs/introduction/overview.md) and [Concepts](/docs/introduction/concepts.md) for the lending model and Position lifecycle.
* [Deployment](/docs/introduction/deployment.md) for documented Sepolia addresses and configuration.
* [X](https://x.com/constant_fi) and [Discord](https://discord.com/invite/gCXeqHYCXC) for announcements and community discussion.

The test assets listed in the deployment pages should not be confused with a launched protocol token.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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 following URL with the `ask` and `goal` query parameters:

```
GET https://constant-finance.gitbook.io/docs/faq/audits-networks-and-points.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.
