[RFC](Non-Constitutional) Proposal: Integrating zkTLS-Powered Oracle Solution (zkFetch) for Arbitrum

Proposals
1

Note: This is an initial draft of the proposal. The content will be refined and updated based on community feedback and discussions. Your input is crucial in shaping the final version.

Abstract

This AIP seeks funding for the development & integration of zkFetch, a zero-knowledge proof-based data fetching service, into the Arbitrum ecosystem. zkFetch will provide cryptographically verifiable, privacy-preserving oracle solution for any off-chain data, enhancing Arbitrum Ecosystems DApp’s security and enabling innovative use cases like Prediction Markets, RWA and AI requiring trust and transparency.

Motivation

The integration of zkFetch into Arbitrum addresses some of the important challenges in the current web3 landscape while opening up new possibilities for the ecosystem:

Enhancing Oracle Security and Privacy:

  • In web3, the Current oracle systems lack robust cryptographic verifiability and privacy preservation. This exposes DApps to manipulation risks and limits the integration of sensitive real-world data.
  • zkFetch provides a zero-knowledge proof-based solution, offering unparalleled security and privacy.

Overcoming Existing Trade-offs:

  • Traditional oracle solutions often compromise between security, privacy, and flexibility. These trade-offs restrict the types of off-chain data that can be reliably integrated.
  • zkFetch’s unique approach allows for secure, private, and flexible data integration without compromises.

Attracting Developers and Projects:

  • By offering a zkTLS-powered oracle solution, Arbitrum can attract more developers and projects to its ecosystem. The enhanced security and privacy features will appeal to projects dealing with sensitive data or complex financial applications. This influx of talent and projects can significantly boost Arbitrum’s ecosystem growth and diversity.

Enabling New Use Cases:

  • zkFetch’s ability to securely integrate any off-chain data opens up possibilities for innovative applications.
  • Potential new use cases include:
    • Dapps with cryptographically verified, temper-proofs price feeds.
    • Verifiable real-world asset (RWA) tokenization
    • Prediction Markets on any off-chain data integrations

Positioning Arbitrum as a Leader in L2 Innovation:

  • Implementing zkFetch showcases Arbitrum’s commitment to adopting new technology like zkTLS. Early adoption of zkTLS-powered oracle technology can give Arbitrum a competitive edge in the L2 space.

Facilitating Institutional Adoption:

  • The enhanced privacy and security features of zkFetch can make Arbitrum more appealing to institutional players. This can potentially lead to increased liquidity and more sophisticated financial products on the platform.

Rationale

The integration of zkFetch aligns perfectly with Arbitrum’s mission to provide a secure, scalable, and developer-friendly Layer 2 solution. Here’s how zkFetch’s unique features support Arbitrum’s core values and objectives:

Enhanced Security without Compromising Performance:

  • zkFetch’s zkTLS infrastructure provides cryptographic guarantees for data integrity.
  • Zero-knowledge proofs are generated in less than 4 seconds, even on low-compute devices, ensuring that Arbitrum’s high-performance standards are maintained.
  • This rapid proof generation allows for real-time, secure data updates without exposing API keys critical for Dapps on Arbitrum.

Scalability and Flexibility:

  • zkFetch is compatible with any HTTPS endpoint, allowing Arbitrum to easily scale its oracle capabilities to any data source.
  • The ability to generate data proofs for any reputed and trusted data providers ensures that Arbitrum can quickly adapt to new data needs.
  • This flexibility supports Arbitrum’s goal of being a versatile platform for a wide range of DApps.

Privacy-Preserving Operations:

  • zkFetch enables the use of private API keys and sensitive endpoints without on-chain exposure.
  • This aligns with Arbitrum’s commitment to user privacy and opens up possibilities for handling confidential data in DeFi operations.

Developer-Friendly Integration:

  • zkFetch’s can seamlessly embeds in both Web2 and Web3 applications, lowering the barrier for developers to build on Arbitrum.
  • No plugins or additional apps are required on the user-end, simplifying the development and user experience.

Proven Track Record:

  • zkFetch leverages zkTLS Infrastructure by Reclaim Protocol, that has been successfully deployed on multiple chains (30+) including Arbitrum, Sui, Polygon, Solana, Optimism, Base and many others, also integrated with Ethereum Attestation Services.
  • Within a span of one year, over 20 projects in production have already integrated this zkTLS infrastructure, building innovative use cases such as DID, Proof of Personhood, RWA, prediction markets, and more.

