← CIP-0079 · citation graph
CITATIONS / CIP-0079
SV Readiness — Demonstrate Third-Party Price Feed Integration for CC Listing · status: Approved
Every place across CCPEDIA's corpus that references CIP-0079 — sibling CIPs, forum threads, the cip-* / grants-* mailing lists, GitHub issues + PRs across all indexed Canton repos, third-party blog coverage, and YouTube transcripts. Each section samples the most recent N; counts above the sample are the totals.
Mailing-list messages · 29 · across 3 threads
Messages on cip-vote, cip-discuss, grants-discuss, and other validator-announce lists. Items with cip_id_match badge come from CCPEDIA-parsed mailing_messages.cip_id — only-here join.
… Today, bringing off-chain data on-chain requires bespoke application-level plumbing: - Price feeds (CIP-0079): Super Validators ingest Kaiko prices and republish them via dedicated Daml contracts and automati …
Hello Canton Network Super-Validators, Kaiko will provide a CC/USD conversion rate to help you meet CIP-0079. We will be live on DevNet on October 10th, then deploy to TestNet and MainNet as soon as possible. …
SBI votes in favor, and confirms to, 'subscribe to a feed that delivers CC/USD and demonstrate the ability to update every 10 minutes' toggle quoted message Show quoted text
Sorry for the quick follow up message. I meant to add: My comments seemed to be what the group discussed prior to the vote so I think my interpretation is correct, but I wanted to clarify given the wo
Cumberland DRW votes in favor but I’d like to condition the vote on clarification of something. The current proposal seems a bit ambiguous. The first requirement, subscribe to a feed that delivers CC/
… sync.global Date: Thursday, September 18, 2025 at 6:30 AM To: cip-vote@... Subject: Re: [cip-votes] CIP-0079: SV Readiness — Demonstrate Third-Party Price Feed Integration for CC Listing MPCH votes in favor. …
… sts.sync.global Date: Thursday, September 18, 2025 at 8:31 AM To: cip-vote@... Subject: [cip-votes] CIP-0079: SV Readiness — Demonstrate Third-Party Price Feed Integration for CC Listing Hello Super Validator …
Five North in favor toggle quoted message Show quoted text
Proof Grouo votes yes for this- thank you Chris Matturri chris@... ProofGroup.xyz toggle quoted message Show quoted text
Thank you Eric. 7RIDGE/C7 remain interested in sponsoring or endorsing this CIP toggle quoted message Show quoted text
Hello Super Validator Node Owners, Please find ready for vote: CIP-0079: SV Readiness — Demonstrate Third-Party Price Feed Integration for CC Listing Digital Asset - SV Sp …
Made 2 changes in the Requirements Table R1 Ingest a reference price feed Subscribe to at least one feed delivering CC/USD to the SV Must be live on MainNet by Oct 15, 2025 R2 Publish on-chain Update
Many thanks! MPCH will support with these changes Get Outlook for iOS toggle quoted message Show quoted text
I have no interest in making the requirements more onerous at this point given the tight timeline Status quo is a manual process, rolling onto feeds is step 1, we can improve it over time - the median
Thanks Yiannis, for laying this out clearly. We agree with the framing that each SV needs to demonstrate the ability to consume a feed by October 15, and that this does not imply a single mandated pro
Hi all. We discussed offline with Eric and Kinga about this but I just want to make sure that this is clear to all, and I didn't miss something: - The consumption of the price feed, doesn't automatica
7RIDGE/C7 is willing to sponsor or endorse! Veronica V E R O N I C A A U G U S T S S O N / P A R T N E R 7RIDGE IS A PRIVATE MARKETS ASSET MANAGER INVESTED IN TRANSFORMATIVE TECHNOLOGY FOR FINA
Liberty City Ventures would also like clarity as to whether accepting a feed would entail requiring the data received via that feed to automatically set the on-chain conversion price. toggle quoted me
MPCH would like to request clearer guidance on what SV operators must demonstrate to show compliance with the requirement to accept data feeds. We also strongly believe that at least two alternative s
Are any of the SV Node owners willing to endorse this CIP in its current form?
Agree completely that SVs should be free to choose their own sources and act independently. The concern is not about mandating which feed must be adopted, but rather about making sure there’s real opt
Fully agree that Kaiko’s option isn’t limiting in theory. The practical issue is that, with the October 15 deadline, most SVs will inevitably start there. Since the CIP explicitly provides a solution
sorry to be a broken record - there are n pathways an SV can consume a price feed - the very convenient way Kaiko will provide one is is not in any way limiting to the other ways in which price can be
I don’t believe that we are restricting the use of other providers. Our comment was to provide at the minimum two available sources from the getgo as an option. We strongly believe that enabling the f
I feel like this discussion continues to diverge into debating a particular potential source instead of the main issue here - that each SV adopt some source I don't think it's a good idea to mandate w
GitHub items · 2
Issues, PRs, and dev-fund proposals across all indexed Canton repositories that mention CIP-0079.
… uting the call, preserving determinism. This replaces the per-source oracle infrastructure pattern (CIP-0079 price feeds, CIP-0043/CIP-0044 KYC attestations) with a single general-purpose mechanism that any c …
For AI agents
Same citation graph through programmatic surfaces:
get_cip_citations— MCP tool. Input:{cip_id}. Output: counts plus sample items per source. Use when an agent needs "everything that references CIP-X across CCPEDIA's corpus" in one round-trip.GET /api/v1/cips/0079/citations— JSON shape mirroring this page.- The legacy
/api/v1/cips/0079/mentionsstays for backward compat — it returns topic / thread counts; this new endpoint returns per-post / per-message granularity plus GitHub and YouTube coverage.
