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

[tac0turtle]

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 Implement Celestia node JSON-RPC compatibility layer #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

• Implement Celestia node JSON-RPC compatibility layer #2 — JSON-RPC compatibility layer (must support v0 + v1)
• Subscription improvements: backpressure, contiguity, multi-namespace #14 — Subscription improvements (subscribe API may change in v1)