Future-Proofing the Oracle System:

  • The modular design of zkFetch ensures adaptability to Arbitrum’s evolving architecture.
  • The underlying zero-knowledge proof system can be updated to more efficient protocols as technology advances, without requiring major changes to the Arbitrum infrastructure.

Expanding Use Cases:

  • zkFetch’s capability to handle various data types beyond crypto price feeds (e.g., Sport Data, News, Global Bonds, Commodities Prices) opens up new possibilities for innovative DApps on Arbitrum.
  • This aligns with Arbitrum’s goal of being a comprehensive platform for diverse blockchain applications.

By integrating zkFetch, Arbitrum not only enhances its oracle capabilities but also solidifies its status as a leading, secure, and developer-friendly Layer 2 solution. The synergy between zkFetch’s features and Arbitrum’s objectives guarantees that this integration will create substantial value for the entire ecosystem.

Key Terms

  • zkFetch: A library that extends standard HTTP fetch operations with zero-knowledge proof components.
  • zkTLS: An infrastructure that secures communication during the handshake mechanism in Transport Layer Security (TLS), provided by Reclaim Protocol.
  • Zero-Knowledge Proofs (ZKPs): Cryptographic methods allowing one party to prove to another that a statement is true without revealing any information beyond the validity of the statement itself.

Specifications

zkFetch is a library that extends the functionality of a standard HTTP fetch operation by adding a ZKP component. It is built on top of the Reclaim Protocol, which provides the underlying infrastructure(Open-source) for generating and verifying zero-knowledge proofs. It can fetch data from any remote resources and generate a cryptographic proof of the fetch operation and its result, without revealing sensitive information like API keys or private headers.

Key Components -

Secure Data Retrieval:

  • Initiates HTTPS requests to any specified endpoint
  • Employs custom TLS implementation for secure communication
  • Supports various HTTP methods and custom headers

Decentralized Proxy Witnessing:

  • Routes requests through HTTP Proxies for additional security
  • Mitigates man-in-the-middle attack risks

Zero-Knowledge Proof Generation:

  • Utilizes Reclaim Protocol to create proofs of data integrity, source authenticity, and parameter correctness

On-chain Verification:

  • Enables efficient verification of proofs directly on the Arbitrum.

image
image777×630 16.8 KB

Our approach with zkFetch is driven by several key factors:

  1. Zero-Knowledge Proofs (ZKPs): We chose to leverage ZKPs because they offer a unique combination of data integrity and privacy. This allows us to verify the authenticity of data without revealing sensitive information, addressing a critical gap in current oracle solutions.
  2. HTTP Extension: By extending standard HTTP fetch operations, we ensure compatibility with existing web infrastructure while adding cryptographic guarantees. This approach allows for easy integration with a wide range of data sources without requiring significant changes to their existing systems.
  3. Decentralized Proxy Witnessing: Routing requests through HTTP Proxies adds an extra layer of security and decentralization. This mitigates risks associated with centralized oracle systems and enhances resistance to manipulation attempts.
  4. Flexibility in Data Sourcing: Our agnostic approach to data sources, supporting any HTTPS endpoint, maximizes the potential use cases for zkFetch. This flexibility is crucial for the diverse needs of the Arbitrum ecosystem.
  5. Cross-Chain Compatibility: Designing zkFetch to work across various blockchains ensures that Arbitrum can easily interact with other ecosystems, promoting interoperability and expanding the potential for cross-chain applications.
  6. Customizable Proof Parameters: This feature allows developers to tailor the security and compliance aspects of data fetching to their specific needs, enhancing the versatility of the solution.

We have already developed a DataDao, testing zkFetch’s capabilities with various data feed APIs, demonstrating our readiness to adapt the technology for Arbitrum. We are aiming to become the nexus for acquiring diverse, cryptographically verified, tamper-proof, and highly secure data across Web2 and Web3 ecosystems.

Our project depends on the Reclaim Protocol, specifically its attestor network, to verify that data is received from the correct source. This dependency is essential because:

  1. The Reclaim Protocol’s attestor network is a core component of zkFetch’s security model, ensuring the integrity and authenticity of fetched data
  2. It provides the infrastructure for generating and verifying zero-knowledge proofs, which is crucial for zkFetch’s privacy-preserving feature
  3. The attestor network helps in maintaining the decentralized nature of the oracle system, enhancing its reliability and resistance to manipulation

