Our Solution & Value Proposition
This documentation is designed for everyone working with SmartCache
SmartCache’s fundamental idea is simple but transformative: make caching a first-class developer experience by expressing intent in code and allowing a trusted off-chain service to handle the rest — from benchmarking to bid placement — only when it’s profitable to do so.
At the user level this looks like three straightforward flows:
Declare intent — a small annotation (e.g.,
#[auto_cache]) or project config (smartcache.toml) marks the contract or specific functions as cache-candidates. This is metadata only — it doesn’t change contract runtime semantics or increase attack surface.Let SmartCache decide — the backend watches deployments or opt-in events, vends short dry-run benchmarks (cached vs uncached), fetches CacheManager’s suggested bids and computes a conservative ROI estimate. If projected savings exceed the configured threshold, SmartCache will place the bid on behalf of the developer or DAO, using the wallet option chosen by the team (their own, multisig, or a managed pool).
Pay only for value — SmartCache charges a small outcome-based fee only when caching yields measurable gas savings. If caching is not beneficial, no bid is placed and no fee is charged.
Why this delivers real value:
Developer-native: caching becomes part of the development lifecycle rather than an afterthought to be managed by ops.
Scalable: automated discovery and ROI-based bidding scale across many contracts and chains without per-project scripts or bespoke dashboards.
Incentive-aligned: outcome-based fees ensure customers pay only when they get value, which reduces friction for trial and adoption.
Safer: the system includes conservative checks (gas estimation, balance verification, ROI margin) and idempotent bid placement to avoid accidental spend.
A working MVP already demonstrates the core idea: backend automation + dashboard that visualizes savings and bid history. The grant-backed plan focuses on finishing the developer tooling (Rust crate and CLI), hardening the bidding engine, and rolling out pilot onboarding for early Stylus projects.
Last updated