Bytecode similarity to audited upstream with behavior deviation
Jupiter's assessment for RD-F-171 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No audited upstream protocol to compare bytecode against (Jupiter is original). EVM bytecode diff tools do not apply to Solana BPF programs. Closed-source binary additionally prevents bytecode derivation from source. Double N/A: no fork + no accessible source + non-EVM substrate.
Sources #
- Curator note00-profile.md §5; process-learnings.md §Non-EVMNot a fork (profile §5); closed-source binary; non-EVM substrate — all three conditions make this N/Aretrieved 2026-04-29
Methodology #
Determine whether the bytecode has high structural similarity to an audited upstream but deviates in state-mutation ordering (AI-generated copy risk pattern).
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol jupiter factor RD-F-171 score not_applicable collected_at 2026-04-29 11:51:25