Summary
Add an S3-compatible API layer on top of Apex so Celestia blobs can be accessed as objects in buckets.
This would allow developers to interact with Celestia-backed storage using standard S3 tooling such as:
- AWS CLI
- S3 SDKs
- MinIO clients
Example usage:
aws s3 cp file.txt s3://celestia-bucket/file.txt
Under the hood Apex would:
- Chunk the object into blobs
- Submit blob transactions to Celestia
- Store object metadata in SQLite
- Reconstruct objects from blobs when requested
Motivation
Apex already provides:
- JSON RPC interface
- gRPC interface
- SQLite cache/index layer
Adding an S3-compatible API would make Apex usable with a huge ecosystem of existing tooling and SDKs.
Architecture
S3 API
↓
SQLite metadata + cache
↓
Apex blob client
↓
Celestia node
Celestia remains the canonical storage layer while SQLite acts as a local index and cache.
Summary
Add an S3-compatible API layer on top of Apex so Celestia blobs can be accessed as objects in buckets.
This would allow developers to interact with Celestia-backed storage using standard S3 tooling such as:
Example usage:
Under the hood Apex would:
Motivation
Apex already provides:
Adding an S3-compatible API would make Apex usable with a huge ecosystem of existing tooling and SDKs.
Architecture
Celestia remains the canonical storage layer while SQLite acts as a local index and cache.