Is-a-fork-of
Cap (cUSD / stcUSD)'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 #
Cap is an original architecture — not a fork of any existing protocol. The GitHub README states: 'This repository contains the core contracts for the CAP platform.' No fork claim in README, docs, or any audit report. Cap integrates LayerZero OFT, Symbiotic, EigenLayer, Aave V3, and OZ libraries as integrations, not as a fork of a single upstream. Not applicable per protocol-type guidance.
Sources #
- InternalCap Profile §5 — Fork Lineage00-profile.md §5 — 'Not forked / original'retrieved 2026-05-17
- Cap Contracts Repository READMEcap-labs-dev/cap-contracts README — 'core contracts for the CAP platform'; no upstream fork declaredretrieved 2026-05-17
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 →