Solv Protocol (SolvBTC): control-plane safety record
2 indexed control-plane surfaces for Solv Protocol (SolvBTC), each pinned to a canonical Ethereum block and compared with what the protocol documents. Contracts: 0x7A56E1C57C7475CCf742a1832B028F0456652F97, 0xfd4B809AD88db6Ca9dbB295A4B9d23bB0093f497.
What differs
Changed / discrepant
- SolvBTC beacon upgrades behind a 3d TimelockController (docs: timelock 'will be added'): SolvBTC is a beacon proxy: EIP-1967 beacon slot = UpgradeableBeacon 0xFc335FdA7E6a33329A83F4d5F578eC7d8A43DC4A (implementation() = 0xA4b6cf2BAaA235ab7Fe10EADB84b82460165B38F), whose owner() = … observed vs docs.solv.finance/llms-full.txt: 'The admin privileges for upgrades are assigned to a Gnosis Safe multi-signature address ... documented
Show the full onchain evidence
SolvBTC is a beacon proxy: EIP-1967 beacon slot = UpgradeableBeacon 0xFc335FdA7E6a33329A83F4d5F578eC7d8A43DC4A (implementation() = 0xA4b6cf2BAaA235ab7Fe10EADB84b82460165B38F), whose owner() = SolvBTCFactory 0x443628281E4f3E5b5A5D029B9a0D13900ae41578 (getBeacon('Solv BTC') = that beacon). The factory's admin() = TimelockController 0xfd4B809AD88db6Ca9dbB295A4B9d23bB0093f497 (pendingAdmin() = 0) with getMinDelay() = 259200s (3d); governor() = the 3-of-5 Safe 0x0c2Bc4d2698820e12E6eBe863E7b9E2650CD5b7D (pendingGovernor() = 0), which holds the timelock's PROPOSER_ROLE, EXECUTOR_ROLE and CANCELLER_ROLE but not DEFAULT_ADMIN_ROLE (held by the timelock itself; EXECUTOR_ROLE not open). Verified source pinned to runtime code: SolvBTCFactory is a Sourcify exact_match and every beacon-mutating path (setImplementation -> upgradeTo, transferBeaconOwnership, importBeacon) and transferAdmin is onlyAdmin, while onlyGovernor only deploys new beacon proxies; the timelock (SolvTimelock is OpenZeppelin v5.0.0 TimelockController, fully verified on Blockscout, not on Sourcify) reverts schedule when delay < getMinDelay() and only lets itself call updateDelay.
Show the full documented text
docs.solv.finance/llms-full.txt: 'The admin privileges for upgrades are assigned to a Gnosis Safe multi-signature address ... The timelock mechanism will be added to further enhance security by introducing a delay between the upgrade proposal and execution.'
Matched
- SolvBTC owner() = 3-of-5 Gnosis Safe (OpenZeppelin Ownable): matches the documentation
Control-plane scorecard
Protective Chain stronger than documented
- Upgradeability
- Strong · Upgradeable behind a ≥48h delay (3d)Evidence: solv-solvbtc-upgrade-beacon-3d-timelock-s17: governor() = the 3-of-5 Safe 0x0c2Bc4d2698820e12E6eBe863E7b9E2650CD5b7D (pendingGovernor() = 0), which holds the timelock's PROPOSER_ROLE, EXECUTOR_ROLE and …
- Timelock floor
- Strong · 3d minimum enforced delay across control surfacesEvidence: controller fact: getMinDelay() = 259200s
- Signer quorum
- Strong · Lowest controlling quorum: 3-of-5Evidence: solv-solvbtc-owner-3of5-safe-s17: … (0x7A56E1C57C7475CCf742a1832B028F0456652F97).owner() = 3-of-5 Safe 0x0c2Bc4d2698820e12E6eBe863E7b9E2650CD5b7D; …
- 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=0x7A56E1C57C7475CCf742a1832B028F0456652F97"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0x7A56E1C57C7475CCf742a1832B028F0456652F97"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0x7A56E1C57C7475CCf742a1832B028F0456652F97"})SolvBTC owner() = 3-of-5 Gnosis Safe (OpenZeppelin Ownable)
Observed onchain. SolvBTC (0x7A56E1C57C7475CCf742a1832B028F0456652F97).owner() = 3-of-5 Safe 0x0c2Bc4d2698820e12E6eBe863E7b9E2650CD5b7D; name() = 'Solv BTC', totalSupply() = 2,397.43 SolvBTC (18 decimals).
Documented. docs.solv.finance/llms-full.txt: 'The permission model for updating business parameters (such as adding supported tokens, setting Oracle address, etc.) uses OpenZeppelin’s Ownable implementation, with the permission address being a Gnosis Safe multi-signature address.'
cast call 0x7A56E1C57C7475CCf742a1832B028F0456652F97 \ "owner()" \ --block 26418060 --rpc-url "$ETH_RPC_URL" cast block 26418060 --field hash --rpc-url "$ETH_RPC_URL" # expect 0x8914f5134a4488a812b61c1c7f479c3082d80f6fbe2f181abb9e5ef4ff973f3c
SolvBTC beacon upgrades behind a 3d TimelockController (docs: timelock 'will be added')
Observed onchain. SolvBTC is a beacon proxy: EIP-1967 beacon slot = UpgradeableBeacon 0xFc335FdA7E6a33329A83F4d5F578eC7d8A43DC4A (implementation() = 0xA4b6cf2BAaA235ab7Fe10EADB84b82460165B38F), whose owner() = SolvBTCFactory 0x443628281E4f3E5b5A5D029B9a0D13900ae41578 (getBeacon('Solv BTC') = that beacon). The factory's admin() = TimelockController 0xfd4B809AD88db6Ca9dbB295A4B9d23bB0093f497 (pendingAdmin() = 0) with getMinDelay() = 259200s (3d); governor() = the 3-of-5 Safe 0x0c2Bc4d2698820e12E6eBe863E7b9E2650CD5b7D (pendingGovernor() = 0), which holds the timelock's PROPOSER_ROLE, EXECUTOR_ROLE and CANCELLER_ROLE but not DEFAULT_ADMIN_ROLE (held by the timelock itself; EXECUTOR_ROLE not open). Verified source pinned to runtime code: SolvBTCFactory is a Sourcify exact_match and every beacon-mutating path (setImplementation -> upgradeTo, transferBeaconOwnership, importBeacon) and transferAdmin is onlyAdmin, while onlyGovernor only deploys new beacon proxies; the timelock (SolvTimelock is OpenZeppelin v5.0.0 TimelockController, fully verified on Blockscout, not on Sourcify) reverts schedule when delay < getMinDelay() and only lets itself call updateDelay.
Documented. docs.solv.finance/llms-full.txt: 'The admin privileges for upgrades are assigned to a Gnosis Safe multi-signature address ... The timelock mechanism will be added to further enhance security by introducing a delay between the upgrade proposal and execution.'
cast call 0xfd4B809AD88db6Ca9dbB295A4B9d23bB0093f497 \ "getMinDelay()" \ --block 26418060 --rpc-url "$ETH_RPC_URL" cast block 26418060 --field hash --rpc-url "$ETH_RPC_URL" # expect 0x8914f5134a4488a812b61c1c7f479c3082d80f6fbe2f181abb9e5ef4ff973f3c
Control-plane badge: Parameter Delta
This badge is amber because at least one Base-EAS-attested surface of Solv Protocol (SolvBTC) differs from what the protocol documents. It turns to the emerald Aligned · Base EAS shield only when the on-chain state or the documentation changes and the two match at a new finalized block, whoever requests the re-check.
Embed this badge (it updates when the status changes):
[](https://pacta.wtf/protocols/solv-protocol-solvbtc/)
<a href="https://pacta.wtf/protocols/solv-protocol-solvbtc/"><img src="https://pacta.wtf/badges/solv-protocol-solvbtc.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>
Badge: https://pacta.wtf/badges/solv-protocol-solvbtc.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/solv-protocol-solvbtc.svg.
Maintaining Solv Protocol (SolvBTC)? Verify and reconcile the record
Two paths, both public. A free doc-update notice asks the maintainers to correct the documentation or the onchain parameter; anyone can send it. A Full Control-Plane Dossier ($2,500–$5,000 USDC, 24h SLA) re-reads the multisig and timelock control planes on archive RPCs and prepares an upstream docs reconciliation PR. Either way the classification changes only when the onchain state or the documentation aligns at a new finalized block.
Need procurement paperwork? Request a commercial invoice (PDF).