Attested metrics feed for Canton assets (RFP 11, Public Verifiability) [Seeking Feedback + Champion]

Hi all,
We’re Eva and Valeriy from ZWING. We are preparing a submission to RFP 11 from the Foundation’s new 2026-2028 roadmap and would like ecosystem input before the PR goes up. As of September 2, 2026, the financial-markets-standards-verification category contains no submissions; ours would be the first.

The RFP states the problem plainly. An aggregate published by an issuer might not be trusted by the market, and transaction disclosure defeats confidentiality. In practice, key metrics of Canton assets (e.g. supply, issuance, volume) are today either invisible to outsiders or published without a way to check them. The demand side is already visible on this forum: the 2026 developer survey rated observability the weakest area, and third-party analytics providers have asked which read path they should even use (thread).

What we propose to build (open source):

A public feed of attested metrics for Canton assets, where each number carries a proof rather than a signature from us. For Canton Coin, supply and mint/burn are public through the super validator Scan APIs, so those metrics are attested by deterministic recomputation against a pinned snapshot and code version; anyone can re-run the computation and reproduce the result.
For private issuer assets, the issuer’s own participant proves the aggregate over its own active contract set: each supported query is compiled into a provable form, and what gets published is the query, the result, the proof, and a commitment anchored on the Global Synchronizer. Payloads never leave the issuer’s node, and no operator needs read access to issuer data.

The design leans on the fact that Canton already authenticates its state by hashes, so proofs cover queries against state the network already vouches for and never touch Daml execution. That keeps the proving system economical and auditable, and for us it is known engineering rather than research.

The interface is deliberately designed so that richer proofs over committed state can be added later without changing how consumers read the feed. It complements node-local indexing (Canton Index), the data standard work, and the proof-primitive proposals in the queue rather than replacing any of them. Issuers who prefer not to use the proving route can publish aggregates in a defined format, carried in the feed as declared values, visibly distinguished from proven ones.

One design limit we want feedback on: a party proves what it observes, so this yields “our issuance is X” rather than “total supply is X” unless observer coverage is complete.

About us: we build ZWING, verification infrastructure for digital assets, as a team of experienced financial infrastructure and blockchain builders (Dfinity, Cardano, PwC, State Street, Google, 1kx). Our verification methodology is published (arXiv), filed as a public comment with the OCC, and will be presented at a Swiss National Bank in October 2026. We have shipped evidence profiles for live assets including MiCA Article 76 assessment support. Valeriy built zkSafe on the same proving pattern this proposal uses.

Three asks:

1. Which metrics would be most useful to your project? Supply, issuance and volume are our starting set; we would rather build what the ecosystem needs.
2. Issuers: would you consider being an early pilot for the proving route? Nothing leaves your node; integration effort is grant-funded.
3. We are looking for a Development Fund champion in this lane; if this is your area, we would value a conversation.

PR link will follow in this thread once submitted.

Thanks, looking forward to your feedback and questions,
Eva & Valeriy