SV Lock insights dev proposal v3

[pixelplex]

Development Fund Proposal Submission

Proposal file:
/proposals/SV_Lock_Insights_Development_Fund_Proposal.md

---

Summary

This proposal covers the continued development of SV Insights, an operational dashboard for Canton Super Validators. It includes the functionality already implemented, plus new capabilities for notifications, unlock flow visibility, and ongoing maintenance. The goal is to improve day-to-day validator operations by giving Super Validators clearer visibility into locking-related activity, reducing manual monitoring, and supporting the dashboard’s reliability as it evolves.

---

Checklist

• Proposal file added under /proposals/
• Milestones and funding amounts defined
• Acceptance criteria included
• Alignment with Canton priorities described

---

Notes for Reviewers

Already working PoC
https://ccview.io/sv-locking/

[waynecollier-da]

I feel this would be a useful contribution to the ecosystem, particularly during Phase 1 of CIP-0105. The ecosystem needs a way to track SV locking compliance, and the Foundation needs reliable sources it can use to assess locking status. This tool would remain valuable after automation kicks in with Phase 2.

[shaul-da]

I see this a useful data, but for an ecosystem grant there are two main areas I'd want clarity on:

1. In what ways does this meaningfully add value above and beyond existing tools such as https://lighthouse.xyz/sv-locking
2. Are there other projects in the community who expect to reuse the code once it's open sourced? Having them come forward here publicly would help assess the ecosystem impact. In other words, beyond the service that ccview.io will be providing, will the code be reused, in practice, by others?

[pixelplex]

@shaul-da Thanks for the questions!

1. CCView has repeatedly proven it delivers the most accurate data across the ecosystem — this has been verified by different committee members when compared against other data sources. As a concrete example, Dr. Amanda currently relies on us to cross-validate the Python script each time anyone requests a milestone release for SV rewards earned. Our featured app ratio performance data is also the only place where this is available with correct interpretation. Beyond what’s there today, we’re planning to add a notification engine so SVs get alerted when they’re approaching or falling below tier thresholds, plus the ability to download raw data for their own accounting. Having multiple independent data sources for something this critical is healthy for the network.

2. All underlying data will be available in raw format via a public API at no cost — so this is fundamentally a public good. The complete frontend will also be open-sourced under Apache 2.0, so any other explorer or analytics provider can integrate both the API data and the UI components into their own product. Between the free API and the open frontend, the barrier for reuse is as low as it gets.