Repository navigation
[P0] Celestia GetBlockTimestamp ignores --celestia-token (all verifications fail with auth enabled) #35
Description
Priority: P0 (bug) · Effort: S
Problem
internal/clients/celestia/client.go:229-284 (GetBlockTimestamp) sends header.GetByHeight with http.DefaultClient and no Authorization header. The --celestia-token value is passed to jsonrpc.NewClient but never stored on Client.
On a celestia-node with auth enabled (the default unless --rpc.skip-auth), this call returns 401. Every verifyAttempt then fails at verifier.go:304, every block exhausts its retries, and each one is reported as unsubmitted. The headline metric becomes false.
Proposed fix
- Add a
token stringfield tocelestia.Client. - In
GetBlockTimestamp, setreq.Header.Set("Authorization", "Bearer "+c.token)when the token is non-empty.
Pros / Cons
- ✅ ~3 lines; fixes verification against authenticated nodes.
⚠️ None.
Acceptance criteria
- Unit test with an
httptestserver asserting that theAuthorizationheader is present when a token is configured and absent otherwise.
Activity
auricom commentedon Oct 20, 2026
Related PR: #33 (ev-node v1.0.0 upgrade) rewrites
internal/clients/celestia/client.gobut does not fix this. CodeRabbit flagged the same bug on that PR. Suggested approach: add the 3-line token fix to #33 withFixes #35, so the Celestia client changes land together.auricom commentedon Oct 20, 2026
Fixed on
mainby #55:GetBlockTimestampnow sendsAuthorization: Bearer <token>, with a test ininternal/clients/celestia/client_test.go. #55 did not link this issue, so it is closed manually.