Problem & Motivation

This documentation is designed for everyone working with SmartCache

Caching on Arbitrum is a powerful way to reduce gas and dramatically speed up hot-path contract calls, but today the workflow around CacheManager is still largely manual. Developers who want to benefit must stitch together many moving parts: instrument contracts to measure gas, collect live bid suggestions, run cost/benefit calculations, submit and monitor bid transactions, and maintain infrastructure that tracks historical savings. For single contracts or small teams that’s tedious; for teams managing dozens or hundreds of contracts across stages and chains it’s a blocker.

The pain is not only operational. Manual workflows are error-prone: a missed renewal, a miscalculated ROI, or a failed transaction can mean wasted escrow funds, missed savings, or unexpectedly expensive operations. Teams often build fragile scripts or run one-off dashboards to keep up, which leads to duplicated effort across teams and poor repeatability. The ecosystem suffers too — cache slots that would have been beneficial may go unused, reducing the overall efficiency gains CacheManager can offer.

There’s also a user-experience problem. Newer Stylus developers — or teams without heavy DevOps resources — are discouraged by the overhead. They already need to master Stylus, testing, deploy pipelines and runtime monitoring; adding manual cache management makes the barrier to adoption higher. Finally, without a standardized automation layer, different teams manage cache slots inconsistently, which complicates audits and makes ROI hard to compare across projects.

SmartCache is built to solve these concrete problems: remove manual bookkeeping, provide reliable automation with predictable outcomes, and lower the barrier to entry so more Stylus contracts actually use caching in a safe, measurable way.