Is-a-fork-of
Jupiter Perpetual Exchange's assessment for RD-F-126 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Jupiter Perps is an original implementation — not a fork of any existing protocol. Profile §5 explicitly states: 'Not forked / original. Jupiter Perps is an original implementation by the Jupiter (jup-ag) team in Anchor/Rust. There is no evidence of a fork relationship with any existing protocol.' No fork declaration found in jup-ag GitHub org. Architecture is analogous to GMX v1 conceptually but codebase is original.
Sources #
- GitHubjup-ag GitHub organizationjup-ag GitHub org — 185 public repositories searched; no perps source repo found; no fork declarationretrieved 2026-05-16
- 00-profile.md §5 Fork LineageProfile §5: 'Not forked / original. Jupiter Perps is an original implementation by the Jupiter (jup-ag) team in Anchor/Rust.'retrieved 2026-05-16
Methodology #
Identify the upstream protocol this is a fork of (if any) via bytecode similarity, function-selector set overlap, or team declaration.
See the full factor methodology and distribution across all protocols →