A checklist for Firedancer testnet milestones

Firedancer progress generates enthusiastic social posts. Our checklist keeps the weekly briefing grounded.

Build identifier and branch

We record the exact tag or commit hash referenced in release notes, not just "latest testnet." Branch names distinguish experimental features from merge candidates.

Known issue tracker status

Public GitHub issues labelled as blockers get a table row with last-updated dates. Resolved issues stay in the table for two editions so readers see closure, not amnesia.

Operator statements only with attribution

Tweet threads are summarized as "Operator X reported" with links. Anonymous claims stay out of paid PDFs unless corroborated by a second public source.

Compatibility notes for existing tooling

RPC method changes and snapshot formats affect downstream teams. We ask client contacts quarterly which tooling they run so compatibility rows stay relevant.

Exit criteria language

We quote activation criteria verbatim from official docs rather than paraphrasing optimism. If criteria are vague, that vagueness becomes an open question.