# Demo Video Script

How to record a compelling 3-minute hackathon demo.

## Structure (3 minutes total)

### 0:00-0:20 — Hook (20 seconds)
- State the problem in one sentence
- Show a visual that makes the problem real
- "Imagine you're a [persona] and you need to [task]..."

### 0:20-0:40 — Solution Overview (20 seconds)
- What does your project do? (one sentence)
- Quick architecture diagram or flow chart
- "Here's how [Project Name] solves this..."

### 0:40-2:20 — Live Demo (100 seconds)
- Show the CORE flow end-to-end
- Click through the actual product (not slides)
- Narrate each step: what you're doing and why
- Show the Solana transaction on Explorer as proof
- If something loads slowly, cut the video (don't wait on camera)

### 2:20-2:50 — Technical Highlight (30 seconds)
- One impressive technical detail
- "Under the hood, we're using [Solana feature] to..."
- Show a code snippet or architecture diagram briefly
- Keep it to ONE thing — don't explain the whole stack

### 2:50-3:00 — Wrap Up (10 seconds)
- What's next?
- Call to action: try it, star the repo, follow for updates
- Thank the hackathon organizers

## Recording Tips

1. **Resolution**: 1080p minimum
2. **Audio**: Use a decent microphone, quiet room
3. **Screen**: Clean desktop, hide bookmarks bar, increase font size
4. **Pace**: Speak slightly slower than normal
5. **Edits**: Cut dead time (loading, typing). Keep it tight.
6. **Browser**: Use a clean browser profile (no personal bookmarks/tabs)

## Tools

- **Screen recording**: OBS (free), Loom, QuickTime
- **Video editing**: DaVinci Resolve (free), iMovie
- **Thumbnails**: Canva

## Anti-Patterns

- Don't start with "Hi, I'm [name] and this is my project" — start with the problem
- Don't show your terminal for more than 15 seconds
- Don't apologize for bugs — either fix them or cut around them
- Don't read from a script on camera — use bullet points
- Don't go over 3 minutes. Judges stop watching.