-
Notifications
You must be signed in to change notification settings - Fork 89
some updates around mainnet being live #1069
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: naga
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR updates the documentation to reflect that Lit Protocol's v1 Mainnet (Naga) is now live, removing outdated warnings and notices about the network being in development or coming soon.
Changes:
- Removed outdated tip about Naga being on testnet only and directing users to Datil mainnet beta
- Updated payment information to indicate that mainnet payments are now enabled using LITKEY tokens
- Removed warning stating that v1 Mainnet is not yet live
- Added FAQ entry about accessing old Datil network documentation and migration deadline
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| docs/sdk/introduction.mdx | Removed outdated tip box about Naga being on testnet and redirecting to Datil |
| docs/sdk/getting-started/payment-manager-setup.mdx | Updated mainnet payment status from "coming soon" to enabled with LITKEY tokens |
| docs/learning-lit/cryptoeconomic-security.mdx | Removed warning box stating v1 Mainnet is not yet live |
| docs/faqs/index.mdx | Added new FAQ entry about Datil network docs location and shutdown date |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| This default keeps compatibility with `Lit.Actions.runOnce`. Only the node that runs the `runOnce` block returns a value, so selecting the least-common response ensures that single result is preserved. When `runOnce` is not used, all nodes should emit the same payload, making least- vs most-common equivalent—the former stayed in place because it was the quickest path to enabling the new `runOnce` flow in v8. | ||
|
|
||
|
|
Copilot
AI
Jan 29, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are two consecutive blank lines here (lines 13 and 14). This is inconsistent with the rest of the codebase which typically uses a single blank line to separate sections. Consider removing one of these blank lines for consistency.
|
|
||
| ## Where are the old Datil network docs? | ||
|
|
||
| You can find the old Datil network docs here: https://datil.developer.litprotocol.com. Note that Datil will be shutdown on Feb 25th so please migrate to Naga before then. No newline at end of file |
Copilot
AI
Jan 29, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a double space after "here:" which should be a single space. The sentence should read "You can find the old Datil network docs here: https://datil.developer.litprotocol.com."
| You can find the old Datil network docs here: https://datil.developer.litprotocol.com. Note that Datil will be shutdown on Feb 25th so please migrate to Naga before then. | |
| You can find the old Datil network docs here: https://datil.developer.litprotocol.com. Note that Datil will be shutdown on Feb 25th so please migrate to Naga before then. |
noticed that there's a bunch of places in the docs that talk about naga being live soon. i wanted to fix that.