Track celestia-node API v1 migration (blob_v1, share_v1)

Open

#21 opened on Feb 19, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 25/100

Issue type: Feature
Clarity: Needs clarification
Activity status: Stale
Tech stack: go
Domain: api, backend-api-design

Research direction

Start by reading apex #2 and the existing GetProof stub, then review celestia-node issues #4308 and #4306 for the v1 API status. Track the blob_v1 and share_v1 signature and proof changes, and use the listed action items as the completion checklist: v0/v1 compatibility, updated proof handling, Included deprecation planning, and app_version support.

Written by the indexing model from the issue text.

Description

Summary

celestia-node is introducing versioned API modules (blob_v1, share_v1) with breaking changes to proof structures and method signatures. Apex must track these changes to maintain compatibility.

Upstream issues

celestiaorg/celestia-node#4308 — EPIC: API v1 release with dataroot proof structure
celestiaorg/celestia-node#4306 — Create share_v1, blob_v1 API modules
celestiaorg/celestia-node#4307 — Deprecate share and blob API v0
celestiaorg/celestia-node#3919 — Deprecate blob.Included() method

Breaking changes to track

blob_v1

Get(height, namespace, commitment) adds a proofs_only option — changes request signature
GetProof is removed as a standalone method (folded into Get with proofs_only=true)
Included is deprecated — replaced by proof validation methods
Proof structure changes from namespace row proofs to "dataroot" proofs (more efficient)

share_v1

GetRange, GetShare, GetEDS, GetSharesByNamespace — new method signatures
Index harmonization: EDS vs ODS indexes unified to ODS-only

Deprecation timeline

v0 gets deprecation warnings in response headers after v1 ships
Migration guide published
v0 eventually removed

Action items

Monitor upstream progress on #4308
When blob_v1 ships, update apex #2 (JSON-RPC layer) to support both v0 and v1
Update GetProof stub to match new proof-via-Get pattern
Plan deprecation of Included from apex API
Ensure apex response types include app_version for downstream consumers (celestiaorg/celestia-node#3977)

Related apex issues

#2 — JSON-RPC compatibility layer (must support v0 + v1)
#14 — Subscription improvements (subscribe API may change in v1)

Dominant language: Go
Stars: 4
Forks: 0
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

Usage controller writes the in-use label on every reconcile even though it is already set Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

crossplane/crossplane#7859 · Opened Sep 22, 2026
Response files don't work well with Go 1.27 Open

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

bazel-contrib/rules_go#4721 · 2 comments · Opened Sep 22, 2026
`gh pr comment --attach` refuses `ghu_` tokens that the upload endpoint accepts Open

needs-triage

Difficulty 1/5 Under an hour Newbie friendliness 92/100

cli/cli#14495 · 1 comment · Opened Sep 22, 2026
[BUG] Package template mutation when constructing Apps during update retries Open

bug carvel-triage

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

carvel-dev/kapp-controller#1861 · Opened Sep 22, 2026
opentelemetry-operator ClusterRole lacks gateway.networking.k8s.io/httproutes — operator wedges on clusters with Gateway API CRDs, garden logging never comes up Open

area/logging kind/bug

Difficulty 2/5 1-3 hours Newbie friendliness 86/100

gardener/gardener#15776 · Opened Sep 22, 2026

More Go issues