The Reclaim Protocol’s zkTLS infrastructure is integral to zkFetch’s core functionality, providing a unique and irreplaceable foundation for secure data fetching. This established system offers unparalleled expertise in zero-knowledge proofs and decentralized attestation, making it essential for delivering a robust, tamper-resistant oracle solution on Arbitrum.

Steps to Implement

Milestone 1: Research & Development Phase (6-8 Weeks)

  • Adapt zkFetch for Arbitrum’s architecture
  • Develop and deploy specific smart contracts to handle data feed responses from various providers, ensuring they can publish proofs on-chain
  • Effectively deploy Semaphore Contracts
  • Optimize zkProof generation and verification
  • Integrate with multiple data providers to demonstrate the capabilities of zkFetch.
  • Estimated cost: $30,000

Milestone 2: Testing and Documentation (4-5 Weeks)

  • Comprehensive unit testing of core functions to ensure functionality and robustness
  • Create detailed developer documentation and test guides
  • Estimated cost: $10,000

Milestone 3: Community Engagement and Marketing (2-4 Weeks)

  • Publish a blog post and host a community call to detail zkFetch Oracle solution and its benefits to the Arbitrum ecosystem
  • Initiate co-marketing efforts with Arbitrum to help onboard projects & Developers to integrate zkFetch in their applications.
  • Estimated cost: $2,000

Milestone 4: Integrate Diverse Data feeds (6-7 weeks):

  • Adding APIs for data feeds like crypto prices, sport data, and others.
  • Target to integrate at least 5-6 high-quality data providers initially.
  • Estimated cost: $10000

Milestone 5: Mainnet Deployment and Support (5-6 weeks):

  • Conduct final testing and deploy to Arbitrum mainnet
  • Integrate with 2 DApps from the Arbitrum ecosystem, focusing on use cases like Prediction Markets, RWA tokenization, and others
  • Provide continuous development support post-integration, led by Integration Support Developer from Reclaim
  • Estimated cost: $10,000

After successful integration and completion of all milestones, we will implement the following monthly budget to ensure the sustainability of the zkFetch oracle service:

  • To keep the oracle service running after covering all the milestones, we will require funding of $10,000 per month for the next 4 quarters. This fund will help us cover various data feed APIs subscriptions, zkFetch development, research and maintenance. We will be sharing monthly reports detailing how this budget is being used and the ongoing developments of zkFetch.

We request co-marketing support from Arbitrum to:

  • Promote the zkFetch oracle solution to Arbitrum Ecosystem and developers
  • Highlight the unique value proposition of cryptographically verified data feeds in joint marketing materials
  • Facilitate introductions to key projects and data providers in the Arbitrum ecosystem

By implementing zkFetch and integrating reputable data providers for diverse data sources, we aim to establish Arbitrum as the go-to platform for secure, verifiable real-world data in the blockchain space, driving significant ecosystem growth and innovation.

Timeline

  • Milestone 1 (Research & Development): 6- 8 Weeks
  • Milestone 2 (Testing and Documentation): 4-5 Weeks
  • Milestone 3 (Marketing & Community Engagement): 2-4 Weeks
  • Milestone 4 (Integrate Diverse Data feeds ): 6-7 Weeks
  • Milestone 5 (Mainnet Deployment and Support): 4-6 weeks

To accomplish the milestones outlined above, the entire project will require 1 Project Manager, 3 Developers, 1 BD manager, 1 Dev Relations Lead, and 1 Integration Support Developer.

Overall Cost

Total Cost: $62,000 (Covering all the milestones) + $10,000 per month (recurring cost)

Breakdown:

  • Development: $30,000
  • Testing and Documentation: $10,000
  • Marketing & Community Engagement: $2000
  • Integrate Diverse Data feeds: $10000
  • Mainnet Deployment and Support: $10,000
  • Monthly budget after covering all the milestones: $10,000 per month

Ongoing maintenance and developer support will be provided by the Reclaim Protocol team as part of their commitment to the zkFetch.

Revenue-Sharing Model
To ensure a mutually beneficial partnership and incentivize long-term collaboration, we propose a two-tier revenue-sharing model with the DAO based on the volume of data fetches processed through zkFetch in the Arbitrum ecosystem:

  • 3% revenue share per month for up to 250K data fetches.
  • 10% revenue share per month for volumes exceeding 250K data fetches.

This model allows for sustainable growth during the early stages of development while ensuring that as adoption scales, Arbitrum benefits proportionally from zkFetch’s success. We believe this approach aligns our long-term goals with the Arbitrum ecosystem’s growth and will enable us to contribute meaningfully to the broader community.

