Sybil surge of identical-pattern transactions

Jupiter's assessment for RD-F-097 — scored not_assessed on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

v1-deferred per T-09 §3.3. Historical Sybil event (Jan 2024 airdrop claim, 9,000+ wallets, ~$1M) was against airdrop claim contract, not core protocol programs. No active Sybil surge on core swap/perps contracts detected. v1-deferred prevents current scoring.

Sources #

Internal
Jupiter Protocol Profile §10Profile §10: airdrop claim drainer Jan 2024 used 9,000+ wallets for claim contract Sybil; remediatedretrieved 2026-04-29
Internal
T-09 Real-Time Signals v1 Scope — v2/deferred tableT-09 §3.3 v2/deferred — F105 Sybil transaction burstretrieved 2026-04-29

Methodology #

Detect multiple new EOAs submitting identical transaction patterns within a short window (sybil setup pattern).

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol jupiter factor RD-F-097 score not_assessed collected_at 2026-04-29 11:51:25