JPY DeFi: control-plane safety record
1 indexed control-plane surface for JPY DeFi, 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: 0x6042…20e4
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: jpy-defi-control-plane: is_eip1967_proxy = true
- Timelock floor
- Not determined · No enforced admin delay in the published records
- 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
- 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=0x6042755eCCa71A1Be9C7091441ca5bEaA6b520e4"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0x6042755eCCa71A1Be9C7091441ca5bEaA6b520e4"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0x6042755eCCa71A1Be9C7091441ca5bEaA6b520e4"})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.
CollateralVault · EIP-1967 Proxy & Controller Chain
Observed onchain. CollateralVault (0x6042755eCCa71A1Be9C7091441ca5bEaA6b520e4) verified on Ethereum Mainnet at canonical block #26,448,221 (170 bytes runtime code). EIP-1967 proxy: implementation 0x878dA559D17458d84fD7A42804CCAEA53C2F10B5, admin slot zero. No owner(), admin(), authority(), curator() or AccessControl admin was readable on the contract.
Documentation (linked, not compared). JPY DeFi documentation is linked for reference (https://jpydf.gitbook.io/jpy-defi). This RPC-pinned record does not compare documentation parameters with the on-chain state.
cast call 0x6042755eCCa71A1Be9C7091441ca5bEaA6b520e4 \ "owner()" \ --block 26448221 --rpc-url "$ETH_RPC_URL" cast block 26448221 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xa7818c0e1b8807aac0c999c2dc9aeeea40b91b4f19b1b76a62ad02d8d17607c8
Control-plane badge: RPC-Observed
The slate badge states only what Pacta pinned on-chain; it makes no documentation claim until JPY DeFi is compared with its documentation and attested on Base.
[](https://pacta.wtf/protocols/jpy-defi/)
<a href="https://pacta.wtf/protocols/jpy-defi/"><img src="https://pacta.wtf/badges/jpy-defi.svg" alt="Pacta Control Plane: RPC-Observed" height="20"></a>
Badge: https://pacta.wtf/badges/jpy-defi.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/jpy-defi.svg.
Fixed this gap? 24h mainnet re-verification ($99 intro)
A maintainer and an independent verifier re-check JPY DeFi 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 JPY DeFi? 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).