Team

zkFetch leverages the zkTLS infrastructure developed by Reclaim Protocol, a project led by the team at CreatorOS Inc. We are a 35+ member engineering and web3 product development & research team including ZKP researchers and with previous affiliations to Stanford, Microsoft, Meta and Google . We have also built - Questbook.app, an industry leading on-chain grants management tool that is used by some of the major L1/L2s including Polygon, Arbitrum, Solana, Compound, Ton, among others. CreatorOS is a YC W21 company.

  • Madhavan Malolan : CEO
    • Building in crypto since 2016.
    • Among first 5 contributors to Plasma (ethereum scaling solution) specifications.
    • Open source contributor.
    • ex-Microsoft, Computer Science IIIT-H.
    • LinkedIn. Github
  • Max Allman, Mechanism Design Researcher
    • PhD from Stanford in Mechanism Design and Game Theory
    • Co- author of the Reclaim Whitepaper
  • Kirill Kutsenok, Cryptography & Security Researcher
  • Adhiraj Singh: Lead Developer
  • Aleksai Ermishkin: Lead Blockchain Developer

I warmly invite all members of our vibrant Arbitrum community to share your thoughts on this zkFetch integration proposal. I’m eager to engage in discussions and address any points you raise.

Relevant Sources:

Social

4 Likes
2

Hey @mr-unomi! Please forgive me, I’m not a technical person and unable to provide valuable insights from a technical perspective. Based on the advantages mentioned in the proposal, I believe integrating zkFetch is worthwhile.

However, I noticed your milestones and budget—this proposal is set to last at least 6 months, and the budget is only $85,000. While I’ve always advocated for doing more with less, we can’t blindly cut costs. Is this budget sufficient to push the proposal forward effectively? Is it reasonable? Will it end up starting strong but fizzling out, or will you come back in a few months asking for more funds because the proposal can’t continue?

Another question is, after the project is completed in 6 months, will you continue to maintain it? Is there a detailed plan for that? Thank you!

1 Like
3

Your website states that zkFetch is recommended for public data that is unlikely to change within 5 seconds during proof generation. The library also supports adding retries and timeouts to fetch requests for improved reliability.

What to do then with the information on token prices, which can change more often and this is the main data?

2 Likes
4

I like that the budget for integrating zkFetch is modest—definitely a plus. But I agree with cp0x’s point; it’d be great to hear more about the real-world applications given the 5 seconds constraint.

1 Like
5

Thank you for your insightful question. Let me address this concern:

Most reputable data providers, for example CoinGecko, Coinmarketcap, and others, typically update their data at intervals of 30-60 seconds. This refresh rate aligns well with zkFetch’s capabilities, significantly reducing the likelihood of data inconsistencies.

Edge Case Handling: We acknowledge the potential edge case where proof generation might be triggered near the end of a provider’s refresh interval. To mitigate this, we’ve implemented several strategies:
a) Retry Mechanism: zkFetch supports 2-3 retries maximum, ensuring that if a data mismatch occurs, the system can quickly attempt to fetch the most up-to-date information.
b) Configurable Timeouts: We set the timeout to match the provider’s refresh interval, optimizing the balance between data freshness and successful proof generation.

We’ve also introduced support for regex in the responseMatch functionality. This feature provides more flexible and precise data extraction, further reducing the potential for mismatches.

Our team is constantly working on optimizing zkFetch’s performance. We’re exploring advanced techniques to handle even more frequent data updates while maintaining the integrity of our zero-knowledge proofs.

We’re confident these measures address concerns about data consistency, even for rapidly changing data like token prices. We’re open to feedback and committed to refining our solution to meet Arbitrum’s evolving needs.

2 Likes
6

Hey @mr-unomi , the overall project looks solid and promising, but we just had a couple of quick questions:

Can you tell us a bit more about how this would specifically attract developers? Also, do you think having docs + examples for developers would help make it better to onboard?

Since you’re already planning to work with Arbitrum for co-marketing, is it possible to lower the marketing budget a bit?

7

I really like the idea behind zkFetch, and it’s exciting to see the team, which has already proven themselves with previous successful projects, pushing this forward. I believe this proposal def aligns with Arbitrum’s goals, and that the integration of zkTLS tech will enable many use cases.

I do have one question regarding the ongoing costs: how long do you expect the $10k monthly payment to be necessary, and do you have a long-term funding plan in mind?

