feat: add more cel-key docs

[hexmarkd]

Still refining this implementation, but would appreciate any early feedback on the approach or potential improvements

Summary by CodeRabbit

• Documentation
  • Added detailed instructions for managing the key used by the node's account address, including backup and recovery methods, key verification steps, and guidance on specifying a key at startup.
  • Included examples and directions to external resources for further guidance.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes introduce new documentation sections focused on managing the key used by the celestia state account-address command. The updates provide detailed instructions on identifying, backing up, recovering, and specifying the key for a Celestia node. These additions clarify the relationship between the node and its key, outline backup and recovery procedures, and explain how to use a specific key with the node, including relevant command examples and references to external guides.

Changes

File(s)	Change Summary
how-to-guides/quick-start.md	Added a subsection under key management explaining how to manage the key used by celestia state account-address, with a link to a detailed external guide.
tutorials/celestia-node-key.md	Introduced a comprehensive section detailing key management for celestia state account-address, including backup, recovery, verification, and specifying a key, with examples.

Possibly related issues

• Better step-by-step instructions for using cel-key #1867: Addresses the need for detailed documentation on managing the key used by celestia state account-address, including backup, recovery, and specifying keys.

Poem

In burrows deep where secrets dwell,
A key is kept, so guard it well.
With guides anew, your path is clear,
To backup, restore, and persevere.
Hop along, Celestia friend—
Your node’s safe key will never end!
🗝️🐇

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cc90f2e and 3526990.

📒 Files selected for processing (2)

• how-to-guides/quick-start.md (1 hunks)
• tutorials/celestia-node-key.md (1 hunks)

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[jcstein]

Does this export the mnemonic or a key file? I think we can get this merged after clearing this up @hexmarkd

[jcstein]

approving because I can't edit your branch