Meta: Blob Submission Pipeline
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- go
- Domain
- backend, distributed-systems
Research direction
Start with sub-issue #4, which determines whether to use a custom transaction submission client or celestia-node. Then follow the dependency order through #9, #5, #8, #18, and #19. The work is done when the complete write path can construct, sign, nonce, broadcast, and confirm blob transactions for the higher-level storage APIs.
Written by the indexing model from the issue text.
Description
Summary
Tracking issue for the full blob submission (write path) pipeline. This is a prerequisite for all higher-level storage APIs (#43).
Apex is currently read-only. To support S3, Git, and npm storage APIs, we need a complete write path: construct transactions, sign them, manage nonces, broadcast, and confirm.
Sub-issues (dependency order)
Core submission client
- #4 — Evaluate custom tx submission client vs celestia-node client (root decision)
Signing & identity
- #9 — Keyring and signing for transaction submission
- #5 — Multi-account support for transaction submission
Reliability
- #8 — Nonce management for transaction submission
- #18 — Rate limiting and circuit breaker for transaction submission
- #19 — Transaction confirmation and lifecycle tracking
Dependency graph
#4 (submission client decision)
├── #9 (keyring/signing)
│ └── #5 (multi-account)
├── #8 (nonce management)
│ └── #5 (multi-account)
├── #18 (rate limiting / circuit breaker)
└── #19 (tx confirmation / lifecycle)
Relationship to storage APIs
The storage platform features (#43) all depend on this pipeline:
S3 API (#40) ──┐
Git remote (#41) ──┼── Blob Submission Pipeline (this issue)
NPM registry (#42) ──┘ │
┌─────┴─────┐
#4 #8 #9 #5 #18 #19
Without a working write path, the storage APIs are read-only caches at best.
- 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 25/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
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug group: validation priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
codecheckers/chekhov#51 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100