2 Likes
8

zkFetch has a good track record, and I don’t see why it wouldn’t be a good idea to integrate it.
The initial $62,000 for development, testing, documentation, marketing, and data integration seems well-allocated. However, the $10,000 monthly cost for API subscriptions and maintenance could become challenging if additional funding or stable income aren’t secured. Ensuring the platform gains enough traction to justify these ongoing expenses will be key to sustaining it long-term.

1 Like
9

Thank you, @Curia, for asking this question. I would like to address it concisely.

zkFetch attracts developers through:

  1. Seamless Integration:
  • Minimal effort required for integration
  • Ability to fetch data from any HTTP endpoint
  1. Cryptographic Guarantees:
  • Ensures trust between users and projects
  • Provides verifiable data integrity
  1. Enabling Innovative Use Cases:
  • Supports new applications like prediction markets (for example - tmr.news, fr.market already integrated zkFetch), AI + Web3 integrations, RWA and many others.
  1. Open-Source Infrastructure:
  • Core zkTLS infrastructure is now open-source
  • Attracts developers interested in transparent, community-driven tech

Regarding documentation:

Yes, comprehensive docs and examples are crucial for onboarding. We’re committed to providing:

  • Detailed technical documentation
  • Integration examples and tutorials
  • Up-to-date resources to support developers throughout the integration process

Our team will ensure these materials are continuously updated and expanded based on developer feedback and new features.

10

Hey @Curia, I’ve lowered the budget to $2,000 for co-marketing.

11

Hey @ggmatch,I appreciate your feedback. In addition to the detailed reply I’ve provided earlier to @cp0x, I’d like to address the 5-second constraint you’ve mentioned. We’re well aware of this limitation and have implemented several measures to tackle it. Over the past few months, our team has been constantly working on improving the zk-proof generation time. We’ve successfully reduced it from 30 seconds to 4-5 seconds, which is a significant improvement. I’m confident that in the future, we’ll be able to achieve sub-second proof generation times. This ongoing optimization will further expand the real-world applications of zkFetch, making it suitable for an even wider range of use cases.

12

Hey @Larva,
Thank you for the thoughtful questions! You’re absolutely right to focus on the long-term sustainability of the project, and we’ve refined our approach based on the community’s feedback.

We’re requesting additional $10K/month for 3-4 quarters. This extended runway will allow us to build, maintain, and smoothly integrate zkFetch into the Arbitrum ecosystem, ensuring quality over speed.

For long-term sustainability, our plan is to introduce paid services once zkFetch is stable and market-ready. We’ll offer a freemium model for smaller clients, with paid plans for larger users, ensuring the platform remains self-sustaining beyond the grant.

We’re committed to zkFetch for the long haul and excited to see what innovative projects will emerge in the Arbitrum ecosystem.

I appreciate your concern about doing more with less, and believe this revised plan strikes the right balance between responsible resource use and ensuring the project’s long-term viability. Let me know if you’ve got any other questions.

13

Hey @0xDonPepe,

Thank you for your support and interest in zkFetch. We’re excited about its potential too!

As we discussed in the recent Governance call, we’re looking at a 3-4 quarter timeline for the monthly $10K budget. This will give us the runway to fully develop, integrate, and refine zkFetch within the Arbitrum ecosystem.

For long-term funding, we have plans to transition to a self-sustaining model by offering paid services to oracle users. We’re aiming to implement this once zkFetch is stable and has achieved product-market fit. This approach will ensure the project’s continuity and ongoing development beyond the initial grant period.

We’re committed to building a valuable, sustainable solution for Arbitrum. Let me know if you have any other questions; I’m happy to answer.

1 Like
14

Hey @0xTALVO.ETH_MTY, thank you for the valuable feedback and for supporting our proposal. I’ve already addressed the monthly budget question in detail in other answers, and I’m happy to share a brief summary here.

We’ve strategically planned to build our product-market fit to ensure long-term sustainability and make zkFetch self-sustaining through revenue generation from potential clients integrating it as their oracle service provider. I’d be happy to answer any additional questions you may have.

1 Like
15

For long-term funding, we have plans to transition to a self-sustaining model by offering paid services to oracle users. We’re aiming to implement this once zkFetch is stable and has achieved product-market fit. This approach will ensure the project’s continuity and ongoing development beyond the initial grant period.

