Membership Tiers
Membership is earned by compounding verified proof-of-work and stewardship inside the Flare network. Each tier unlocks new surface area, from early context to capital allocation.
Tier map
| Tier | Signals | Access | Review focus |
|---|---|---|---|
| Tier 1 — Launchpad | First shipped bounty or event support, consistent updates, clear artefacts | Read-only programme boards, learning cohorts, public calls | Reliability, clarity of documentation, responsiveness |
| Tier 2 — Operator | Multiple shipped scopes with measurable lift, peer endorsements, call participation | Priority placement on bounties/contracts, internal syncs, proposal co-authorship | Impact on ecosystem metrics, collaboration quality, feedback loops |
| Tier 3 — Steward | Leads initiatives, unblocks squads, drives partnerships, mentors talent | Budget recommendations, cross-programme governance, external representation | Strategic leverage, delegation effectiveness, repeatable playbooks |
Earning the next tier
Launchpad → Operator
- Ship at least two distinct scopes (bounty, contract, event) with artefacts logged in the proof-of-work tracker.
- Participate in minimum two community calls with demo, retro, or Q&A contribution.
- Secure one peer testimonial highlighting collaboration and delivery speed.
Operator → Steward
- Lead an initiative spanning multiple contributors with published scope, updates, and retro.
- Demonstrate measurable ecosystem lift (usage, integrations, validator metrics, or community growth) tied to your work.
- Sponsor or mentor another contributor through a full delivery cycle, documenting the playbook.
Review cadence
- Reviews run on a six-week heartbeat led by programme ops; urgent escalations can be requested via the ops form.
- Evidence lives in the proof-of-work tracker—include repo links, dashboards, call recordings, or specs.
- Decisions are logged in the forum with acceptance notes and next-step guidance so contributors understand how to keep momentum.
Maintaining standing
- Stay active in agreed surfaces; prolonged inactivity (two cycles) triggers a friendly check-in.
- If deliverables slip, share blockers openly and align on new checkpoints to avoid trust erosion.
- Mentoring, documentation, and community building help sustain higher tiers even when personal bandwidth shifts.