July 2025 Development Updates #4

Hey devs, big news this week—zkFetch is now live on Stellar! 🚀

We're back with another exciting batch of updates across the Reclaim Protocol stack.

zkFetch is now deployed on the Stellar Blockchain, unlocking a new era of on-chain access to cryptographically verified public data.

From prediction markets and verifiable AI agents to proof-of-reserve and real-time economic/sports/weather feeds - Stellar devs can now build powerful, data-driven apps like never before.

Technical Details & Implementation

zkFetch - Stellar Deployment

zkFetch is now live on the Stellar Blockchain.

This milestone opens the door to migrating millions of public data points to Stellar - empowering developers to leverage the most powerful and cost-effective oracle available in the market.

With this deployment, Stellar developers can now build novel use cases around prediction markets, verifiable AI agents, proof-of-reserve, weather data, sports data, economic data, AI data marketplaces, and other applications involving public data that is cryptographically verified using zkFetch.

// Example URL to fetch the data from
const url =
  "<https://api.coingecko.com/api/v3/simple/price?ids=stellar&vs_currencies=usd>";
 
// Generate the proof
const proof = await reclaimClient.zkFetch(
  url,
  { method: "GET" },
  {
    responseMatches: [
      {
        type: "regex",
        value: '\\\\{"stellar":\\\\{"usd":(?<price>[\\\\d\\\\.]+)\\\\}\\\\}',
      },
    ],
  }
);

Documentation: http://docs.reclaimprotocol.org/zkfetch/stellar
Integration Example: https://github.com/reclaimprotocol/zkfetch-stellar-example

Mobile SDK Ecosystem

SDKs Repositories: React Native | Android | iOS

This week, we’ve focused on bug fixes, UI updates, and the addition of some new features.

Bug Fixes

• For Android, fixed automatic closing of verification screen on immediate errors.

• Corrected permissions dialog and URL loading behavior in iOS.

• Enhanced verification review screen UI and error message details.

• Improved handling of Android verification errors and webview re-initialization. https://github.com/reclaimprotocol/reclaim-inapp-android-sdk/pull/21

• Resolved an issue where the verification screen failed to present when rootViewController was replaced by a controller that blocked presentation. https://github.com/reclaimprotocol/reclaim-inapp-ios-sdk/pull/27

New Features

• Added tracking and validation of unique attempt IDs for verification activity instances.

• Added support for the optional credentials field in provider configurations for JS injections. This controls whether cookies or authentication headers are sent during verification fetch requests.

  As per MDN Fetch API docs, valid values are:

  • omit: Never include credentials

  • same-origin: Include credentials only for same-origin requests (default)

  • include: Always include credentials, even for cross-origin requests.

  This provides finer control over authentication behavior during claim verification.

---

Resources

• Documentation: docs.reclaimprotocol.org

• GitHub: github.com/reclaimprotocol

• Community: t.me/reclaimprotocol

Got questions about any of these changes? Hit us up in the community chat. We're always happy to help debug, explain, or chat about ideas you are working on.