{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/af87a7d08c084c84b8ad60912a5f8d56\" frameborder=\"0\" width=\"1280\" height=\"960\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":960,"width":1280,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":960,"thumbnail_width":1280,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/af87a7d08c084c84b8ad60912a5f8d56-c989096642f232ea.gif","duration":420.075,"title":"CAPS Privacy Standard for Canton Oracles","description":"This Loom introduces CAPS, the Canton Access and Privacy Standard, and explains how it improves oracle data delivery for financial institutions. Marcin describes Redstone as a modular blockchain oracle with no major incidents in five years, protecting over $10 billion, serving 100+ customers, and providing 1,000+ feeds. He contrasts pull models that can be exploited due to lack of synchronization and push models that break privacy by making queries visible, and then outlines CAPS using a Root Capsule to shield query visibility while preserving canonical and auditable fixing for composability. He notes an early roadmap and milestones including locking the spec for community review, adding Fetcher and Relayers, and shipping an EVM subnet, with a requested $1.8 million grant (60% development) and an estimate of about 300 million Canton coin per year from traffic fees."}