Application: Stylus Manager - Caching, Activating and Tracking Stylus Contracts
Team: Augusto Collerone, Lautaro Sole, Ignacio Quesada
Milestone: Frontend Development
Funding Amount Unlocked: 9,500 USD
Date Submitted: 30/07/2026
Summary of the Deliverables: Frontend implementation of the Activation module, integrated contract-centrically into the rebranded Stylus Manager. Activation status is now surfaced across the contract tables with real backend data, a full Activation tab inside the contract detail view supports manual on-chain activation, interactive auto-activation configuration and activation history, the Add Contract flow handles expired Stylus WASM, four activation alert types are exposed in the per-contract alerts panel, and the upgraded app is deployed to a public staging URL.
Product surface renamed from "Cache Manager" to "Stylus Manager": app metadata (title + description), header wordmark, and logo alt text updated to reflect the broader product positioning (caching + activation + bidding). Feature-specific references to the CacheManager contract are intentionally left untouched.
Activation status column added to both My Contracts and Explore Contracts tables via the ActivationBadge component, wired to real backend data (persisted activationStatus + programTimeLeft). As a follow-up cleanup, the backend now returns programTimeLeft and programTimeLeftReason on both list and detail endpoints, so the frontend dropped its on-chain multicall fallback — one source of truth, fewer RPC calls per page load.
The contract detail view (the same place where caching is configured) now has a fully functional Activation tab:
ActivationBadge, humanized last-activation timestamp, and an activation history table (Date | Event | Spent (ETH) | Tx | Reason) populated from the backend's per-contract activationHistory.