> For the complete documentation index, see [llms.txt](https://docs.blackrockfund.finance/blackrockfund.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blackrockfund.finance/blackrockfund.finance/contracts.md).

# Contracts

BTC Staking contract: [<mark style="color:blue;">https://etherscan.io/address/0x1FDe0d2F44539789256D94D1784a86bF77D66DD0</mark>](https://etherscan.io/address/0x1FDe0d2F44539789256D94D1784a86bF77D66DD0)

LP Staking contract: <https://etherscan.io/address/0x1e4a10d18698e4450e13b4e8ef361a5841850611>

BTC contract: [<mark style="color:blue;">https://etherscan.io/token/0xbD6323A83b613F668687014E8A5852079494fB68</mark>](https://etherscan.io/token/0xbD6323A83b613F668687014E8A5852079494fB68)

aBTC contract: <https://etherscan.io/address/0xa709aad0691fc67279577566640ae1d6515c1b81>

USDC Bond contract: <https://etherscan.io/address/0xef9e6123eff4dae9db1e6d585884b45b369a8ad1>

LP Bond contract: <https://etherscan.io/address/0x101c89a2c08295474e20e48a3fe77dc73f780351>

## Audits:

Paladin: <https://paladinsec.co/projects/blackrockfund/>

SourceHat: <https://sourcehat.com/audits/BlackRockFund/>

## Clarification on Paladin Audit Issues:

<figure><img src="https://lh7-us.googleusercontent.com/us1Hmjsqf0kr0FH2oiy6pBuU10F2J3ZqWqx20k0w7ZvalOFvzKKYMFe8Ppzcwe-fVHZVHyy5UlZQdenhCUGykCXi2-wcctenzlfDtd-7UJ-8aKWGF99jstOoHA4u88BnvKunLOH-iMxVMrb_UoeS2CE" alt=""><figcaption></figcaption></figure>

This is just a vague warning that your tokens might be rebased very quickly. We do not have a fixed debase rate so its hard to calculate the exact debase.&#x20;

It all depends on how many new tokens are claimed/emitted. Therefore, we acknowledged that there is no concrete way to calculate debase rate, but the mechanism of how and when debase happens are clear in the docs.

<figure><img src="https://lh7-us.googleusercontent.com/zvMrou77Clhf28TrgASQoHDBmjZhQEfgPf3aynybU_roIz7poKPM2jkNIu9XAUX8mV5criBdwj7SO-SkTTkhHHqO1P8iRruoXoyTuOx7Q4Ah14_dMa4cuLvKZGrqgQzmlgwmNcsYIfhD18YLpc1bTdA" alt=""><figcaption></figcaption></figure>

We are currently using approve() for all the approve functions and not using permit() anywhere. Even so, BTC is only on 1 chain. For future deployment we will remove this function completely.

<figure><img src="https://lh7-us.googleusercontent.com/PH0_5wnOi0GXO8kNm-lBsV7eaWKkeA3_IEZHjrGIv8-20Rn4nixhmifV7Xo4H2UUe2ea0nLZCinUBwrIYKtcxAuuARIYsll4pwnNgawfha1ilEb9uv06ZvTNFKJ2yapL8gg7Z6vICKpVLJAbTIAgN7g" alt=""><figcaption></figcaption></figure>

The team has commented on the resolution here. It is working as the logic intended too.

For future integrations, we will audit beforehand and fix all the issues before deployment. Blackrock team takes security seriously and we will show that through our future products.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.blackrockfund.finance/blackrockfund.finance/contracts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.