Skip to content
SIH Buddyby Ganeev Singh
Dev

🔥 Roast My Pick · SIH26183

Real-Time Identification of Fraud-Linked Cryptocurrency Exchanges from Victim-Reported Suspect Wallet Addresses through Automated Blockchain Analytics

Ministry of Home Affairs

Medium39/100

Reasonable choice. The scoreboard liked it. The scoreboard is not the one asking questions on the day.

Worth considering. Nearly the same problem as SIH26182 with a victim-report framing and harder real-time and mixer requirements — pick one of the two, not both, and if this one, make the laundering-pattern detection your distinctive contribution and be honest that mixers and bridges defeat the trace. Roughly 70–160 teams are expected to go here.

The receipts

Every red flag on this statement, in full. These are the four places it bites.

  1. Exhibit A

    It overlaps SIH26182 from the same ministry so heavily that the two are nearly the same product with different entry points

  2. It gets worse

    The description names mixers, bridges and DeFi as in-scope, and these are exactly the mechanisms that break blockchain tracing

  3. Still reading?

    Attribution accuracy is capped by the sparse public VASP label set, the same constraint as its sibling

  4. And the finisher

    Commercial tools already do near-real-time crypto tracing, so the novelty bar is set high

The damage report

Every score this statement earned, and what each one actually costs you.

  • Feasibility

    3/5

    Buildable. Not comfortably. There is a week in here you have not planned for yet.

    The same public-chain tracing and clustering as its sibling apply and are achievable, but the near-real-time requirement across multiple chains and the DeFi, mixer and bridge cases the description explicitly names are genuinely hard, and attribution still depends on the sparse public VASP labels.

  • Innovation scope

    3/5

    Mildly interesting. The novelty will not carry the room; the build has to.

    This is largely the same tracing-and-clustering problem as SIH26182 with a victim-report entry point and added laundering-pattern detection, so the room is in the pattern detection and real-time performance rather than in a new concept.

  • Clarity

    5/5

    The ask is unambiguous, which quietly removes your favourite excuse.

    The description enumerates the ingestion source, the tracing and clustering tasks, the specific hard cases — mixers, bridges, DeFi — the portal integrations and the dashboard outputs, making it precisely specified.

  • Acceptance potential

    3/5

    Middle of the pack. This statement will not win the room for you — you will have to.

    Genuinely useful and precisely specified, but it overlaps SIH26182 so closely that a judge may treat them as one, commercial tools already do this, the label-set dependency caps attribution, and the mixer, bridge and DeFi cases it explicitly names are exactly where tracing breaks.

  • Effort

    Massive

    A semester of work wearing a hackathon costume. Something is getting cut; decide what now, not in week five.

    Near-real-time multi-chain tracing, laundering-pattern detection, cross-chain handling, risk categorisation and portal integration is a large, demanding build.

  • Demo-ability

    Easy

    Easy to demo — and so is everyone else's. Working is the floor here, not the achievement.

    Tracing a reported wallet through its laundering hops to an exchange, with intermediaries flagged, is a concrete and compelling investigative demo.

  • Data

    None supplied

    No dataset comes with this one, so every accuracy figure you quote is a number about labels you invented.

    Nothing is provided with the statement. You are sourcing, cleaning and labelling it yourself, and that work is invisible in the demo but very visible in the questions.

The demo they will have already seen

Somewhere around 70–160 teams are heading here, and the description is doing the choosing for most of them. They will read the same brief, reach the same architecture, and build a version of the same demo you are planning. Being correct is the floor. If your five minutes could be swapped with the team before you and nobody in the room would notice, you have not picked badly — you have built predictably, which costs exactly the same and hurts more.

What survives

The ground worth standing on when the questions start.

  • Public blockchain data means the tracing runs on real on-chain data with no access barrier
  • The victim-report entry point and portal integration give it a clear operational workflow a judge can follow
  • Flagging intermediary laundering wallets along the trace is a genuinely useful investigative output beyond bare attribution

Nothing here is fatal. It is just the list of places this statement pushes back, and you now get to push there first.

Full analysis ↗Roast another

The framing is a joke. The findings are not — they are the same analysis on the statement page, and every line above is attached to a score or a fact in the record. It is one opinion with its reasoning attached, so argue with it before you trust it.