Develop an Origin Private File System (OPFS) caching layer for historical fractional token charts

[Damola-Sodiq]

Description

Utilize the browser's native OPFS to store megabytes of historical candlestick data locally, drastically reducing payload sizes on return visits to the dashboard.

Architecture & Context

Fetching 5 years of fractional token OHLCV (Open, High, Low, Close, Volume) data continuously wastes user bandwidth and slows down charting. OPFS provides synchronous, near-native file system I/O capabilities directly within a Web Worker.

Technical Requirements

• Access the OPFS API using a dedicated Next.js Web Worker.
• Implement a binary serialization format to write historical chart chunks to the local disk.
• Sync only the missing delta (new blocks) from the backend API on subsequent loads.

Acceptance Criteria

• Returning users load historical charts with near-zero network payload.
• OPFS read/write speeds massively outperform standard IndexedDB implementations.
• Storage quotas are actively monitored and older assets are LRU evicted.

[Brainoncrack]

Hi maintainer, i will love to work on this

[grantfox-oss]

🦊 GrantFox — @Brainoncrack has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #473)
2. Your PR will be reviewed by the Sahara-Pay maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@Brainoncrack's PR #501 was approved and merged by @Damola-Sodiq.

🏆 @Brainoncrack: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (261 total points). Track your full progress on GrantFox.

👏 Great work, @Brainoncrack! Keep contributing to Sahara-Pay.