|
| 1 | +# Celestia Foundation Ecosystem Delegation Program |
| 2 | + |
| 3 | +## Table of Contents |
| 4 | +- [Program Overview](#program-overview) |
| 5 | +- [Basic Eligibility & Compliance](#basic-eligibility--compliance) |
| 6 | +- [Form Submission](#form-submission) |
| 7 | +- [Background](#background) |
| 8 | +- [Mamo-Users Rules & Requirements](#mamo-users-rules--requirements) |
| 9 | + - [Objectives & Key Metrics](#objectives--key-metrics) |
| 10 | + - [Example Submission for Mamo-Users](#example-submission-for-mamo-users) |
| 11 | +- [Bootcamp & Mammothon Rules & Requirements](#bootcamp--mammothon-rules--requirements) |
| 12 | + - [Scope & Deliverables](#scope--deliverables) |
| 13 | + - [Timeline & Cadence](#timeline--cadence) |
| 14 | + - [Participation & Scale](#participation--scale) |
| 15 | + - [Review Process](#review-process) |
| 16 | + - [Success Criteria](#success-criteria) |
| 17 | + - [Example Submission for Bootcamp/Mammothon](#example-submission-for-bootcampmammothon) |
| 18 | +- [R&D Rules & Requirements](#rd-rules--requirements) |
| 19 | + - [Scope](#scope) |
| 20 | + - [Milestone Reporting](#milestone-reporting) |
| 21 | + - [Review Process](#review-process-1) |
| 22 | + - [Success Criteria](#success-criteria-1) |
| 23 | + - [Example Submissions for R&D](#example-submissions-for-rd) |
| 24 | + |
| 25 | +## Program Overview |
| 26 | + |
| 27 | +| Parameter | Details | |
| 28 | +| --- | --- | |
| 29 | +| Cohort size | 10 validators total | |
| 30 | +| Duration of delegation | 6 months (July 2025–Dec 2025) | |
| 31 | + |
| 32 | +--- |
| 33 | + |
| 34 | +## Basic Eligibility & Compliance |
| 35 | + |
| 36 | +| Requirement | Description | |
| 37 | +| --- | --- | |
| 38 | +| Validator status | Active validator on mainnet or testnet | |
| 39 | +| Commission | Maximum commission of 10% | |
| 40 | +| Reliability | No more than 1 jailing incident in the last 6 months (if more than 1, a public forum post with a detailed post mortem is required) | |
| 41 | +| Independence | Not associated with an exchange or custodian | |
| 42 | +| Compliance | Not based within the US, within any country subject to economic sanctions, or within any other prohibited jurisdiction, and successfully complete a compliance screen | |
| 43 | +| Infrastructure | Maintain a fully archival (non-pruned) bridge node for both Mainnet Beta and Mocha if selected for the program | |
| 44 | +| Hosting | Not running your infrastructure in Hetzner or OVH | |
| 45 | +| Conduct | Violations of the Celestia.org Code of Conduct will result in immediate disqualification | |
| 46 | + |
| 47 | +--- |
| 48 | + |
| 49 | +## Form Submission |
| 50 | + |
| 51 | +Please send your application to this [form](https://forms.gle/Fbdo66W3GvCiQw896) |
| 52 | + |
| 53 | +## Background |
| 54 | +This 6-month pilot runs July–December 2025 and will result in the Celestia Foundation delegating to up to 10 validators. Every applicant must choose exactly one of our three tracks—Mamo-Users, Bootcamp & Mammothon, or R&D—and will be evaluated solely on that focus area. Eligibility and success criteria are defined separately for each track below. |
| 55 | + |
| 56 | +--- |
| 57 | + |
| 58 | +## Mamo-Users Rules & Requirements |
| 59 | + |
| 60 | +### Objectives & Key Metrics |
| 61 | + |
| 62 | +| Category | Requirements | |
| 63 | +| --- | --- | |
| 64 | +| **Recruitment** | • 100 total power users* onboarded by November | |
| 65 | +| **Events & Engagement** | • ≥ 1 app-focused meetup or AMA per month<br>• ≥ 10 attendees at each meetup/AMA<br>• Weekly discussion threads on Discord/forum | |
| 66 | +| **Content Production** | • 6 native-language app tutorials or blog posts (1/month)<br>• 6 review videos of Celestia dApps (1/month)<br>• All high-quality content released under CC0 or equivalent | |
| 67 | +| **Evangelism & Feedback** | • Active promotion of Bootcamp & Mammothon outputs in each report<br>• Aggregate and escalate user feature-requests in Celestia Discord/forum | |
| 68 | +| **Community Health** | • Track retention: power users who contribute (reviews, threads, evangelism)<br>• By Month 6, identify a shortlist of "rising stars" in your local community | |
| 69 | + |
| 70 | +> \*Power User in the Celestia ecosystem is an active, engaged advocate who: |
| 71 | +
|
| 72 | +| Characteristic | Description | |
| 73 | +| --- | --- | |
| 74 | +| **Regularly Uses Apps** | Interacts daily or weekly with Celestia-powered applications, test pilots early access features without handholding | |
| 75 | +| **Gives Actionable Feedback** | Opens tutorial threads, participates in Q&A, and responds to surveys to make products better | |
| 76 | +| **Creates & Shares Content** | Publishes high-quality native-language tutorials or short review videos highlighting real-world use | |
| 77 | +| **Evangelizes Authentically** | Recommends apps to peers at meetups or online, acting as an informal ambassador | |
| 78 | +| **Leads Locally** | Organizes testing groups, spawns discussion threads, mentors newcomers, and escalates critical insights to Community Managers | |
| 79 | + |
| 80 | +| Category | Details | |
| 81 | +| --- | --- | |
| 82 | +| **Penalties** | Missing a monthly report or skipping the required event ⇒ immediate disqualification | |
| 83 | +| **Out-of-Scope** | Bootcamp/Mammothon programming, R&D/CIP work, general protocol marketing | |
| 84 | +| **Licensing** | All user-facing content must be released under CC0 (or similarly permissive public-domain terms) | |
| 85 | + |
| 86 | +#### Example Submission for Mamo-Users |
| 87 | +<details> |
| 88 | +<summary>Click to expand example</summary> |
| 89 | + |
| 90 | +| Month | Event Type | Activities | |
| 91 | +| --- | --- | --- | |
| 92 | +| **M1** | Virtual AMA | • Topic: "Which Celestia dApps do you use daily?" (15 attendees)<br>• Gather feedback on existing apps<br>• Discuss how Bootcamp can grant early-alpha access<br>• Publish recap on Discord & Twitter | |
| 93 | +| **M2** | In-person meetup | • Hands-on testing of three flagship dApps<br>• 12 power users document UX pain points<br>• Collate feedback for Bootcamp teams on how users discover and adopt alphas | |
| 94 | +| **M3** | Virtual AMA | • Review updated dApp versions<br>• Solicit feature requests and "wish-list" items (20 attendees)<br>• Share a "User Adoption Guide" draft for Bootcamp cohorts | |
| 95 | +| **M4** | In-person meetup | • Mammothon idea-pitch event<br>• Power users vote on top 5 hackathon themes based on user demand<br>• Publish pitch summaries and vote results on forum + Twitter | |
| 96 | +| **M5** | Virtual AMA | • Mammothon kickoff—introduce allowlisted ideas<br>• Advise hacker teams on engaging power users for early testing (25 attendees)<br>• Post "How to Reach Your First 50 Users" guide tailored to chosen hackathon themes | |
| 97 | +| **M6** | In-person meetup | • Preview of early hackathon prototypes<br>• Power users provide live feedback and adoption tactics<br>• Release a "Community Impact Report" detailing recruitment, retention, feedback loops, and rising-star power users | |
| 98 | +</details> |
| 99 | + |
| 100 | +--- |
| 101 | + |
| 102 | +## Bootcamp & Mammothon Rules & Requirements |
| 103 | + |
| 104 | +### Scope & Deliverables |
| 105 | + |
| 106 | +| Deliverable | Description | |
| 107 | +| --- | --- | |
| 108 | +| **Community Outreach** | Host local meetups (dev & product) to promote Celestia Bootcamp (July–Aug) and Mammothon (Sep–Oct) | |
| 109 | +| **Participant Funnel** | Drive recruited attendees into both programs; celebrate completions with exit events | |
| 110 | +| **Weekly Pit-Stops** | During Bootcamp/Mammothon, run ≥ 1 check-in per week to motivate and troubleshoot | |
| 111 | +| **Translations & Workshops** | Translate in-house learning materials; optionally host validator-onboarding workshops (must notify council) | |
| 112 | + |
| 113 | +### Timeline & Cadence |
| 114 | + |
| 115 | +| Period | Activities | |
| 116 | +| --- | --- | |
| 117 | +| **Jul (Recruitment Warm-Up)** | ≥ 1 local promo event per month | |
| 118 | +| **Aug-Sep** | Execute Bootcamp programming & weekly pit-stops | |
| 119 | +| **Oct-Nov** | Run Mammothon hackathon & weekly pit-stops | |
| 120 | +| **Dec** | Wrap up what local talent has delivered as an event | |
| 121 | +| **Reporting** | For each month, deliver a written + social-media report at least 24 h before the B&M council sync | |
| 122 | + |
| 123 | +### Participation & Scale |
| 124 | + |
| 125 | +| Aspect | Requirement | |
| 126 | +| --- | --- | |
| 127 | +| **Recruitment Target** | Recruit ≥ 50 individuals or 10 teams (3–5 members each) per applicant for bootcamps and mammothons participation | |
| 128 | +| **Mentorship Format** | (one-on-one or group) at team’s discretion | |
| 129 | + |
| 130 | +### Review Process |
| 131 | + |
| 132 | +| Component | Details | |
| 133 | +| --- | --- | |
| 134 | +| **Monthly B&M Council Sync** | Present outreach stats, pit-stop summaries, and issue resolutions | |
| 135 | +| **Attendance Policy** | Live attendance may be waived if all written reports and community responses are complete | |
| 136 | + |
| 137 | +### Success Criteria |
| 138 | + |
| 139 | +| Criterion | Target | |
| 140 | +| --- | --- | |
| 141 | +| **Bootcamp** | ≥ 50% of recruited participants complete the program | |
| 142 | +| **Mammothon** | ≥ 30% of Bootcamp graduates (and new public sign-ups) finish & submit a built application | |
| 143 | +| **Competition Results** | Produce at least 1 winner (or 2 semi-finalists) in the hackathon | |
| 144 | + |
| 145 | +| Category | Details | |
| 146 | +| --- | --- | |
| 147 | +| **Penalties** | Missing a monthly report or weekly pit-stop ⇒ immediate disqualification | |
| 148 | +| **Out-of-Scope** | • Working with pre-existing, production-grade teams or products<br>• Gambling or unrelated hackathon content | |
| 149 | +| **Licensing** | All created materials must be open-sourced | |
| 150 | + |
| 151 | +#### Example Submission for Bootcamp/Mammothon |
| 152 | +<details> |
| 153 | +<summary>Click to expand example</summary> |
| 154 | + |
| 155 | +| Month | Activities | |
| 156 | +| --- | --- | |
| 157 | +| **M1** | • Host first local meetup to announce Celestia Bootcamp<br>• Recruit ≥ 20 devs<br>• Translate Week 1 slides<br>• Publish a forum post + tweet<br>• Hold second meetup focused on career pathways through hackathons<br>• Recruit additional ≥ 30 individuals<br>• Finalize pit-stop schedule<br>• Share update on Discord/Twitter | |
| 158 | +| **M2** | • Kick off Bootcamp Month 1<br>• Run weekly pit-stop check-ins<br>• Post attendance stats & participant feedback to forum + socials | |
| 159 | +| **M3** | • Conclude Bootcamp<br>• Host exit celebration event<br>• Report 50%+ completion rate<br>• Gather testimonials<br>• Publish a wrap-up thread | |
| 160 | +| **M4** | • Activate Mammothon<br>• Onboard participants (Bootcamp grads + public)<br>• Facilitate team formations and ideas selection / commitment | |
| 161 | +| **M5** | • Run pit-stops for teams locally<br>• Motivate team progress with help on sharing progress to the broader audience<br>• If applicable, help or be teams' first users | |
| 162 | +| **M6** | • Close Mammothon<br>• Report ≥ 30% finish rate<br>• Open-source all demo projects<br>• Publish final outcomes | |
| 163 | +</details> |
| 164 | + |
| 165 | +--- |
| 166 | + |
| 167 | +## R&D Rules & Requirements |
| 168 | + |
| 169 | +### Scope |
| 170 | + |
| 171 | +| Category | Description | |
| 172 | +| --- | --- | |
| 173 | +| **CIPs** | Research & propose protocol improvements (e.g. fee-models, staking incentives); produce Celestia Improvement Proposals with simulations or data analysis | |
| 174 | +| **Public-Goods Tooling** | Develop open-sourced libraries/SDKs for JSON-RPC or canonical APIs (e.g. Python, JavaScript), or reusable CLIs for developer workflows | |
| 175 | +| **Duration** | 6 months | |
| 176 | +| **Deliverable Volume** | Teams may tackle multiple CIPs and/or tools as they choose | |
| 177 | + |
| 178 | +### Milestone Reporting |
| 179 | + |
| 180 | +| Requirement | Details | |
| 181 | +| --- | --- | |
| 182 | +| **Monthly Demo** | Recorded video + written summary published at least 24 h before the R&D council sync | |
| 183 | +| **Feedback Response** | Must address council comments and community feedback on the forum/socials within 2 weeks of receipt | |
| 184 | +| **Communication Channels** | Celestia Forum, X and Discord required; other platforms optional | |
| 185 | + |
| 186 | +### Review Process |
| 187 | + |
| 188 | +| Component | Details | |
| 189 | +| --- | --- | |
| 190 | +| **Monthly R&D Council Sync** | Live attendance may be waived if demos, write-ups, and feedback responses are all complete | |
| 191 | + |
| 192 | +### Success Criteria |
| 193 | + |
| 194 | +| Area | Target | |
| 195 | +| --- | --- | |
| 196 | +| **CIPs** | ≥ 1 proposal advances to "beyond Draft" and is featured on a Core Devs call, with clear ownership and resolved feedback | |
| 197 | +| **Tooling** | Adoption by ≥ 1–2 external teams (e.g. Mammothon or Bootcamp cohorts); bonus for third-party startup integration | |
| 198 | +| **Penalties** | Missing a demo/report deadline or failing to address feedback on time ⇒ immediate disqualification | |
| 199 | + |
| 200 | +#### Example Submissions for R&D |
| 201 | +<details> |
| 202 | +<summary>Click to expand example</summary> |
| 203 | + |
| 204 | +**1. CIP: "Dynamic Data Availability Fees"** |
| 205 | + |
| 206 | +| Month | Deliverables | |
| 207 | +| --- | --- | |
| 208 | +| **M1** | • Publish forum post with proposal outline<br>• Promote via Twitter thread | |
| 209 | +| **M3** | • Share on-chain simulation results<br>• Respond to community Q&A on forum & Discord | |
| 210 | +| **M6** | • Submit final CIP<br>• Present on a Celestia Core Devs call | |
| 211 | + |
| 212 | +**2. Tooling: "py-celestia-node-rpc"** |
| 213 | + |
| 214 | +| Month | Deliverables | |
| 215 | +| --- | --- | |
| 216 | +| **M1** | • Repository skeleton + basic JSON-RPC wrapper | |
| 217 | +| **M4** | • Release v1.0 (support subscriptions + tests)<br>• Demo recording + write-up on Discord & Twitter | |
| 218 | +| **M6** | • Enable two Bootcamp teams to build MVPs using the library<br>• Collect adoption feedback | |
| 219 | + |
| 220 | +**3. Tooling: "bridge-health-checker"** |
| 221 | + |
| 222 | +| Month | Deliverables | |
| 223 | +| --- | --- | |
| 224 | +| **M1** | • Repo skeleton + CLI that reads DA bridge node disk usage<br>• Forum post + Twitter announcement | |
| 225 | +| **M2** | • Add PagerDuty integration + unit tests + CI<br>• Demo recording + write-up on Discord & Twitter | |
| 226 | +| **M3** | • Onboard 3–5 validators<br>• Collect usage metrics & feedback<br>• Publish adoption report | |
| 227 | +</details> |
0 commit comments