K3 Capital: control-plane safety record
1 indexed control-plane surface for K3 Capital, with its controller and timelock state pinned to a canonical Ethereum block over archive JSON-RPC (not EAS-attested; documentation parameters are linked, not compared). Contract: 0xdC47953c816531a8CA9E1D461AB53687d48EEA26.
Control-plane scorecard
Observed Chain pinned; docs not assessed
- Upgradeability
- Not determined · Upgradeable; the delay gating the upgrade path is not in the published recordsEvidence: k3-capital-control-plane: is_eip1967_proxy = true
- Timelock floor
- Not determined · No enforced admin delay in the published records
- Signer quorum
- Moderate · Lowest controlling quorum: 2-of-3Evidence: k3-capital-control-plane: … controller is in turn controlled by Safe 2-of-3 0x5721ce64Ee0D772Ce613b62D411350091C544cD0.
- Emergency / freeze scope
- Not determined · No pause / freeze authority in the published records
- Docs-vs-chain parity
- Uncompared · Uncompared: documentation not assessed (RPC-observed)
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=0xdC47953c816531a8CA9E1D461AB53687d48EEA26"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0xdC47953c816531a8CA9E1D461AB53687d48EEA26"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0xdC47953c816531a8CA9E1D461AB53687d48EEA26"})Provenance
RPC-pinned record: read over public JSON-RPC at the Ethereum block shown below and independently re-read at the same block by a second Pacta seat. It is not EAS-attested: no sprint number, no summary document and no Base EAS UID. Status Observed (RPC-observed baseline): the onchain control plane is pinned at block height; whether it matches the protocol's documented parameters is not assessed here (the documentation is linked for reference). Machine-readable: /api/v1/rpc-pinned.json. The Base-EAS-attested Sprint records are in /api/v1/index.json.
MigratableEntityProxy · EIP-1967 Proxy & Controller Chain
Observed onchain. MigratableEntityProxy (0xdC47953c816531a8CA9E1D461AB53687d48EEA26) verified on Ethereum Mainnet at canonical block #26,440,048 (808 bytes runtime code). EIP-1967 proxy: implementation 0xDd649AdaB2e67cAdC2EC29d75ABe73f3Df08065c, admin 0xAEb6bdd95c502390db8f52c8909F703E9Af6a346. The EIP-1967 admin slot holds contract VaultFactory 0xAEb6bdd95c502390db8f52c8909F703E9Af6a346. That controller is in turn controlled by Safe 2-of-3 0x5721ce64Ee0D772Ce613b62D411350091C544cD0.
Documentation (linked, not compared). K3 Capital documentation is linked for reference (https://docs.k3.capital/). This RPC-pinned record does not compare documentation parameters with the on-chain state.
cast storage 0xdC47953c816531a8CA9E1D461AB53687d48EEA26 \ 0xb53127684a568b3173ae13b9f8a6016e243e63b6e8ee1178d6a717850b5d6103 \ --block 26440048 --rpc-url "$ETH_RPC_URL" cast block 26440048 --field hash --rpc-url "$ETH_RPC_URL" # expect 0x2c6e70ac6ce978ce5c457208ea6d953e60e92ebf2151578f46cbdd070baa54c6
Control-plane badge: RPC-Observed
The slate badge states only what Pacta pinned on-chain; it makes no documentation claim until K3 Capital is compared with its documentation and attested on Base.
[](https://pacta.wtf/protocols/k3-capital/)
<a href="https://pacta.wtf/protocols/k3-capital/"><img src="https://pacta.wtf/badges/k3-capital.svg" alt="Pacta Control Plane: RPC-Observed" height="20"></a>
Badge: https://pacta.wtf/badges/k3-capital.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/k3-capital.svg.
Maintaining K3 Capital? 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).