I’m glad to see there is an idea of how to fund ongoing costs that isn’t reliant on the DAO to subsidize. I have two questions relating to that however:

  1. Do you have any rationale or research on why you believe this will produce >$10,000 a month in revenue within that timeframe? i.e., is this an estimate or have you implemented this with other projects and seen historical data to indicate the timeframe. I would be concerned if we reach those 12 months and we have to continue funding (or decide not to fund and the project dies).

  2. Is there any willingness to have a portion of those subscription fees go to the DAO / Arbitrum?

16

Hey @Bob-Rossi, thank you for the feedback. I’d like to address your questions:

Our team has a proven track record of building revenue-generating products like Questbook and Reclaim Protocol, and we’re fully committed to making zkFetch a success. The requested funding for the next few quarters will allow us to focus on development, research, and essential expenses.

We’ve already streamlined our budget, and we’re confident zkFetch will continue to serve users and developers beyond the grant period. Our focus is on building a robust solution and achieving product-market fit, with the goal of making zkFetch self-sustainable in the long term.

While we can’t commit to sharing fee revenue at this stage, our budget is significantly lower than other oracle solutions that charge millions. Our primary goal is to establish zkFetch as a valuable, cost-effective solution for the Arbitrum ecosystem.

17

Thank you for the additional context.

Without agreeing to share revenue with the DAO, this as you noted becomes a grant. Can you explain why you are unable to apply for a grant through the Arbitrum Foundation? Or did not apply to one of the LTIPP / STIP programs?

As a delegate, I essentially have two concerns:

  1. We are ultimately still within the grant detox period
  2. I’m not sure why we as a DAO gave the Foundation another 250m ARB from the treasury if we have to continue to be asked to fund projects like this without the prospect of earning revenue on the backend to keep the treasury stable long term.

Please note: This isn’t me speaking against the project itself. I would be without hesitation be open to supporting it if there was a revenue sharing agreement.

18

Hi, could you please point out what would be the benefits of using zkTLS oracles over Chainlinks approach?
They have VRF for prediction markets etc.

I would assume the trust level could be higher because of a zk implementation. But my technical knowledge in terms of Oracles isn’t good enough to see all benefits.

Appreciate the answer

19

Hey @Bob-Rossi, I agree with your concerns and would like to share with you the latest update.

After internal discussions with my team, we’ve agreed to share revenue with the Arbitrum DAO after the funding period is over, allowing for initial growth and development. I’d be happy to propose the following two-tier model:

  • 3% revenue share per month for up to 250K data fetches.
  • 10% revenue share per month for volumes exceeding 250K data fetches.

I’ve updated the proposal with these details.

We didn’t apply to other programs as we only recently started seeking funding, and the application periods for LTIPP/STIP had likely closed. We approached the community directly to align our product with Arbitrum’s needs and work closely as a zkTLS-based oracle provider, envisioning ourselves as a long-term oracle solution contributing to the ecosystem’s growth.

1 Like
20

Hey @EzR3aL, Thank you for your question about the benefits of zkTLS-based oracles like zkFetch compared to other oracles. zkFetch offer several unique advantages:

  1. Cryptographic Verification: zkFetch cryptographically verifies the data received from servers, ensuring tamper-proof data integrity. This provides a higher level of security and trust in the data being used by smart contracts.
  2. Flexibility and Diverse Data Sources: Using zkTLS infrastructure as its core, zkFetch can fetch data from any HTTP endpoint. This offers a wider spectrum of diverse data sources, enabling new and emerging use cases. We can even fetch price feeds for long-tail assets in a verified manner, which many traditional oracle doesn’t offer.
  3. Developer-Friendly Integration: zkFetch is designed with minimal friction for developers, making integration simple and easy even for complex applications. This can significantly reduce development time and costs.
  4. Progressing Decentralization: We’re actively working towards greater decentralization. Our team is developing our own chain and increasing the number of attestors to ensure a robust, decentralized network. While I can’t share all the details yet, we’re excited about our upcoming public announcements related to this in the coming months.
  5. Cutting-Edge Technology: The zkTLS approach represents the latest infrastructure development in the blockchain space. It enables developers to fetch any off-chain data that was previously inaccessible with other oracle services, opening up new possibilities for DApp development.
  6. Affordability: A crucial point often overlooked is affordability. zkFetch offers highly secure, cryptographically verifiable data feeds and easy integration at competitive prices. This ensures the technology is accessible to a wide range of developers and projects, potentially saving millions in oracle costs and allowing teams to focus on their core product.

I hope this covers your questions, and I’m happy to answer any more questions you may have.

1 Like