Bytecode similarity to audited upstream with behavior deviation
Uniswap (v2 + v3)'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 #
V2 and V3 are original protocols. No audited upstream exists to compare against for bytecode similarity / behavior deviation (AI-copy risk). This factor applies to AI-generated forks mimicking an audited protocol while deviating in behavior. Not applicable.
Detail #
This factor was designed for the class of forks where an AI tool generates code closely resembling an audited upstream (e.g., Aave V2) but with subtle behavioral deviations in state mutation ordering. Since V2 and V3 are themselves the canonical originals, there is no upstream to compare against. Uniswap V2 and V3 are more likely to be the TARGET of this pattern by their forks than to exhibit it themselves.
Sources #
- DocsUniswap V3 whitepaper — original human-authored codebaseV3 whitepaper — original human-designed protocolretrieved 2026-05-12
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 →