A software platform that automatically traces unknown cryptocurrency wallets across multiple blockchains to identify the nearest Virtual Asset Service Provider and generates investigation reports for law enforcement agencies.
Ministry of Home Affairs · Indian Cyber Crime Coordination Centre (I4C),CIS Division · Software
Signing in saves it for your whole team — everyone on your invite link sees the same two entries. Anything you shortlisted while signed out comes with you.
Decomposed from what the description asks for. Nothing added.
Blockchain Trace Engine
Automatically traces transaction paths across multiple blockchain networks to find deposit addresses.
VASP Attribution and Tagging
Identifies exchange clusters, custodial wallets, and mixers while providing confidence scoring.
SAHYOG Portal Integration
Integrates with the platform through APIs to route lawful disclosure and freezing requests.
Investigation Dashboard
Provides visualization of fund movement, case analytics, and risk classification for law enforcement.
Automated Report Generator
Generates investigation-ready reports and alerts for high-risk wallets.
Both columns are read off the brief's own wording. Nothing here is inferred from the ministry's name.
The evaluators will check if the system can accurately trace transactions across multiple specified blockchain networks, integrate with the SAHYOG Portal via APIs, and correctly attribute unknown wallets to the nearest VASP with confidence scores.
A jury can still ask about these. Decide them deliberately rather than by accident.
Generated from the brief's own wording and the competition's published rules — never from a guess about what this ministry prefers.
Specific blockchain intelligence APIs to be used?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Exact data schemas for SAHYOG Portal integration?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Quantitative accuracy targets for VASP attribution?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Access credentials or API keys for live blockchain data?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Each one is quoted from a gap in the brief, not a guess about your team.
Needs data you may not get
The system requires integration with the SAHYOG Portal and access to specialized blockchain intelligence APIs which students typically cannot obtain.
What the organisers attached, and what the brief assumes you can get.
Same organisation, same year. Reading two of theirs tells you more about what they care about than reading one.
Pick what you are about to do and copy the prompt. It carries the organisers' own wording, the constraints they never spell out, and an instruction not to invent requirements they never set.
Who has this problem, what already exists, and what you would have to find out.
Has any part of this been shown at a previous event, hackathon or college project?
The guidelines are explicit: your solution must not have appeared in any previous event or programme, of any sort. A recycled project is what a team under time pressure reaches for.
The brief asks for blockchain trace engine. How would you build that?
Decoded from SIH26182 itself — Automatically traces transaction paths across multiple blockchain networks to find deposit addresses. The brief asks for it by name.
The brief asks for vasp attribution and tagging. How would you build that?
Decoded from SIH26182 itself — Identifies exchange clusters, custodial wallets, and mixers while providing confidence scoring. The brief asks for it by name.
The brief asks for sahyog portal integration. How would you build that?
Decoded from SIH26182 itself — Integrates with the platform through APIs to route lawful disclosure and freezing requests. The brief asks for it by name.
The brief asks for investigation dashboard. How would you build that?
Decoded from SIH26182 itself — Provides visualization of fund movement, case analytics, and risk classification for law enforcement. The brief asks for it by name.
The brief asks for automated report generator. How would you build that?
Decoded from SIH26182 itself — Generates investigation-ready reports and alerts for high-risk wallets. The brief asks for it by name.
Where does your data come from — a published source, one you collect, or one you generate?
No dataset is attached to this problem statement, so sourcing it is part of the work and nobody told you that.
Why not use what already exists? Name the closest thing to this that is already running.
A team that has not named the alternative themselves is answering this for the first time in the room.
Which single thing will you demonstrate end to end, start to finish, with nothing skipped?
Ours, not a rule: a narrow thing that fully works survives questioning better than a broad thing that half works. If nobody on the team can name it, that is the finding.
Show me this working: the evaluators will check if the system can accurately trace transactions across multiple specified blockchain networks, integrate with the SAHYOG Portal via APIs, and correctly attribute unknown wallets to the nearest VASP with confidence scores.
This is the evaluator read for your problem statement, decoded from the brief's own wording.