I’ve shared a proposal to integrate zkFetch, a zero-knowledge proof-based data feed solution, into the Cardano ecosystem. zkFetch will deliver diverse, real-time off-chain data such as sports scores, financial updates, weather reports, social media metrics, and more. All data will be updated and published to XYZ at regular intervals relevant to each data stream, accompanied by zk-proofs to ensure cryptographic verifiability. By leveraging zkFetch, XYZ can enable secure, transparent, and trustless prediction markets powered by accurate, tamper-proof data.
Our service seamlessly integrates into DApps, offering over 100 diverse data feeds with regular updates, ensuring the integrity and growth of prediction markets in your ecosystem.
Would love to hear your thougths and feedback.
Thank you.
1 Like
Hi, @ROHIT_GOSWAMI thanks for your post. Would love to get some thoughts and better understanding about the proposed protocol.
In particular, I am curious how you would handle centralization and anti-collusion measures, which are the largest problem areas of any proxy-TLS, MPC-TLS, or zk-tls protocols. In the end, most solutions must address similar issues, despite their vastly different approaches to the problem.
- Who runs zkFetch’s ingestion and proof-generation infrastructure?
- Where are the feeds and who operates them?
- Reclaim might use residential proxies, is this the case? These can be blocked, and are a single point of failure(centralized)
- Does zkFetch attempt to bind or ensure integrity of the TLS transript? How might the protocol deter collusion if its the case?
- Does it rely on a single attestor for every proof?
Thanks,