updates on staking contest #1001
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR updates documentation to reflect that the staking contest for selecting the genesis validator set has been completed. The changes convert future and present tense references to past tense throughout the documentation.
- Updated references to the staking contest from future/present to past tense
- Removed promotional notices about the live staking contest
- Added links to the staking portal for ongoing staking opportunities
Reviewed Changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| docs/node-ops/staking-contest/logistics.mdx | Updated tense to indicate the staking contest has concluded |
| docs/node-ops/requirements.mdx | Added link to staking contest documentation |
| docs/node-ops/overview.mdx | Removed promotional tip about live contest, updated contest description to past tense |
| docs/learning-lit/communicating-with-lit-nodes.mdx | Changed tense to reflect completed contest |
| docs/index.mdx | Replaced promotional tip with status update about completed contest and upcoming mainnet |
| docs/governance/overview.mdx | Removed promotional tip about live contest |
| docs/governance/litkey/staking.mdx | Removed contest bonus notice, updated references to past tense, changed launch date to ongoing availability |
| docs/governance/governance-architecture.mdx | Updated to reflect completed contest with link to staking portal |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| <Tip> | ||
| $LITKEY and the Staking Contest to Select the Genesis Node Operator Set for the Naga Mainnet are now LIVE. [Learn More](https://spark.litprotocol.com/litkey-is-live/). | ||
| The Naga Mainnet will be live soon. The Staking Contest is completed, the node operators have been selected and the network is being set up right now. Note that you can always stake your tokens to support the network and earn rewards via the [Staking Portal](https://staking.litprotocol.com/). |
There was a problem hiding this comment.
Extra space between sentences. Should use a single space: "The Naga Mainnet will be live soon. The Staking Contest"
Suggested change
| The Naga Mainnet will be live soon. The Staking Contest is completed, the node operators have been selected and the network is being set up right now. Note that you can always stake your tokens to support the network and earn rewards via the [Staking Portal](https://staking.litprotocol.com/). | |
| The Naga Mainnet will be live soon. The Staking Contest is completed, the node operators have been selected and the network is being set up right now. Note that you can always stake your tokens to support the network and earn rewards via the [Staking Portal](https://staking.litprotocol.com/). |
|
|
||
| <Tip> | ||
| $LITKEY and the Staking Contest to Select the Genesis Node Operator Set for the Naga Mainnet are now LIVE. [Learn More](https://spark.litprotocol.com/litkey-is-live/). | ||
| The Naga Mainnet will be live soon. The Staking Contest is completed, the node operators have been selected and the network is being set up right now. Note that you can always stake your tokens to support the network and earn rewards via the [Staking Portal](https://staking.litprotocol.com/). |
There was a problem hiding this comment.
Inconsistent tense usage. The first part uses "will be" (future tense) while the rest uses "is completed" (present perfect) and "is being set up" (present continuous). Consider revising to: "The Naga Mainnet will be live soon. The Staking Contest has been completed, the node operators have been selected, and the network is being set up right now."
Suggested change
| The Naga Mainnet will be live soon. The Staking Contest is completed, the node operators have been selected and the network is being set up right now. Note that you can always stake your tokens to support the network and earn rewards via the [Staking Portal](https://staking.litprotocol.com/). | |
| The Naga Mainnet will be live soon. The Staking Contest has been completed, the node operators have been selected, and the network is being set up right now. Note that you can always stake your tokens to support the network and earn rewards via the [Staking Portal](https://staking.litprotocol.com/). |
| In the future, as the network scales and new Realms are spun up, new node operators may be selected for participation in specific Realms even outside of regular onboarding windows. | ||
|
|
||
| The initial node operator set will be selected via a staking contest beginning after Lit’s token generation event (TGE). | ||
| The initial node operator set has been selected via a staking contest that ran after Lit’s token generation event (TGE). You can always stake your tokens to support the network and earn rewards via the [Staking Portal](https://staking.litprotocol.com/). |
There was a problem hiding this comment.
Extra space between sentences. Should use a single space: "The initial node operator set has been selected via a staking contest that ran after Lit's token generation event (TGE). You can always stake"
Suggested change
| The initial node operator set has been selected via a staking contest that ran after Lit’s token generation event (TGE). You can always stake your tokens to support the network and earn rewards via the [Staking Portal](https://staking.litprotocol.com/). | |
| The initial node operator set has been selected via a staking contest that ran after Lit’s token generation event (TGE). You can always stake your tokens to support the network and earn rewards via the [Staking Portal](https://staking.litprotocol.com/). |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: Chris Cassano <1285652+glitch003@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Just remove info about the stake weight contest and explain that it already happened