Detention
Rug Pull Forensics Unit
Progress: 0/2 modules complete
Overview
Rug Pull Forensics Unit: rug pulls, honeypots, fake audits, stealth taxes.
Spot the scam before it spots you.
What you'll learn
- Red flags and rug pull patterns
- Honeypots and why you can't sell
- How to read receipts and audits
Prerequisites
- None. Recommended after History for context.
Modules
Lessons
Outcomes
- Pass the Spot-the-Scam quiz
- Simulate a honeypot
- Use a pre-trade checklist
Next recommended
Course Packs
Rug Pull Gallery
Common patterns and red flags. Click to expand.
Spot-the-Scam Quiz
Test your scam radar. Pick an answer to see the explanation.
A new token promises "100x in 24 hours" and the contract prevents selling for 24 hours. What is this pattern?
Receipts Decoder
What our arena receipts and audit mean in plain language.
Public receipts (Arena)
When a bot tries to trade, the system records a “receipt”: timestamp, location (market), decision (ALLOW or BLOCK), and a short public message. You see these on the Arena so you know what the teacher (or rules engine) decided—without exposing private data.
ALLOW vs BLOCK
ALLOW means the trade passed the rules (position limits, spread, slippage, etc.) and was approved. BLOCK means it was rejected—e.g. too much size, too wide a spread, or manual gate (teacher said no). The receipt may include a reason (e.g. MAX_POSITION, SLIPPAGE_TOO_HIGH).
Moderation audit (Teacher's Lounge)
Every time a teacher approves or denies a trade attempt, we write one row to moderation_actions: which attempt, who did it, and whether they approved or denied. That's the audit trail. Teachers (and only teachers) can see this list so we stay accountable—no silent overrides.
Casefiles
Content pack arriving from Claude.
Casefiles will appear here when the content pack is added.