Upshift: control-plane safety record
1 indexed control-plane surface for Upshift, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0x4107…57F7
What differs
Changed / discrepant
- Vault ProxyAdmin multisig: docs state generally 4 of 6, the Safe is 2-of-3: Upshift vault 0xE9B725010A9E419412ed67d0fA5f3A5f40159D32 (Ethereum): EIP-1967 admin slot = ProxyAdmin 0xB5fBf201A35327Ddd89986FfA60CF5A675B2bDbc, whose owner() = Safe … observed vs 'Upgrades to the vault's code are approved by the ProxyAdmin multisig. documented
Show the full onchain evidence
Upshift vault 0xE9B725010A9E419412ed67d0fA5f3A5f40159D32 (Ethereum): EIP-1967 admin slot = ProxyAdmin 0xB5fBf201A35327Ddd89986FfA60CF5A675B2bDbc, whose owner() = Safe 0x4107557d726933f0BcA591A4218Afc92978457F7 with getThreshold() = 2 of getOwners() = 3 owners; the vault's owner() is a separate Safe 0x17ab7568Cd5386DF6C8E4552438E32794D057cC1 (2-of-3).
Show the full documented text
'Upgrades to the vault's code are approved by the ProxyAdmin multisig. It is generally a 4 of 6 Gnosis Safe with two signers each from the asset issuer, Upshift and the curator, so no single party can upgrade a vault alone.' (docs.upshift.finance/vault-architecture/risk-controls)
Protocol maintainer and fixed this gap? Get it re-verified on mainnet in 24h
Control-plane scorecard
Delta Docs and chain differ
- Upgradeability
- Weak · Upgradeable with no enforced delay: upgraded by a Safe directly (a Safe has no delay of its own)Evidence: upshift-proxyadmin-safe-s28: Upshift vault 0xE9B725010A9E419412ed67d0fA5f3A5f40159D32 (Ethereum): EIP-1967 admin slot = ProxyAdmin 0xB5fBf201A35327Ddd89986FfA60CF5A675B2bDbc, whose owner() …
- Timelock floor
- Weak · 0s minimum enforced delay across control surfacesEvidence: upshift-proxyadmin-safe-s28: Upshift vault 0xE9B725010A9E419412ed67d0fA5f3A5f40159D32 (Ethereum): EIP-1967 admin slot = ProxyAdmin 0xB5fBf201A35327Ddd89986FfA60CF5A675B2bDbc, whose owner() …
- Signer quorum
- Moderate · Lowest controlling quorum: 2-of-3Evidence: upshift-proxyadmin-safe-s28: … 0x17ab7568Cd5386DF6C8E4552438E32794D057cC1 (2-of-3).
- Emergency / freeze scope
- Not determined · No pause / freeze authority in the published records
- Docs-vs-chain parity
- Weak · Documentation differs from the chain (parameter delta)
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=0x4107557d726933f0BcA591A4218Afc92978457F7"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0x4107557d726933f0BcA591A4218Afc92978457F7"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0x4107557d726933f0BcA591A4218Afc92978457F7"})Provenance · research credit
Reported by @dankezo through the Pacta Wave 2 pool (PR #45, fixture bounties/wave-2/ethereum-upshift.json), merged under the Apache-2.0 commercial grant and paid $1.00 USDC (tx 0x3aac…ca8d); credited on upshift-proxyadmin-safe-s28. Pacta then re-read every value below on two independent RPCs at its own Sprint pin and compared it with the documentation; the classifications and the Base EAS attestation are Pacta's. See the leaderboard.
Vault ProxyAdmin multisig: docs state generally 4 of 6, the Safe is 2-of-3
Observed onchain. Upshift vault 0xE9B725010A9E419412ed67d0fA5f3A5f40159D32 (Ethereum): EIP-1967 admin slot = ProxyAdmin 0xB5fBf201A35327Ddd89986FfA60CF5A675B2bDbc, whose owner() = Safe 0x4107557d726933f0BcA591A4218Afc92978457F7 with getThreshold() = 2 of getOwners() = 3 owners; the vault's owner() is a separate Safe 0x17ab7568Cd5386DF6C8E4552438E32794D057cC1 (2-of-3).
Documented. 'Upgrades to the vault's code are approved by the ProxyAdmin multisig. It is generally a 4 of 6 Gnosis Safe with two signers each from the asset issuer, Upshift and the curator, so no single party can upgrade a vault alone.' (docs.upshift.finance/vault-architecture/risk-controls)
cast call 0x4107557d726933f0BcA591A4218Afc92978457F7 \ "getThreshold()" \ --block 26441165 --rpc-url "$ETH_RPC_URL" cast block 26441165 --field hash --rpc-url "$ETH_RPC_URL" # expect 0x5182be2c61af5f48ed2ec43d3c177dedad257c4e966a7e384120829de73901d9
Control-plane badge: Parameter Delta
This badge is amber because at least one Base-EAS-attested surface of Upshift differs from what the protocol documents. It turns to the neutral 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/upshift/)
<a href="https://pacta.wtf/protocols/upshift/"><img src="https://pacta.wtf/badges/upshift.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>
Badge: https://pacta.wtf/badges/upshift.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/upshift.svg.
Fixed this gap? 24h mainnet re-verification ($99 intro)
A maintainer and an independent verifier re-check Upshift on mainnet within 24h and attest the result on Base. The fee pays for the 24-hour mainnet re-verification work, never the grade: your attestation reads Aligned when on-chain controls match the published documentation, and Delta when they do not.
Maintaining Upshift? 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).