Implement Fiber DA spec compatibility (FiberFetcher)

Open
#1 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
Mostly clear
Activity status
Stale
Tech stack
go
Domain
backend, networking

Research direction

Start with the DataFetcher interface in pkg/fetch/fetcher.go, the planned implementation in pkg/fetch/fiber.go, and test_plan.md Phase 4. Read the upstream fibre-da-spec and determine the required data types and wire format before implementing the five methods and fiber data_source configuration. Done means the implementation conforms to the spec and integration tests run against a local Fiber node or mock.

Written by the indexing model from the issue text.

Description

Summary

Implement FiberFetcher as a DataFetcher backend that conforms to the Fiber DA spec. This enables apex to fetch namespace data directly from the Fiber network instead of going through celestia-node, reducing latency and removing the celestia-node dependency for production deployments.

Context

The architecture already defines a pluggable DataFetcher interface (pkg/fetch/fetcher.go). The FiberFetcher implementation (pkg/fetch/fiber.go) is planned for Phase 4. This issue tracks aligning that implementation with the upstream Fiber DA spec as it stabilizes.

Requirements

  • Implement FiberFetcher satisfying the DataFetcher interface:
    • GetHeader(ctx, height)
    • GetBlobs(ctx, height, namespace)
    • GetNetworkHead(ctx)
    • SubscribeHeaders(ctx)
    • Close()
  • Conform to the data types and wire format defined in fibre-da-spec
  • Add config support for type = "fiber" in [data_source]
  • Integration tests against a local Fiber node (or mock)

Blocked on

  • Fiber DA spec reaching a stable/tagged version
  • Fiber network availability for testing

References

ref https://github.com/celestiaorg/celestia-node/issues/4777

Dominant language
Go
Stars
4
Forks
0
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

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

More from evstack/apex

All issues in evstack/apex

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.