Repository navigation
fix(celestia): send auth token on block timestamp lookups - #55
Merged
Merged
Conversation
GetBlockTimestamp issued a raw HTTP request without the Authorization header, so it failed against celestia-nodes with auth enabled. Store the token on the client and send it as a Bearer token, and add a test covering the header. Clarify the --celestia-token flag in the README. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
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. Comment |
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This was referenced Oct 20, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
GetBlockTimestampmakes a raw HTTP request that bypassed the JSON-RPC client, so it never sent the configured--celestia-token. Against a celestia-node with auth enabled (the default), these lookups failed. The client now stores the token and setsAuthorization: Bearer <token>on that request when a token is configured.Adds a test covering the header with and without a token, and updates the README description of
--celestia-token.🤖 Generated with Claude Code