BitFi Basis: control-plane safety record
1 indexed control-plane surface for BitFi Basis, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0xCdFb…fb15
Control-plane scorecard
Aligned Docs and chain match
- Upgradeability
- Weak · Upgradeable with no enforced delay: no timelock in front of upgrades (1 other upgrade path not determined)Evidence: bitfi-bfbtc-multisig-manager-is-a-safe-s37: its owners have no code. In the verified source depositNative, approveWithdraw, nativeWithdraw and updateEpoch are onlyMultisig (msg.sender == multisig), the …
- Timelock floor
- Weak · 0s minimum enforced delay across control surfacesEvidence: bitfi-bfbtc-multisig-manager-is-a-safe-s37: its owners have no code. In the verified source depositNative, approveWithdraw, nativeWithdraw and updateEpoch are onlyMultisig (msg.sender == multisig), the …
- Signer quorum
- Not determined · No signer quorum in the published records
- Emergency / freeze scope
- Not determined · No pause / freeze authority in the published records
- Docs-vs-chain parity
- Strong · Chain matches or is stronger than the documentation
Each slice is derived only from the pinned records on this page and their controller facts (/api/v1/scorecards.json). A hollow slice is not determined by the published evidence (never a guess); docs-vs-chain parity is uncompared for RPC-observed protocols. How to read it.
Check it live (free)
The pre-flight API re-reads the controller, proxy and capabilities of one contract at the latest block. No key, no wallet. The score rates that single contract, not the whole protocol.
curl -s "https://pacta-x402.pacta.workers.dev/v1/check/preflight?chain=ethereum&address=0xCdFb58c8C859Cb3F62ebe9Cf2767F9e036C7fb15"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0xCdFb58c8C859Cb3F62ebe9Cf2767F9e036C7fb15"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0xCdFb58c8C859Cb3F62ebe9Cf2767F9e036C7fb15"})bfBTC multisig manager: multisig() = a 2-of-3 Safe, as documented; owner() a key
Observed onchain. bfBTC 0xCdFb58c8C859Cb3F62ebe9Cf2767F9e036C7fb15 (Ethereum; the deployed-contracts page lists it): ERC-1967 proxy, implementation slot = 0x4ca67a794051e036eefB5Aa4b34fE2bd836069F0, admin slot empty (UUPS); implementation Bfbtc (verified source). multisig() = 0x1Eb14eC5fc6D596C041F4DEA2Bf0F2cb6EF0dD03, a Safe: getThreshold() = 2 of getOwners() = 3; guard slot empty; getModulesPaginated() lists no module; its owners have no code. In the verified source depositNative, approveWithdraw, nativeWithdraw and updateEpoch are onlyMultisig (msg.sender == multisig), the functions the docs assign to the multisig manager. Not documented, and stated here: owner() = 0xd931401B37c3A368505E7AE6dE700f2b0ad14ac6, an account with no code at this pin, and the owner functions include setMultisig (replacing the multisig manager), _authorizeUpgrade (the UUPS upgrade), setPause, setBlacklisted, setFee and setFeeReceiver, with no timelock in the path. The docs say nothing about the owner role, so this record compares only the documented multisig manager. This record does not allege any misuse of these powers.
Documented. 'After a request is submitted, it must be approved by an authorized multisig manager.' (docs.bitfi.one/developer/using-contract/unstake-bfbtc); 'This is an administrative function callable only by the designated multisig manager.' (docs.bitfi.one/developer/using-contract/stake-bfbtc); 'bfBTC: 0xCdFb58c8C859Cb3F62ebe9Cf2767F9e036C7fb15' (docs.bitfi.one/developer/bfbtc-overview/deployed-contracts)
cast call 0xCdFb58c8C859Cb3F62ebe9Cf2767F9e036C7fb15 \ "multisig()" \ --block 26458556 --rpc-url "$ETH_RPC_URL" cast block 26458556 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xe258bb1cbcc988e2dfdba4ba173f9f8690520dba3647cdcae18e0651822769d2
Embed Live Control-Plane Badge
Show BitFi Basis's Base-EAS-attested Aligned control-plane status in a README, docs page or forum post. The badge links back to this record.
[](https://pacta.wtf/protocols/bitfi-basis/)
<a href="https://pacta.wtf/protocols/bitfi-basis/"><img src="https://pacta.wtf/badges/bitfi-basis.svg" alt="Pacta Control Plane: Aligned · Base EAS" height="20"></a>
Static badge: https://pacta.wtf/badges/bitfi-basis.svg (rebuilt with the site). Live edge badge: https://pacta-x402.pacta.workers.dev/v1/badges/bitfi-basis.svg (5-minute cache).
Operating BitFi Basis? Add Continuous Control-Plane Monitoring
Continuous Control-Plane Monitoring ($1,500 USDC / month) re-checks your control plane after governance proposals, signer rotations and timelock upgrades, and refreshes the dossier and attestation. It does not buy a status: the result can still be Delta whenever docs and chain diverge.