Update foundation-delegation-program.md#2003
Conversation
WalkthroughThe changes update the "foundation-delegation-program.md" documentation by simplifying the cohort structure, removing specific program start dates, and streamlining the eligibility and application requirements. The tiered cohort system is replaced with a uniform structure, and eligibility criteria regarding validator jailing are refined. Application requirements are reduced, and the contributions section is consolidated. No code or exported entities are affected; the modifications are limited to documentation content. Changes
Sequence Diagram(s)Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Note ⚡️ AI Code Reviews for VS Code, Cursor, WindsurfCodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback. Note ⚡️ Faster reviews with cachingCodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 30th. To opt out, configure Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (5)
community/foundation-delegation-program.md (5)
41-44: Standardize bullet phrasing
Consider using consistent verb tense and phrasing for readability. For example, change “Each Cohort has to renew in 12 months” to “Each cohort renews after 12 months.”- * Each Cohort has to renew in 12 months. + * Each cohort renews after 12 months.
66-68: Add comma for clarity in performance clause
Insert a comma before “so that” to improve readability:- (for new applicants - on testnet, so that we can evaluate performance) + (for new applicants – on testnet, so that we can evaluate performance)🧰 Tools
🪛 LanguageTool
[typographical] ~67-~67: The conjunction “so that” does not have a comma in front.
Context: ...ics.md) (for new applicants - on testnet, so that we can evaluate performance) * Not jail...(SO_THAT_UNNECESSARY_COMMA)
68-71: Harmonize jail criteria wording and punctuation
Use a hyphenated adjective (“6-month period”), add a comma before “and,” and hyphenate “post-mortem” for consistency:- * Not jailed more than once in the 6 months before application deadline - * If jailed more than once in the 6 months period before application deadline, - then we require a public forum post with detailed post mortem and we consider case by case + * Not jailed more than once in the 6-month period before the application deadline. + * If jailed more than once in the 6-month period before the application deadline, + then we require a public forum post with a detailed post-mortem, and we consider each on a case-by-case basis.🧰 Tools
🪛 LanguageTool
[misspelling] ~70-~70: This expression is normally spelled as one or with a hyphen.
Context: ...quire a public forum post with detailed post mortem and we consider case by case * Not asso...(EN_COMPOUNDS_POST_MORTEM)
[uncategorized] ~70-~70: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...lic forum post with detailed post mortem and we consider case by case * Not associat...(COMMA_COMPOUND_SENTENCE)
141-141: Clarify testnet naming and indentation
To maintain consistency with earlier mentions, replace “Mocha-4” with “Mocha testnet” and align the bullet indent with the surrounding list:- * If you don't run an active Mainnet Beta validator, please provide us with - validator address, bridge node ID on Mocha-4 + * If you don't run an active Mainnet Beta validator, please provide us with + the validator address and bridge node ID on the Mocha testnet.
150-150: Refine contributions bullet for precision
Change “for Celestia and its ecosystem” to “to Celestia and its ecosystem” for grammatical accuracy:- * Please list all contributions for Celestia and its ecosystem + * Please list all contributions to Celestia and its ecosystem
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
community/foundation-delegation-program.md(5 hunks)
🧰 Additional context used
🪛 LanguageTool
community/foundation-delegation-program.md
[typographical] ~67-~67: The conjunction “so that” does not have a comma in front.
Context: ...ics.md) (for new applicants - on testnet, so that we can evaluate performance) * Not jail...
(SO_THAT_UNNECESSARY_COMMA)
[misspelling] ~70-~70: This expression is normally spelled as one or with a hyphen.
Context: ...quire a public forum post with detailed post mortem and we consider case by case * Not asso...
(EN_COMPOUNDS_POST_MORTEM)
[uncategorized] ~70-~70: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...lic forum post with detailed post mortem and we consider case by case * Not associat...
(COMMA_COMPOUND_SENTENCE)
🔇 Additional comments (3)
community/foundation-delegation-program.md (3)
37-37: Cohort process overview is clear
The simplified description “Here is an overview of how the cohort process will work.” aligns well with the updated documentation.
45-50: Simplified cohort table is concise and informative
The new uniform table for Cohorts 5–7 improves clarity and maintains the necessary details.
63-64: 1-month minimum validator requirement is clearer
Highlighting the “at least 1 month” threshold improves eligibility transparency.
| Prospective validators are welcome to apply to the program starting. The application | ||
| is designed to assess a validator’s uptime performance | ||
| and contributions to the Celestia ecosystem. Of the 100 total slots in |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Fix incomplete sentence in program launch
Removing the specific start date has left the sentence “Prospective validators are welcome to apply to the program starting.” unfinished. Please clarify the intended launch timeline (e.g., “starting immediately” or specify the application window).
- Prospective validators are welcome to apply to the program starting.
+ Prospective validators are welcome to apply to the program starting immediately.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| Prospective validators are welcome to apply to the program starting. The application | |
| is designed to assess a validator’s uptime performance | |
| and contributions to the Celestia ecosystem. Of the 100 total slots in | |
| Prospective validators are welcome to apply to the program starting immediately. The application | |
| is designed to assess a validator’s uptime performance | |
| and contributions to the Celestia ecosystem. Of the 100 total slots in |
|
@jcstein pls check if all ok, not sure if we merge yet but at least if its all fine and we can push merge once we are there |
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (5)
community/foundation-delegation-program.md (5)
21-22: Suggest clarifying application start timeline
Removing the specific start date correctly abstracts the timeline but the sentence “Prospective validators are welcome to apply to the program” could still leave readers wondering when applications open. Consider adding a phrase such as “starting immediately” or “applications are now open” to make it explicit.
63-63: Merge continuation line into bullet for readability
The continuation “for at least 1 month before application deadline” should either be indented under the previous bullet or merged into the same line for consistency. For example:* Run an active Mainnet Beta validator **or** an active Mocha testnet validator **for at least 1 month before application deadline**
68-71: Refine eligibility jailing criteria for clarity and grammar
Combine the two bullets and apply hyphenation for “post-mortem” and “case-by-case”:-* Not jailed more than once in the 6 months before application deadline -* If jailed more than once in the 6 months period before application deadline, -then we require a public forum post with detailed post mortem and we consider -case by case +* Not jailed more than once in the 6 months before application deadline; if jailed more than once, a public forum post with a detailed post-mortem is required, and the application will be considered on a case-by-case basis.🧰 Tools
🪛 LanguageTool
[misspelling] ~70-~70: This expression is normally spelled as one or with a hyphen.
Context: ...quire a public forum post with detailed post mortem and we consider case by case * Not asso...(EN_COMPOUNDS_POST_MORTEM)
[uncategorized] ~70-~70: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...lic forum post with detailed post mortem and we consider case by case * Not associat...(COMMA_COMPOUND_SENTENCE)
141-141: Ensure consistent use of “Mocha” naming
Earlier you refer to “Mocha testnet,” but here “Mocha-4” is used. Consider standardizing on one term (e.g., “Mocha testnet” or “Mocha-4 testnet”) across the document.
150-150: Minor wording improvement
Change “list all contributions for Celestia and its ecosystem” to “list all contributions to Celestia and its ecosystem” for consistency with common phrasing.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
public/img/cohort-timeline.jpgis excluded by!**/*.jpg
📒 Files selected for processing (1)
community/foundation-delegation-program.md(5 hunks)
🧰 Additional context used
🪛 LanguageTool
community/foundation-delegation-program.md
[typographical] ~67-~67: The conjunction “so that” does not have a comma in front.
Context: ...ics.md) (for new applicants - on testnet, so that we can evaluate performance) * Not jail...
(SO_THAT_UNNECESSARY_COMMA)
[misspelling] ~70-~70: This expression is normally spelled as one or with a hyphen.
Context: ...quire a public forum post with detailed post mortem and we consider case by case * Not asso...
(EN_COMPOUNDS_POST_MORTEM)
[uncategorized] ~70-~70: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...lic forum post with detailed post mortem and we consider case by case * Not associat...
(COMMA_COMPOUND_SENTENCE)
🔇 Additional comments (3)
community/foundation-delegation-program.md (3)
34-37: LGTM: Cohort process description is clear
The reflowed line break and phrasing “Here is an overview of how the cohort process will work.” reads well. No issues found.
41-43: LGTM: Key points simplified and accurate
The updated bullet points concisely capture the program cadence, duration, and slot management.
45-50: LGTM: Cohort table simplification
The new table format clearly presents cohorts, sizes, durations, and renewal mapping.
3 participants
Update of the delegation program, do not merge yet!
Summary by CodeRabbit