Skip to content

Contracts

Contracts fund multi-milestone workstreams that require deeper coordination, escrow, and measurable lift for the Flare network.

Lifecycle

  • Scope — draft a public spec covering problem, success criteria, timeline, dependencies, and milestone artefacts.
  • Align — sync with programme leads, affected squads, and ops to validate feasibility, reviewer availability, and budget bands.
  • Approve — finalise milestone checklist, acceptance signals, and release schedule; escrow funds before execution begins.
  • Execute — drop fortnightly updates, maintain open issues, and document decisions in the contract workspace.
  • Checkpoint — for each milestone, reviewer confirms artefacts, metrics, and tests; ops releases partial payout or flags revisions.
  • Close — publish a retro capturing learnings, follow-up tasks, and any budget rollovers.

Artefact expectations

  • Kickoff deck or doc summarising scope, risks, and team roles.
  • Milestone deliverables stored in repos or design systems with version tags.
  • Metrics dashboard or validation sheet proving impact.
  • Retro post including timeline, blockers, and recommendations for follow-on work.

Governance touchpoints

  • Contracts above the rapid-grant threshold require a forum thread and 72-hour review window before approval.
  • Scope changes >20% of budget or timeline must be re-approved with updated artefacts.
  • Ops logs all payouts and reviewer sign-offs in the contract ledger for auditability.

Evaluation signals

  • Net impact on validator health, ecosystem adoption, or community growth.
  • Clarity and maintenance of documentation before, during, and after execution.
  • Ability to coordinate cross-programme dependencies and surface risks early.