Tiered hot/cold storage for historical data

[Miracle656]

Background

Recent data is queried constantly; old data rarely. Tiering keeps hot data fast while moving cold data to cheaper storage, transparently to API consumers.

What to build

Move partitions older than a threshold to a cold store (object storage / cheaper table), and make queries spanning the boundary transparently union hot + cold results.

Key files

• src/storage/tiering.ts (new)
• src/api.ts

Acceptance criteria

• Cold data offloaded past the hot-window threshold
• Cross-boundary queries return correct merged results
• Tests covering boundary-spanning queries

Drips Wave · Complexity: Advanced · 200 points

---

Required: Before submitting, join the contributor Telegram so your work can be tracked and counted toward the Stellar Wave: https://t.me/+fxHXq8f1SwlkZDBk

[mikkyvans0-source]

@mikkyvans0-source has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

hello would love to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @mikkyvans0-source to this issue.

[drips-wave]

Congratulations, @mikkyvans0-source! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @mikkyvans0-source: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