celestiaorg / celestiaorg/celestia-node

refactor(api): Remove `da` API Interface from Celestia Node

Open
#3,932 4 comments 1 reaction 0 assignees View on GitHub
area:api enhancement
Dominant language
Go
Stars
996
Forks
1.1k
Avg merge
1d 6h
Merged PRs (30d)
34

Description

### Implementation ideas

# Remove `da` Interface from Celestia Node

---

## What's the Issue?
Right now, our Celestia node includes a `da` (Data Availability) interface from the Rollkit client. It was originally added to fix some dependency issues, but it's not actually part of Celestia’s official API.

## Why Remove It?
- **Extra Work:** We're maintaining something that doesn't need to be here.
- **Confusion:** Users might think `da` is a core part of the Celestia API, which it isn’t.
- **Inconsistency:** Other nodes don’t have this interface, leading to mixed expectations.

## Proposed Solution:
1. **Move the `da` Interface:**
- **Option A:** Create a separate repository for the `da` interface.
- **Option B:** Integrate it directly into the Rollkit repository.
2. **Clean Up Celestia Node:**
- Remove all `da` related code and dependencies.
- Update the documentation to point users to the new location for `da`.

## Benefits:
- **Less Maintenance:** We can focus on the core features of the Celestia node.
- **Clearer API:** Users will have a better understanding of what’s officially supported.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.