Meta: Apex as a Celestia-backed Developer Storage Platform
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, sqlite
- Domain
- backend, databases, distributed-systems
Research direction
Start by reviewing prerequisite issue #44 and the related API issues #40, #41, and #42, then trace the architecture from protocol adapters through blob chunking and the SQLite index/cache. Done means the shared content-addressed blob abstraction and submission pipeline exist well enough to support the planned S3, Git, and npm adapters.
Written by the indexing model from the issue text.
Description
Summary
Tracking issue for exposing Celestia blob storage through familiar developer interfaces.
The core idea: Apex already indexes and caches Celestia blobs in SQLite. By adding a write path and a generic blob abstraction, we can layer multiple storage APIs on top.
Prerequisites
- #44 — Blob Submission Pipeline (write path — keyring, nonce, tx lifecycle)
Storage APIs
- #40 — S3-Compatible Object Storage API
- #41 — Git Remote Storage via Apex
- #42 — Celestia-backed NPM Registry
Architecture
Protocol-specific API (S3 / Git / npm)
↓
Object ↔ Blob chunking + metadata
↓
SQLite index/cache
↓
Blob Submission Pipeline (#44)
↓
Celestia DA
Dependency graph
#43 (this — storage platform)
├── #44 (blob submission pipeline)
│ ├── #4 (tx client decision)
│ ├── #9 (keyring/signing)
│ ├── #5 (multi-account)
│ ├── #8 (nonce management)
│ ├── #18 (rate limiting)
│ └── #19 (tx confirmation)
├── #40 (S3 API)
├── #41 (Git remote)
└── #42 (NPM registry)
The key enabler is a common content-addressed blob storage abstraction that handles chunking, reassembly, and metadata tracking. Once that and the submission pipeline exist, each protocol adapter becomes a relatively thin translation layer.
- Dominant language
- Go
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor 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.
More from evstack/apex
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
Similar issues
-
bug carvel-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
carvel-dev/kapp-controller#1861 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100