★ Contract unverified on Etherscan/Sourcify
Jupiter Perpetual Exchange's assessment for RD-F-046 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Program PERPHjGBqRHArX4DySjwM6UJHiR3sWAatqfdBS2qQJu confirmed NOT VERIFIED on verify.osec.io as of 2026-05-16. API response: is_verified=false, on_chain_hash empty, executable_hash empty, no repository URL, no commit reference. Source code is not publicly available — 185 jup-ag GitHub repos searched, no perps source repo found. Third-party IDL parsers exist but IDL does not constitute source verification. The Squads v4 4-of-7 authority data does not change this finding — the program binary remains unverifiable. This is the Solana equivalent of unverified at launch (no reproducible build hash).
Sources #
- URLOtterSec Program Verification Status — PERPHjGBqRHArX4DySjwM6UJHiR3sWAatqfdBS2qQJuverify.osec.io status check: is_verified=false, on_chain_hash='', executable_hash='', no repo URL — confirmed closed-source unverified binaryretrieved 2026-05-16
- Jupiter GitHub organizationgithub.com/jup-ag: 185 public repositories searched; no Jupiter Perps smart contract source repository foundretrieved 2026-05-16
Methodology #
Determine whether the protocol's deployed contracts have source code verified on Etherscan or Sourcify (public ABI available).
See the full factor methodology and distribution across all protocols →