Closed gupadhyaya closed 8 months ago
The recent changes involve integrating an authentication mechanism in the init-full-node.sh
script and the corresponding tutorial documentation for setting up a full node. This mechanism fetches an authentication token from a Celestia node, which is then utilized in the gmd start
command, marking a shift from using a static rollkit.da_auth_token
to a dynamic retrieval process. This update ensures enhanced security and customization, particularly when operating separate nodes for the sequencer and full node.
File Path | Change Summary |
---|---|
scripts/gm/init-full-node.sh |
Modified to fetch an AUTH_TOKEN from a Celestia node for use in gmd start , replacing a static token. |
tutorials/.../full-and-sequencer-node.md |
Updated to include instructions on obtaining AUTH_TOKEN from celestia-node for full nodes, highlighting the need for distinct tokens for different node types. |
🐇✨
In the world of code, where secrets are bold,
A rabbit hopped in, with a story untold.
"Fetch me a token," it said with a grin,
"For nodes to start talking, let the magic begin."
With a flick and a hop, the task was clear,
Secure the connections, far and near.
🌟🌿
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
PR Preview Action v1.4.7 :---: Preview removed because the pull request was closed. 2024-03-22 17:41 UTC
Overview
Checklist
Summary by CodeRabbit
AUTH_TOKEN
from the Celestia node, highlighting the requirement for separate tokens for different node types.