What makes a good milestone
- Specific Clear deliverable (e.g., “API documentation published,” “Alpha deployed to testnet”).
- Verifiable Reviewer can check completion (link, report, demo).
- Scoped One main outcome per milestone; avoid bundling too much.
- Ordered Sequence that makes sense (e.g., design before build, testnet before mainnet).
Example structure
| Milestone | Deliverable | Payout % |
|---|---|---|
| 1 | Project spec and timeline | 20% |
| 2 | Alpha / MVP | 40% |
| 3 | Documentation and open-source release | 20% |
| 4 | Mainnet or production launch | 20% |
When applying
- In your application, list each milestone with a short description and expected date.
- Match the program’s requested format (e.g., table, form fields).
When delivering
- Submit exactly what the milestone describes so reviewers can approve without ambiguity. See Milestone delivery.