> 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/security.md).

# Security

## 1. A new investment multisig has been created

<https://etherscan.io/address/0x890aa6fe016b36127564132466256355d900a562>

70-80% of liquid fund in the treasury will be transferred to the multisig&#x20;

The rest will be kept in deployer wallet for buy backs, add liquidity and other actions that requires fast execution &#x20;

Treasury’s portion of the tokenomics will be vested and sent here to stake \
Treasury will become the new owner of the $BTC token contract => prevent the deployer from having sole control.&#x20;

## 2. A new marketing multisig has been created

<https://etherscan.io/address/0xcb0149bf39F915218E3b897469beB760A515b50f>

Any tokens used for marketing will be sent here to stake and distribute. This ensures that transparency is there for usage of marketing budget.&#x20;

## 3. Remove mint access from deployer + move token owner to multisig&#x20;

\
We will revoke the mint privilege of the deployer wallet. This ensures that the deployer cannot mint tokens freely. This will also prevent a security breach should the deployer wallet is compromised.\
\
Revoke mint role tx: <https://etherscan.io/tx/0x772bf01f321266ed14979e217788f33435ba2817ae4ee7fdc2f5c00a790cf0b4>

Transfer ownership to multisig tx: <https://etherscan.io/tx/0x8e2dd57f25ae9e9f3c424559b3cb17450ef6fa15fd3a52c957d1aab273dd4794>

## 4. Contract audits:&#x20;

Paladin: In Process

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

## Conclusion:

By conducting security measures, Blackrock wants to show that we are committed to growing the project long term and creating a more trusted profile to attract more big investors.&#x20;


---

# 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/security.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.