Contracts

Contracts of BlackrockFund

BTC Staking contract: https://etherscan.io/address/0x1FDe0d2F44539789256D94D1784a86bF77D66DD0

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

BTC contract: 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:

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.

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.

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.

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.